`pnpm` packaging not working
See original GitHub issueWhile working on #267, I could not get pnpm
functionality to work.
pnpm
stores it’s deps in a subdirectorynode_modules/.pnpm/
or some npm_reg folder for older versions with{package}@{version}
folders so the rest of the packaging logic doesn’t pull it into external.- It fails at the install command saying the lockfile is out of date.
- The list deps command is very broken because the list command without a depth only shows its top level dependencies.
At this point the pnpm
functionality does not work. Not sure if there was a version which this is actually compatible with @floydspace? If you are after this functionality please leave a comment below and I’ll try and find some time to work on it.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Automatic packaging workflow does not work properly #5201
I run a workflow on GitHub that automatically packages and creates RPM / docker image packages. As a result, they display pnpm: not...
Read more >Error Codes | pnpm
To fix this error, all dependencies that use the workspace protocol should be updated to use versions of packages that are present in...
Read more >Newest 'pnpm' Questions - Stack Overflow
The project I am working on currently uses pnpm as the package manager, ... library package in the project (pnpm i react-bootstrap) but...
Read more >How to migrate a JavaScript project to pnpm (package manager)
To resolve those problems and others, Facebook introduced a new package manager in 2016 called Yarn . Yarn was touted as being faster, ......
Read more >pnpm/pnpm - Gitter
The problem is, I ended up with a 4.3 GB image, because each package in the repo might have symlinks in its node_modules...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I had a first take last week and discovered the incompatibility with lambda and the symlinked structure. I would absolutely love to fix this. But ultimately this is just a volunteer thing for me and sometimes it’s quite hard to pick up the tools after work
Hey @samchungy, it was contributed by @lulzneko, to be honest, I haven’t tested it and have never used it, maybe initially it worked. Please go ahead to fix it if possible.