Closed LeGeek01 closed 1 year ago
better-sqlite3@7.6.2
is not the latest, clean up your project folder. Does this happen in a clean empty folder? If not, then it's not a better-sqlite3 issue.
so in a empty folder the bug doesn't reproduce... so why I can't upgrade this package from a folder that contains an older version????
The package managers do not perform a full cleanup when installing (updating) an existing module to a newer version. Especially if node-gyp is used to build native modules this may lead to previous, auto generated files might stay in place and causing node-gyp to work with the old ones.
Due to the nature of the life-cycle of modules and capabilities of npm scripts, it is not totally impossible to implement something like a auto clean up, but in the end the best way is just cleaning up the node_modules folder manually when dealing with projects that use native modules which may require local (re)compilation.
Cleaning the node_modules requires a download of all modules again, and for someones who doesn't have a fast internet connection, that can be annoying So if a auto_clean script can be implemented in better-sqlite3, why not implementing it?
An "auto clean" feature would belong in node-gyp
, not this library. I can see that being useful: please feel free to suggest it to that project!
When I try to install the latest version of this package with
npm i better-sqlite3@latest
, npm give me this error :don't know why...