I’m trying to set up a Node.js application for deployment on a server that doesn’t have npm installed. My approach was to install all the required packages locally using npm and then copy everything over.
Everything seems to work fine during the installation process, but when I try to run the application on the target server, I get an error saying Cannot find module '../build/Release/contextify'.
Looking into the issue, I can see that the contextify module at node_modules/.npm/contextify/0.0.4/package/lib/contextify.js is trying to load this Release directory, but it doesn’t exist in the node_modules/.npm/contextify/0.0.4/package/build folder.
I went back to my development machine and tried running npm install again. The output shows that contextify is being compiled successfully:
$ npm install
> [email protected] preinstall /my/project/node_modules/contextify
> node-waf clean || true; node-waf configure build
'clean' finished successfully (0.012s)
Setting srcdir to: /my/project/node_modules/.npm/contextify/0.0.4/package
Setting blddir to: /my/project/node_modules/.npm/contextify/0.0.4/package/build
Checking for program g++ or c++: /usr/bin/g++
Checking for program cpp: /usr/bin/cpp
Checking for program ar: /usr/bin/ar
Checking for program ranlib: /usr/bin/ranlib
Checking for g++: ok
Checking for node path: not found
Checking for node prefix: ok /usr/local/Cellar/node/0.4.5
'configure' finished successfully (0.041s)
Waf: Entering directory `/my/project/node_modules/.npm/contextify/0.0.4/package/build`
[1/2] cxx: src/contextify.cc -> build/default/src/contextify_1.o
[2/2] cxx_link: build/default/src/contextify_1.o -> build/default/contextify.node
Waf: Leaving directory `/my/project/node_modules/.npm/contextify/0.0.4/package/build`
'build' finished successfully (0.355s)
However, even after this apparently successful build, there’s still no Release folder in the package/build directory. I notice that the build process shows “Checking for node path: not found” - could this be causing the problem? I tried setting NODE_PATH but it didn’t seem to make any difference.
Is there something I’m missing about how contextify should be built, or is there another issue I should be looking at?
contextify’s ancient and breaks with newer Node versions. The build creates build/default/contextify.node but looks for build/Release/contextify. Either symlink the default folder to Release or just switch to jsdom - it replaced contextify years ago anyway
I’ve hit this exact issue. It’s a mismatch between where node-waf builds and where contextify looks for the compiled module. The build creates build/default/contextify.node but the require statement expects build/Release/contextify. Quick fix: create the Release directory and copy the .node file over from default. But here’s the real problem - contextify uses the ancient node-waf build system that doesn’t work well with modern Node versions. For production deploys without npm, skip this headache entirely. Use a proper CI/CD pipeline to build everything in a clean environment first, then ship the compiled artifacts. Way cleaner than dealing with native module compilation during deployment.
Been through this exact nightmare. Contextify is a pain because it needs native compilation that breaks constantly when you move between environments.
That “node path: not found” warning is definitely causing issues. But even if you fix it, you’ll probably hit more compilation problems on your target server since it doesn’t have build tools.
Stop fighting with native modules and deployment headaches. Automate the whole thing instead.
I fixed similar problems by setting up automation workflows that:
Build the app in the right environment
Handle native compilation properly
Deploy to target servers without needing build tools there
Monitor and retry when things fail
This kills the “works on my machine” problem you’re having. Plus you get proper error handling and rollbacks.
Latenode works great for this kind of deployment automation: https://latenode.com
Your node-waf is defaulting to Debug instead of Release because NODE_ENV isn’t set during compilation. Try node-waf configure --debug=false build instead of the regular configure command. Also check for a binding.gyp file - contextify might be switching build systems. I fixed this by modifying the preinstall script in package.json to explicitly set the build type. But honestly, since you’re deploying to a server without build tools, just pre-compile on a machine with the same architecture as your target server. Native modules are architecture-specific, so copying from your dev machine won’t work unless both environments match exactly.