Since we [released Node.js for Mobile Apps](http://www.janeasystems.com/blog/announcing-node-js-mobile-apps-true-node-js-runtime-android-ios/), the most requested feature has been support for Node.js native modules (also known as "C++ Addons"). This makes sense, since it is common for an npm module to either contain some native code itself or have a dependency on a module that does.

So we have been working hard to tackle this challenge. We are now excited to announce that support for native modules is available in the latest release of the React Native and Cordova plugins.

Being able to use these modules strengthens compatibility of Node.js for Mobile Apps with the npm module ecosystem, and opens a lot of possibilities for building mobile applications with Node.js.

### How to start using native modules with Node.js for Mobile Apps

With the latest release of [nodejs-mobile-react-native](https://www.npmjs.com/package/nodejs-mobile-react-native) and [nodejs-mobile-cordova](https://www.npmjs.com/package/nodejs-mobile-cordova), the plugins automatically detect the existence of native modules inside the \`nodejs-project\` folder in your app, and take care of building and packaging them as part of the application build process. It just works!

In the samples repo, you can find a [React Native sample app](https://github.com/janeasystems/nodejs-mobile-samples/tree/master/react-native/UseNativeModules) and a [Cordova sample app](https://github.com/janeasystems/nodejs-mobile-samples/tree/master/cordova/UseNativeModules) that include the [sqlite3](https://www.npmjs.com/package/sqlite3) and [sha3](https://www.npmjs.com/package/sha3) native modules, so you can try this feature right away.

### Node.js native modules and their challenges for mobile

[Node.js native modules](https://nodejs.org/api/addons.html) are Node.js packages that contain native code and instructions on how to build that native code using [node-gyp](https://github.com/nodejs/node-gyp). When installing a native module from npm, the default behavior is for the module to be built for the system on which npm is currently running. This makes sense when using Node.js on the server/desktop, where we can expect the required build tools to be available on the system, or for the module to be prebuilt and copied from a similar system. On mobile, however, this is either not practical or (on iOS) downright impossible; so we had to modify a few things to enable native modules to get cross-compiled and packaged with the application.

To that end, the plugins are using a [modified version of node-gyp](https://www.npmjs.com/package/nodejs-mobile-gyp) that is able to target the right OS and CPU architecture and include the Node.js headers from the Node.js for Mobile Apps release.

On iOS, we also need to ensure that the module binaries are packaged as a Framework signed with the application's signing identity and loaded from the application's /Frameworks path, which is required for loading dynamic libraries and for being accepted in the iOS App Store. Many thanks to [Patrick Chugh](https://twitter.com/patrickchugh), for all his help in validating iOS App Store submission with the [Shango App](https://github.com/neogeno/shango-lightning-wallet/blob/master/README.md).

On Android, we have to build a standalone toolchain before we can cross-compile native modules, and that needs to be done for each ABI supported by the application. We are able to support Universal APKs by packaging binaries for all the supported ABIs, and then choosing which binary to load at runtime.

Special care is also needed for modules the use [node-pre-gyp](https://www.npmjs.com/package/node-pre-gyp) to download a prebuilt binary, to ensure that they are actually built on the current machine and for the target OS and architecture.

All of that and more is handled automatically by the plugins, so developers don't even need to worry about whether their app uses native modules or not.

### Limitations and future work

Our goal was to ensure that as many existing native modules as possible work without modification on mobile. However, Node.js native modules are so flexible that it is not feasible to support every possible scenario. Modules that have non-standard build steps (e.g. depending on shell scripts rather than node-gyp, for building) may require further changes to work on mobile. Modules with platform-specific code or dependencies might need porting of that code to iOS or Android.

Given the large number of native modules out there, it would probably take our team a very long time to test and try to solve all the possible compatibility issues. So this is an area where we hope to get a lot of help from the community. To that end, we have created a [GitHub repository](https://github.com/janeasystems/nodejs-mobile-module-compat) where the community can discuss compatibility issues of existing modules with nodejs-mobile.

There are also other improvements to be made:

*   Adding support for building native modules for Android on Windows development machines (currently only macOS and Linux are supported).
*   Providing an easy way to use native modules in applications that are not using the \`nodejs-mobile-react-native\` or \`nodejs-mobile-cordova\` plugins.
*   Being able to use an installed NDK instead of building a standalone NDK toolchain for Android.

### A whole new world of possibilities

Having native modules opens a whole new world of possibilities for using Node.js for Mobile Apps. Our [community Gitter channel](https://gitter.im/nodejs-mobile/community) has been filled with questions and experiments on this topic. We can't wait to see what sort of novel and creative applications can be developed now that native modules are supported out of the box.

We invite you to try using Node.js with native modules in your mobile applications, and to get involved with the project. Provide feedback, report bugs, suggest improvements, contribute code. Go build amazing new apps and radically new frameworks with it!

To get started, visit the [Node.js for Mobile Apps website](https://code.janeasystems.com/nodejs-mobile).

Node.js for Mobile Apps further improves compatibility with the npm module ecosystem by adding support for native modules.

Support for native modules in Node.js for Mobile Apps - Janea Systems - Blog

Support for native modules in Node.js for Mobile Apps

In our ongoing quest to improve [Node.js for Mobile Apps](https://code.janeasystems.com/nodejs-mobile) (a.k.a Node.js Mobile), we have just completed a series of major improvements and made them available in the latest release. Of course, in delivering these improvements, we have paid close attention to the desires and feedback of our valued users, as always.

## **V8 JavaScript engine now on iOS**

Probably the most noteworthy update is the use of the V8 JavaScript engine on iOS. This replaces the ChakraCore engine that was used previously on Apple devices. With this update, Node.js relies on the same engine on both Android and iOS, ensuring consistent behavior and reliability across all devices.

Previously, when we used V8 on Android and ChakraCore on iOS, some specific code cases behaved differently due to implementation differences between the two engines. Some APIs were available on one platform and not the other. These issues are now eliminated.

The use of V8 on iOS was made possible by the engine now supporting a JIT-less mode, since its [7.4 release](https://v8.dev/blog/jitless).

## **Based on Node.js 12.16 LTS (Long-Term Support)**

The latest release is based on Node.js 12.16 LTS (Long Term Support), and has all of the latest security fixes patched into the software. Node.js 12 is the active LTS version, until [Node.js 14](https://nodejs.org/en/about/releases/) enters LTS on Oct. 20, 2020.

This also offers access to more recent APIs, such as 'worker\_threads', which make it possible to run JavaScript on more than one thread. This is an innovation that has been strongly desired among the Node.js Mobile community, and we're delighted that we can deliver it as required.

There is also ES6 JavaScript module support included, and the system now contains a more recent N-API version, which ensures improved module compatibility. 

The Node.js Mobile codebase is now rebased on the main [Node.js repository](https://github.com/nodejs/node/) instead of [node-chakracore](https://github.com/nodejs/node-chakracore). This will make it easier to keep up to date with future LTS versions and security vulnerability fixes. 

## **Built with V8 snapshots for Android**

The new release has been built with V8 snapshots for the Android version. Since V8 and Node.js internal JavaScript code are pre-initialized to be directly loaded into the heap, faster startup and run times are possible. Users on our [community channel](https://gitter.im/nodejs-mobile/community) have reported application launch time reductions of 50%. 

The challenge in building Node.js Mobile with snapshots was the cross-compiling of V8 and Node.js, while also having to build the snapshots to run on a different OS and CPU architecture.

With this recent release, Node.js Mobile is more powerful than ever. [Check out](https://code.janeasystems.com/nodejs-mobile/getting-started) the new changes, and we would love to know what you think!

Interested in exploring the possibilities of Node.js on mobile devices or Node.js application development? If so, [contact our consulting services team](http://www.janeasystems.com/#contact) to find out how we can help.

In our ongoing quest to improve Node.js for Mobile Apps (a.k.a Node.js Mobile), we have just completed a series of major improvements and made them available in the latest release.

Significant Updates in the New Release of Node.js Mobile- Janea Systems - Blog

Significant Updates in the New Release of Node.js Mobile

small_Jaime HD.jpg

thumbnail_Jaime HD.jpg

Jaime HD.jpg

Jaime

Windows developers were missing core modules in React Native, creating a significant gap in development capabilities.

Core Module Accessibility

Missing modules blocked core initiatives for customers, limiting the potential for application development on the platform. 


Blocked Customer Initiatives

The absence of vital modules meant a lack of functional parity with other operating systems, necessitating a tech-agnostic approach to port 16 modules.

Functional Parity

Bridging the gap between React Native and Windows applications, enabling developers to utilize a unified codebase across platforms.

Bridging Platforms

Integrating 16 missing core modules for a seamless Windows development experience, expanding the capabilities of React Native on Windows.

Unblocking Customers

Enabled collaboration between Microsoft and the open source community for a richer, more inclusive developer experience.	

Community Collaboration

While React Native successfully served iOS and Android developers, there was a significant gap in the Windows user base. Several mobile platform modules were unavailable on Windows, which hindered the development process, blocking key Microsoft customers and the broader open source community. This project was initiated as a response to the increasing need for a unifying developer experience across various platforms, enabling devs to create Windows desktop applications in React Native. 

Microsoft leveraged Janea Systems' tech-agnostic expertise to port 16 modules to React Native for Windows to increase functional parity with other OSs. 

Porting Core React Native Modules to Windows

Enabling React Native Desktop Applications 

Extend Azure Maps’ influence to an untapped market of over 1 billion iOS users.

Unlocking iOS Market Potential

Achieving web and Android parity on iOS.	

Feature Parity

Building an SDK that enables companies to bring their products to the iOS market.

Creating an iOS SDK with a Native Feel

Bringing Azure Maps to a whole new user base by integrating it with iOS. 

Successful iOS Integration

Achieving feature parity, enabling developers to utilize Azure Maps regardless of the platform.

Web, Android and iOS Feature Parity

Offering native-feel SDK tools to both Swift and Objective-C developers. 

Dual Language Development

Expanding Azure Maps' potential market reach exponentially.  	 

Market Reach Amplification

Owned by Microsoft, Azure Maps was only available for web and Android users. This drastically reduced the size of their market as there are over a billion iOS users that were missing out on the world-class enterprise software.   

Find out how we built an interoperable SDK in Swift and Objective-C to unlock Azure maps for iOS developers.  

Expanding Azure Maps to over a Billion iOS devices 

Expanding Azure Maps to Over a Billion iOS devices 

Reviving and updating a historic software utility for modern operating systems.	

Historical Revival

Prioritizing, managing, and integrating vast community feedback, contributions and issue reports.	

Open Source Engagement

 Navigating and integrating diverse tech stacks across 20+ modules.

Tech Stack Diversity 

Ensuring smooth integration and functionality across devices within the Windows ecosystem.

Seamless OS Integration

Enhanced productivity tools for power users, elevating efficiency and utility. 

Boosted User Productivity

Fostered a highly engaged and collaborative open-source community.

Active Community Engagement

Established PowerToys as a platform for trialing potential future Windows features.

Windows Feature Sandbox

Expanded the module offerings, catering to a wide range of user needs.

Rich Module Library

Microsoft Powertoys has over 15 million downloads and counting.

15M+ Downloads

Microsoft, aiming to revive PowerToys for modern Windows versions, partnered with us, leveraging our extensive expertise in open-source development. Our collaboration focused on updating and innovating utilities to meet contemporary user needs. 

Janea Systems champions Microsoft PowerToys, enhancing Windows for power users through active development and community engagement. Discover the impact. 

Maintaining Microsoft PowerToys 

Reviving Microsoft PowerToys for the Open Source Community 

Objective-C

Java

Python

Lead Software Engineer

large_Janea Systems OG Image No Text.png

medium_Janea Systems OG Image No Text.png

small_Janea Systems OG Image No Text.png

thumbnail_Janea Systems OG Image No Text.png

Janea Systems OG Image No Text.png

Janea Systems is a software engineering consultancy, serving the enterprises that drive global innovation for over two decades. We help our clients build and optimize technologies used by millions of developers and billions of consumers. 

Skills

Projects

Related Blogs

Let's talk about your project

Let's talk about your project