Replies: 1 comment
-
|
The only side effect I seem to be having is this warning during updates, so I always need to rerun the linking script afterwards. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
In a monorepo I'm using better-sqlite3 both in Electron and in a Fastify server. Exact same package versions, different required ABI versions for each env.
For Electron, I have to rebuild it to Electron's Node ABI, with
electron-rebuild -f.My problem is that it breaks the backend's version as well.
I'm trying hard to break pnpm's hard linking to somehow separate those packages from each other.
I ended up writing a Python script which breaks a hard-linked folder for this package and make it into a copied folder.
Super hacky, but works.
Is there a built-in way to do this in pnpm? I'd love to have a specific package not-hard-linked, meanwhile having every other package hard-linked.
Also, I'm wondering about the following: if there is no Fastify server, so no conflict, what happens with the pnpm store's location when I run
electron-rebuild? Isn't that command destroying every instance of this package on my system, because of the shared pnpm store?Beta Was this translation helpful? Give feedback.
All reactions