Zoltan Kochan
Zoltan Kochan
Děkuji za dobré slova! What also makes pnpm unique is that it uses a content-addressable store and files are hard-linked from it. So you end up using less disk space...
I have forked this project to https://github.com/pnpm/node-byline in order to fix this warning in pnpm.
Do you use `auto-install-peers=true`?
So the issue is that we added the publishDirectory field to the lockfile. You probably just need to update your lockfile.
It is your choice. I try to not cause such issues but of course pinning the version is the most reliable solution.
can you create repository that reproduces the issue?
Do you use the `auto-install-peers=true` setting?
It was caused by this change: https://github.com/pnpm/pnpm/pull/5067 And a similar issue was already reported and fixed: https://github.com/pnpm/pnpm/issues/5080 But looks like there are still some edge cases.
Have you tried to remove your lockfile and node_modules, then to generate again and commit it? The issue is that pnpm now installs the root peer dependency automatically, so if...
@jason-ha thanks I was able to reproduce it https://github.com/zkochan/pnpm-issue-5144