-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pnpm publish
produces different package contents than npm publish
#6997
Comments
Could you share a repo to reproduce this issue? What I can see is that |
Sorry for the late response, but you can look at my repo here: https://github.com/vue-youtube/vue-youtube |
Any update on this? |
We need to update |
Love to see that it got fixed now. |
pnpm/pnpm#6997 finally fixes the pack command creating duplicated file, We can now use relative pathing for main, module and types
Verify latest release
pnpm version
8.7.0
Which area(s) of pnpm are affected? (leave empty if unsure)
CLI
Link to the code that reproduces this issue or a replay of the bug
No response
Reproduction steps
Running
pnpm -r publish --access public --no-git-checks --dry-run
produces:Running
npm publish --workspaces --access public --dry-run
produces:Describe the Bug
What seems rather odd is that there are slight differences in which files are included in the final package:
pnpm
(not explicitly included)npm
(not explicitly included)dist/index.cjs
file is included twice with slightly different paths when usingpnpm
:./dist/index.cjs
anddist/index.cjs
. This shouldn't affect the package contents, as both file paths refer to the same file.Expected Behavior
The package contents are the same for both tools. Also, the same file is only included once instead of two (or more) times.
Which Node.js version are you using?
20.5.0
Which operating systems have you used?
If your OS is a Linux based, which one it is? (Include the version if relevant)
Arch
The text was updated successfully, but these errors were encountered: