I’m working on a Keystone.js project and deployed it to my Ubuntu server. The app works perfectly on my local development machine, but I’m having trouble with dependency installation on the production server.
Whenever I run npm install, the process gets stuck during the extraction phase. Here’s what I see in the terminal:
npm WARN deprecated [email protected]: This package has been renamed, please use the updated version
npm WARN deprecated [email protected]: Package is no longer maintained
npm WARN deprecated [email protected]: No build tools needed anymore, use alternative package
npm WARN deprecated [email protected]: Update to version 3.0.2+ to fix security vulnerability
npm WARN deprecated [email protected]: Update to version 3.0.2+ to fix security vulnerability
npm WARN deprecated [email protected]: Compatibility issues with node v7+. Please upgrade to v4+
npm WARN deprecated [email protected]: Old version no longer supported. Use v4+ instead
Terminated .....] - extract:time-grunt: sill doParallel extract 1194
The installation always hangs at the extract:time-grunt step and never completes. I’ve checked the node_modules directory and it remains empty. I tried removing everything and starting fresh multiple times but get the same result.
My server environment: Ubuntu 16.04, Node.js 4.5.0, npm 3.10.16
Has anyone encountered this issue before? Any suggestions on how to resolve this extraction problem?
Had the same issue with an old Node.js setup on Ubuntu. Your Node 4.5.0 is ancient (2016) and doesn’t play nice with modern npm packages - extraction gets stuck constantly. Usually happens when there’s permission problems or your Node version can’t handle the package compression. Upgrading to Node 8+ fixed it for me. Before upgrading, run npm install --verbose to see exactly where it hangs. Also check you’ve got enough disk space and npm can write to node_modules. Try npm cache clean --force too, though the syntax might be different on your old npm version.
I’ve hit this exact freeze on a legacy project with similar versions. Time-grunt has known issues with older npm extraction - usually network timeouts or registry connection problems. Try npm install --timeout=120000 to give it more time. Also check your server’s RAM - npm extraction eats memory and will hang if you’re running low. You might need more swap space or use --production to skip dev dependencies. Quick workaround: install time-grunt separately first with npm install time-grunt, then run your full install.
check your npm registry first - it gets corrupted during server deploys. run npm config get registry and make sure it’s pointing to https://registry.npmjs.org/. also delete the entire npm cache folder manually (usually ~/.npm) instead of using the clean command. i’ve hit this exact hang with keystone projects before and it was always cache corruption or registry connection issues.