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 bundling strategy of tsup #289

Merged
merged 2 commits into from Apr 15, 2024
Merged

Fix bundling strategy of tsup #289

merged 2 commits into from Apr 15, 2024

Conversation

valentinpalkovic
Copy link
Contributor

@valentinpalkovic valentinpalkovic commented Apr 12, 2024

Closes storybookjs/storybook#26819

The node entry needed to be bundled correctly. This led to externalizing packages, which we don't do in a node environment, only for the browser.

Additionally, I have removed the source map generation because we usually don't do it for add-ons since it increases the download size by a lot.

πŸ“¦ Published PR as canary version: 1.3.3--canary.289.2081b09.0

✨ Test out this PR locally via:

npm install @chromatic-com/storybook@1.3.3--canary.289.2081b09.0
# or 
yarn add @chromatic-com/storybook@1.3.3--canary.289.2081b09.0

@valentinpalkovic valentinpalkovic added the patch Auto: Increment the patch version when merged label Apr 12, 2024
@valentinpalkovic valentinpalkovic self-assigned this Apr 12, 2024
@valentinpalkovic valentinpalkovic added the release Auto: Create a `latest` release when merged label Apr 12, 2024
@ghengeveld ghengeveld merged commit 6afda22 into main Apr 15, 2024
8 checks passed
@ghengeveld ghengeveld deleted the valentin/fix-bundling branch April 15, 2024 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
patch Auto: Increment the patch version when merged release Auto: Create a `latest` release when merged
Projects
None yet
3 participants