-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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(web-components): dont ship non production assets to npm registry #26854
fix(web-components): dont ship non production assets to npm registry #26854
Conversation
Asset size changesSize Auditor did not detect a change in bundle size for any component! Baseline commit: ae03f3eec389aca7e15fde295868aacd51eb1822 (build) |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit d6259c0:
|
137a65d
to
d6259c0
Compare
📊 Bundle size report🤖 This report was generated against e1be11888330811efdbf51f3fd4682dd9f0b804c |
temp | ||
temp/ | ||
etc/ | ||
CHANGELOG.json |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about this one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean CHANGELOG.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is no purpose to ship metadata json to registry, but it turns out that even ignore wont work on this one. Im aware that you cannot ignore Readme.md and Changelog.md but this is a bit mystery to me heh
…26854) * fix(web-components): dont ship non production assets to npm registry * generate change file
…icrosoft#26854) * fix(web-components): dont ship non production assets to npm registry * generate change file
…icrosoft#26854) * fix(web-components): dont ship non production assets to npm registry * generate change file
…icrosoft#26854) * fix(web-components): dont ship non production assets to npm registry * generate change file
…26854) * fix(web-components): dont ship non production assets to npm registry * generate change file
…26854) * fix(web-components): dont ship non production assets to npm registry * generate change file
…26854) * fix(web-components): dont ship non production assets to npm registry * generate change file
…26854) * fix(web-components): dont ship non production assets to npm registry * generate change file
…26854) * fix(web-components): dont ship non production assets to npm registry * generate change file
…26854) * fix(web-components): dont ship non production assets to npm registry * generate change file
…26854) * fix(web-components): dont ship non production assets to npm registry * generate change file
…26854) * fix(web-components): dont ship non production assets to npm registry * generate change file
…26854) * fix(web-components): dont ship non production assets to npm registry * generate change file
Previous Behavior
New Behavior
stories and other metadata/assets are no longer shipped to npm
helpers.ts moved to
helpers.stories.ts
to match proper domain and remove from npm registrytweak of script aliases to align more with repo nomenclature
Generate api.md changes
Related Issue(s)