Ghost-CLI: npm install sqlite3 --save error
See original GitHub issueCurrently when using ghost-cli 1.0.0.4 and using ghost install local
during the installation I get this error and the installation fails.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:27 (9 by maintainers)
Top Results From Across the Web
Ghost local installation fail because of SQlite3
A GhostError occurred. Message: Ghost was able to start, but errored during boot with: Knex: run $ npm install sqlite3 --save. Cannot find ......
Read more >Fixing "Cannot find module 'sqlite3'" error when installing ...
I was getting the following error when installing Ghost v4 ... 1) GhostError $ npm install sqlite3 --save Cannot find module 'sqlite3'.
Read more >Installing Ghost 1.8.6 with sqlite db fails after configuring ...
The ghost installer try to install sqlite3 via node but it seems there ... again and it seems to take the compiled version...
Read more >NPM is throwing a bunch of errors when I try to install SQLite3
Whenever I run npm install --save sqlite3@^4.0.9 in my integrated terminal in Visual Studio Code, NPM throws these errors:
Read more >Ghost Theme Development on WSL2 - Perspectives
sudo npm install -g ghost-cli@latest ghost install local ghost start ... Error: Knex: run $ npm install sqlite3 --save Cannot find module ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
For anyone else who comes across this issue, it is caused by changing node versions after installing ghost-cli.
Sqlite3 is a binary dependency that comes with precompiled binaries and downloads the right one for your system on install. If you change the environment, it will look for a different binary, which wasn’t downloaded.
Ideally, the CLI would catch this error and explain clearly what the problem was 😬
Got the same error when using Node 14 LTS (Fedora 33, Yarn). Downgrading to Node 12 LTS and removing and reinstalling ghost-cli fixed it. (
yarn global remove ghost-cli && yarn global add ghost-cli
)