"ENOENT: no such file or directory, rename ..." when running npm install

[kevinmannn]

After running npm install --save-dev sqlite3, each subsequent time I try to run npm install I get an error relating to "ENOENT: no such file or directory, rename ...".

The first subsequent run resulted in the following:
npm ERR! path /Users/[...]/node_modules/.staging/npmlog-702088a9
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename '/Users/[...]/node_modules/.staging/npmlog-702088a9' -> '/Users/[...]/node_modules/sqlite3/node_modules/node-pre-gyp/node_modules/npmlog'
npm ERR! enoent This is related to npm not being able to find a file.

The next run resulted in this error:
npm ERR! path
/Users/[...]/node_modules/sqlite3/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/are-we-there-yet/node_modules/delegates
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename
npm ERR! enoent ENOENT: no such file or directory, rename '/Users/[..]/node_modules/sqlite3/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/are-we-there-yet/node_modules/delegates' -> '/Users/[...]/node_modules/sqlite3/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/are-we-there-yet/node_modules/.delegates.DELETE' npm ERR! enoent This is related to npm not being able to find a file.

Environment:
MacOS 10.12.6
NPM 5.3.0
Node v6.11.2
Also occurring on Jenkins on Ubuntu 16.04 LTS.

[bkimminich]

Seems essentially the same issue as #865, just that it seems to hit you on node 6.x while hitting me on 8.x.

[mauris]

the current way I'm working around this is to do the following for each subsequent npm install needed:

1. Uninstall sqlite3: npm un sqlite3
2. Install what I need, along with sqlite3: npm i --save ...<all other packages>... sqlite3

Alternatively:

1. Write my dependencies and version numbers manually into package.json.
2. Delete node_modules folder: rm -rf node_modules
3. Install dependencies from package.json: npm i

[louisremi]

The simplest workaround is to pin sqlite3 package temporarily to 3.1.8.

[wayofthefuture]

How do you pin it, if it is a dependency of another package.

[XieX]

Same problem, running node v8.3.0 (npm v5.3.0).

How do you pin it, if it is a dependency of another package.

Good q'n. I'm using db-migrate which has a dependency on sqlite3, so here's what I did:

1. Uninstall the package(s) that depend on sqlite3 (e.g. for me it was npm un db-migrate)
2. npm i sqlite3@3.1.8
3. Reinstall the package(s) that depend on sqlite3 (e.g. for me, npm i db-migrate)

Hope it helps 🍺

[shawnbissell]

I had a few packages that used sqlite3. The easiest way to find them all was to run
npm ls sqlite3

[makamekm]

Please fix it. We cannot use it. The module doesn't work on any platform.

[wayofthefuture]

+1

[pleerock]

Owners, this is very critical issue and needs to be fixed urgently.