This post will cover post-deployment and runtime errors where you may encounter the message "The module was compiled against a different version of Node.js".
important: First, make sure App Service Logs is enabled
- log stream
- Get records directly fromKuduwebsite or directly view/download via FTP client
- Diagnose and fix problems -> Application Log Detector, Container Crash Detector or Container Problem Detector
Only if application service logs are not enableddocker logsThe files will be generated, the files associated with the application will not be displayedstandard output/standard errorAnd it can complicate troubleshooting.
important: This post focuses on the Azure App Service Linux "Blessed" image running Node.js - however, this issue can occur inany environmentAnd it's not limited to Azure.
Depending on the packages you have installed and used in your project - and the difference between "build" vs. "Runtime" versions of Node.js - you can see errors like this - this can happen in any environment - such as on-premise or on another machine, such as a virtual machine, or on an Azure App Service instance.
Error: Module '[something-project]\node_modules\[something-module]\bin\binding\bin\[something-module].node' was compiled with a different version of Node.js with NODE_MODULE_VERSION 83. This version of Node . js requires NODE_MODULE_VERSION 108. Try to recompile or reinstall the module (eg using `npm rebuild` or `npm install`). at Object.Module._extensions..node (node:internal/modules/cjs/loader:1310:18) at Module.load (node:internal/modules/cjs/loader:1089:32) at Function.Module._load ( node:internal/modules/cjs/loader:930:12) to Module.require (node:internal/modules/cjs/loader:1113:19) to require (node:internal/modules/cjs/helpers:103:18) in the Object.(C:\Users\[Bruger]\node_modules\[noget-modul]\dist\binding\index.js:6:17) ε¨ Module._compile (Δvor:internal/modules/cjs/loader :1226:14) ε¨Object.Module._extensions..js (node:internal/modules/cjs/loader:1280:10) ε¨ Module.load (node:internal/modules/cjs/loader:1089:32) ε¨ε½ζ°.Module._load (Δvor ) :intern/modules/cjs/loader:930:12) depends too much onknot cracksInstall or compile the C/C++ source code that those packages depend on via the Node.js plugin. For example, a package likepasswordorsharp.
Why is this happening?
The main reason this happens is the difference between the Node.js version in "build" and the Node.js version in "runtime"npm install(or an equivalent installation command using your recommended package manager)
Ideally, both build-time and runtime versions should have the same major and minor version of Node.js.
It usually ends up referring to one. knotFiles created under similar paths[some project]\node_modules\[some module]\bin\binding\bin\[some module].nodeIt was created with a different version of Node.js than the one currently running.
record: This can happen when the middleware version is lower than the runtime version and vice versa.
What is NODE_MODULE_VERSION
In tracking you will therefore notice this message at the beginning:
The module '[something-module]' was compiled with a different version of Node.js with NODE_MODULE_VERSION [VERSION]. This version of Node.js requires NODE_MODULE_VERSION [VERSION]where [VERSION] is an integer. This version number usually refers to the version it was built with and the version it ran with.
We can use the original message at the top of this article as an example. Here we have the following middleware and runtime versions in the error message:
The module '[something-module]' was compiled with a different version of Node.js with NODE_MODULE_VERSION 83. This version of Node.js requires NODE_MODULE_VERSION 108You can download fromThe Node.js download and release page is here.Using this page we can see:
- NODE_MODULE_VERSION 83 DaBefore 14.x
- NODE_MODULE_VERSION 108 DaBefore 18.x
That being said, we can say that the error message says that the package and possibly other plugins are installed and compiledBefore 14.xand we're actually trying to run itBefore 18.x.Tells us to run against the same regular major version of Node.js.
The download and release pages provide some additional information on whatNODE_MODULE_VERSIONAlso used for:
NODE_MODULE_VERSION refers to the ABI (application binary interface) version number for Node.js, used to determine which versions of Node.js compiled binary C++ plugins can be loaded without recompilation. It used to be stored as a hexadecimal value in previous versions, but is now represented as an integer.
(Video) π ππ Microsoft Teams ππ«π«π¨π« ππ¨ππ ππππππππ Your Computer's Trusted Platform Module has Malfunctioned βοΈ
More information about Node.js plugins can be found ather.
More information about the Application Binary Interface (ABI) can be found ather- We can see in this documentation that it says that major versions have the same intent in all environments and packages using possible plugins:
Conversely, if an application depends on packages that contain native plugins, the application must be recompiled, reinstalled, and reinstalled again every time a new major version of Node.js is brought into production.
In the deployment and runtime environment on Azure App Service Linux, we cover some possible solutions.
Node.js runtime version change - Oryx
If you use Oryx for deployment -- for example, local Git, ZipDeploy (using Oryx Builder), or other methods that rely on Oryx to build your application -- build the environment, this is done for the "Kudu" container. The version of Node.js in the Kudu container must match the Node.js in the application container.
As an example, we set up our application to use node 16:
We will implement a dependency onSemiotics.this userknot cracksFor additional compilation of C/C++ code.
Now we will change the application to use node 18. Note that this usesYesReinstall any package, but in this case just change the runtime version.
Now we run into the error described in this post:
PATH="$PATH:/home/site/wwwroot" node dist/main.jsFound tar.gz-based node_modules.Removing existing module library from root...Unpacking modules...Done.node:internal/modules/cjs/ loader :1338 return process.dlopen(module, path.toNamespacedPath(filename));Error: Module '/node_modules/symbology/bin/binding/bin/symbology.node' was compiled with a different version of Node.js using NODE_MODULE_VERSION 93. This the Node.js version requires NODE_MODULE_VERSION 108. Try to recompile or reinstall the module (eg using `npm rebuild` or `npm install`). at Module._extensions..node (node:internal/modules/cjs/loader:1338:18) at Module.load (node:internal/modules/cjs/loader:1117:32) at Module._load (node:internal/ modules/cjs/loader:958:12) at Module.require (node:internal/modules/cjs/loader:1141:19) at require (node:internal/modules/cjs/helpers:110:18) at Object.< Anonymous > (/node_modules/symbology/dist/binding/index.js:6:17) in Module._compile (node:internal/modules/cjs/loader:1254:14) in Module._extensions..js (node:internal /modules/cjs/loader:1308:10) at Module.load (node:internal/modules/cjs/loader:1117:32) at Module._load (node:internal/modules/cjs/loader:958:12) { Code: 'ERR_DLOPEN_FAILED'}In this case,NODE_MODULE_VERSION93 corresponds to node 16.x, docNODE_MODULE_VERSION108 corresponds to node 18.x. shows that we are building the application on node 16 but trying to run it on node 18.
solve:
- If you need to change the runtime version, you must reinstall the applicationbackPlease upgrade to a newer version of Node.js to properly rebuild any packages that depend on C/C++ code and/or plugins.
Change Node.js runtime and build version - Azure DevOps
In your Azure DevOps pipeline, you can usenode toolA task that specifies the version of Node.js used fornpm install(oryarn).
- Task: node tools@0 A nurse: version specification: '16.x' visningsnavn: 'Install Node.js'- the script: | npm install npm run build --if-present visningsnavn: 'npm Install, put up i try out'Same as above if this differs from the abovefeel, you will still encounter thisNODE_MODULE_VERSIONMismatch error.
it is possible to stateversion of linuxFxSets the runtime of the program. For example inAzure Web Appdeployment task, we'll make sure it matches the Node.js specified in the pipeline and vice versa.
- Task: AzureWebApp@1 visningsnavn: 'blue mesh Application insert: some apps' A nurse: azure subscription: $(azure_subscribe) Types of applications: Linux network application Application name: $(web application name) runtime stack: 'node|16-lts' package: $(Pipeline.Workspace)/drop/$(Build.BuildId).zipChange Node.js runtime and build version - GitHub actions
The same concept applies to GitHub actions. The following tasks are common ways to set the Node.js version in the currently running GitHub Actions workflow:
- To do: Set the version of Node.js use: action/set node@v1 i: node version: '18.x'- To do: npm install, build feel: | npm install npm run build --if-presentAgain, we have to be sureThis corresponds to the Node.js version of the running application.
ZipDeploy i FTP (bez Oryx Buildera)
If using ZipDeploy (without Oryx) or FTP to deploy an application, this usually means deploying a package (npm installorFit/add yarn) is executed locally first, and that's itmodule nodesIt should be implemented along with other application content.
In that case, check if it's yoursLocalThe version of the Node.js environment matches what you have setfeelna Azure App Service.
A good tool to ensure parity betweenmost importantLocal machine and App Service versions are created using Node Version Manager, also known asnvm.
You can download nvmherAnd check out the documentation on how to change your Node.js version locally.
non-application server environment
If this happens in an environment other than the Azure App Service Linux build and run system, you can use one or more of the following methods to troubleshoot the issue:
- Verify that there are no node version changes in progress
npm install(or an appropriate package manager installation)- For example, using two different terminals, this could accidentally target two different environments
- delete
module nodesipackage lock.json(oryarn lock), and try to install the package again. - You can try to restore the package using
npm rebuild [ε ] --update-binaryor justnpm rebuild [paket]
If you installed the package globally, uninstall the package withnpm uninstall -g [package]. Otherwise, if you're targeting a specific package that isn't globally installed, just usenpm uninstall(or the equivalent for your current package manager).
FAQs
How do I resolve a node module error? βΊ
- delete the node modules folder by running rm -rf node_modules.
- delete package.lock.json file by running rm -f package-lock.json.
- clean up the NPM cache by running npm cache clean --force.
- install all packages again by running npm install.
Changing Node.
If you don't know the version you want to install, type nvm ls-remote to get a full list of all installable Node. JS versions. You can also use nvm install --lts instead! As before, nvm use node or nvm use --lts will use the latest stable version.
- To install the latest version of Node, run nvm install latest .
- To install the LTS version of Node, run nvm install lts .
- To install a specific version of Node, you need to run nvm list available first so you can see the versions of Node that are available.
On Windows Platform the simplest way is to use the terminal. Please Run the command RMDIR /Q/S foldername to delete the folder and all of its subfolders. The Above Command deletes node_modules folder and its subfolders.
How to reinstall npm node modules? βΊ- To force this behavior, start by deleting the node_modules directory within the project:
- Then run the install command to reinstall the packages in a new node_modules folder:
- The install command creates the node_modules within your current directory and downloads the package to the project.
So, the flag to get the version is --version or -v . So just type node -v and you will get the version of Node. js you are using.
How to switch node versions with npm? βΊ- Open the Terminal and check your current Node version: node -v.
- Install n package using the following command: npm install -g n. ...
- To update Node, run the following command in your terminal: n latest. ...
- Now you can verify that your update is complete by rechecking your Node version: node -v.
- Navigate to the root directory of your project and ensure it contains a package.json file: cd /path/to/project.
- In your project root directory, run the update command: npm update.
- To test the update, run the outdated command. There should not be any output.
With npm or yarn, you can install a package under a custom alias. This enables you to install multiple versions of a package in the same project. Read the documentation on aliasing with npm here and yarn here.
How do I uninstall current Node version? βΊ- Go to Settings by searching it in the start menu.
- Click on the Apps section.
- Look for the search box under Apps & Features section, and enter Nodejs there.
- Select on Nodejs application and click on uninstall.
How to check if two nodes are the same in js? βΊ
Node: isEqualNode() method
The isEqualNode() method of the Node interface tests whether two nodes are equal. Two nodes are equal when they have the same type, defining characteristics (for elements, this would be their ID, number of children, and so forth), its attributes match, and so on.
If it's just running (not a daemon) then just use Ctrl-C.
How do you handle node failure? βΊHandling node crashes
If a failed node cannot be recovered, auto recovery migrates all data from disks in this node to other disks in cluster. If the system does not recover, delete the disks in the node and node.
How to clear cache? To clear a cache in npm, we need to run the npm cache clean --force command in our terminal. To clear the cache present in npm, you need to run the command. If it doesn't work, run the force clean method since the cache is not cleared simply.
How do I find my node module? βΊNode Modules
Packages are dropped into the node_modules folder under the prefix . When installing locally, this means that you can require("packagename") to load its main module, or require("packagename/lib/path/to/sub/module") to load other modules. Global installs on Unix systems go to {prefix}/lib/node_modules .