Skip to content
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

fix(build): add script to fix package.json before publishing #475

Merged
merged 3 commits into from
May 16, 2023

Conversation

wolfy1339
Copy link
Member

@wolfy1339 wolfy1339 commented May 9, 2023

Resolves #474

Behavior

Before the change?

The released npm package is missing most of the files generated by the build step. dist-node, dist-types, dist-web... even though they are generated correctly.

After the change?

With the corrected file patterns, npm will publish all the necessary files again.

Other information

This is a mix of an issue with npm@v9 (npm/cli#6164) and the fact we rely on pika for the build step. Pika has been archived since April 2022 so there is nothing we can do with Pika.


Additional info

Pull request checklist

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)
  • Added the appropriate label for the given change

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

  • Yes (Please add the Type: Breaking change label)
  • No

If Yes, what's the impact:

  • N/A

Pull request type

Please add the corresponding label for change this PR introduces:

  • Dependencies/code cleanup: Type: Maintenance

@wolfy1339 wolfy1339 added Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR Priority: High labels May 9, 2023
Copy link
Member

@kfcampbell kfcampbell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I appreciate you getting us unbroken here! In the future, I'm going to be confused about this script's existence and purpose. What are your feelings on linking an associated issue/PR in the comments, or perhaps adding a note in our documentation about why it's necessary?

@wolfy1339
Copy link
Member Author

I appreciate you getting us unbroken here! In the future, I'm going to be confused about this script's existence and purpose. What are your feelings on linking an associated issue/PR in the comments, or perhaps adding a note in our documentation about why it's necessary?

It won't be necessary too long into the future, hopefully.

A comment in the file would probably be best.

@wolfy1339
Copy link
Member Author

@kfcampbell I added comments to the release workflow, and to the script file itself.

@wolfy1339 wolfy1339 merged commit 9e3a7e1 into main May 16, 2023
@wolfy1339 wolfy1339 deleted the fix-release branch May 16, 2023 22:06
@github-actions
Copy link
Contributor

🎉 This PR is included in version 4.0.11 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

[BUG]: package files not published to npm
2 participants