-
Notifications
You must be signed in to change notification settings - Fork 74
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
Possibly provide more of the built-in npm "dry run" output #184
Comments
I like this idea! I think what might be happening here is that What we could do is have |
Sounds promising, thanks! Unfortunately, I'm not familiar enough with this codebase to submit a PR myself. Sorry. 😞 |
All good! It’ll be a pretty small lift if my assumptions hold 🤞, will take a crack at it by Friday |
Awesome, thanks! We're already seeing those changes in our builds, and it looks great! 😁 🎉 |
Have you considered including more of the standard output of npm's "dry run" mode? I find that quite helpful sometimes, such as to see what all files would be included in the published package (so that I can adjust things to remove unneeded files).
Here's a slightly-redacted example of what npm shows:
However, the npm-publish GitHub action seems to only show something like this:
Thank for making helpful open source packages, nonetheless! 😁
The text was updated successfully, but these errors were encountered: