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
pnpm version: 7.19.0, on 7.18.(0,1,2) works fine breaking change was introduced on 7.19.0
Code to reproduce the issue: Will create a repo for reproducing asap.
Problem:
After pnpm install -r --frozen-lockfile, postinstall hook runs and generates a client folder for prisma, inside the symlinked package, but this folder is not reflected inside the node_modules of the packages that has this module installed.
7.18.2 behavior:
When running pnpm generate which creates this client folder, the symlinked folder correctly diplays this client folder and the typings work correctly.
Additional information:
node -v prints:v16.18.1
Windows, macOS, or Linux?: Mac and Ubuntu
The text was updated successfully, but these errors were encountered:
Tried with latest, 8.1.1 and this is still present. @zkochan Zoltan didn't want to mention you, but could you give me some guideline of how could we fix this?
Basically since 7.19.0, when we generate a folder inside a module that is present in our packages of our monorepo, that's not updated across the monorepo, we need to run again a pnpm install to resync.
Couldn't we add something like a listener on config so when a package folder changes, autmoatically refreshes the other packages node_modules?
pnpm version: 7.19.0, on 7.18.(0,1,2) works fine breaking change was introduced on 7.19.0
Code to reproduce the issue: Will create a repo for reproducing asap.
Problem:
After
pnpm install -r --frozen-lockfile
,postinstall
hook runs and generates aclient
folder for prisma, inside the symlinked package, but thisfolder
is not reflected inside the node_modules of the packages that has this module installed.7.18.2 behavior:
When running
pnpm generate
which creates this client folder, the symlinked folder correctly diplays this client folder and the typings work correctly.Additional information:
node -v
prints:v16.18.1The text was updated successfully, but these errors were encountered: