You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was reading through the newest release changelog (8.24.0), where I noticed the breaking change "Removed support for Firefox bookmarks due to sqlite and pnpm implications", and after reading the commits, I was able to see that the problem is caused by a pnpm's issue with the sqlite3 dependencies, which causes the build to fail when running pnpm package to build the installer.
However, npm run package worked just fine, so I wanted to propose:
Is it possible that we use npm instead of pnpm (while the pnpm's team solves the issue) instead of completely dropping the feature?
Perhaps, there's something else that I'm missing?
Otherwise, I'd drop a PR if needed, please let me know ^^
The issue is already documented in the pnpm's repo, and there's a workaround available, though perhaps not so convenient:
this can be fixed in my windows by edit 'AppData\Roaming\npm\node_modules\pnpm\bin\pnpm.cjs', but how to let other users auto fix this, all users need change like this?
Hello :)
I was reading through the newest release changelog (8.24.0), where I noticed the breaking change "Removed support for Firefox bookmarks due to sqlite and pnpm implications", and after reading the commits, I was able to see that the problem is caused by a pnpm's issue with the sqlite3 dependencies, which causes the build to fail when running
pnpm package
to build the installer.However,
npm run package
worked just fine, so I wanted to propose:Is it possible that we use npm instead of pnpm (while the pnpm's team solves the issue) instead of completely dropping the feature?
Perhaps, there's something else that I'm missing?
Otherwise, I'd drop a PR if needed, please let me know ^^
The issue is already documented in the pnpm's repo, and there's a workaround available, though perhaps not so convenient:
Originally posted by @AiHaibara in pnpm/pnpm#5638 (comment)
The text was updated successfully, but these errors were encountered: