Closed M3rcena closed 9 months ago
Probably the special characters in Υπολογιστής
or the space in Milrato Remake
which causes trouble with building (outside the control of better-sqlite3). If you upgrade to the latest better-sqlite3 (7.6.2 is old) this should not be an issue since it has prebuild for Node 20.
Probably the special characters in
Υπολογιστής
or the space inMilrato Remake
which causes trouble with building (outside the control of better-sqlite3). If you upgrade to the latest better-sqlite3 (7.6.2 is old) this should not be an issue since it has prebuild for Node 20.
What else can I try?
Are you getting the same error with the renamed path? From what I can see weky-update
is an outdated package that is no longer maintained so you're on your own.
Well the package itself doesn't use better-sqlite3 that why they told me to contact here. They are not responsible for the error. Also I am getting the same error.
What happens if you run npm install better-sqlite3
in a completely empty folder with no parent folder containing any node_modules
? Does that install without any error? If so, then this is not an issue with better-sqlite3.
I can install better-sqlite3 package to any folder without error. Even the project I am trying to install the weky-update package the better-sqlite3 was installed already with version 8.6.0.
Try installing the latest node 20 build, and make sure you click the checkbox that adds support for compiling native modules:
Also, this may help set up you box:
https://github.com/WiseLibs/better-sqlite3/blob/master/docs/troubleshooting.md
Closing as this isn't an issue with better-sqlite3, but a windows toolchain setup issue.
Problem
I am trying to install weky-update package using npm and every time I run the
npm i weky-update
on terminal it tries to do something with better-sqlite3 which causes an error. They don't me to contact better-sqlite3 while the error is not from their side.Error