ManagerBuilder: Fix "type": "commonjs"
compatibility
#24534
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #22511
What I did
iife
for manager-builder so it work in commonjsI found out that when
package.json
module
-field is set tocommonjs
(I do not understand why this is even a thing, as this is the default AFAIK), that the output of esbuild changes.When using
commonjs
as thetype
andesm
as theesbuild
-format
, the output looks like:The
export default
part in a non-top-level code section is invalid.It's invalid because we wrap the code outputted with a
try-catch
-block, to ensure manager entries are fault-tolerant.When I change the
esbuild
format
config toiife
then the output looks like this:So that works!
I also checked if this affects the case where
package.json
usestype
=module
, and it's not that different:Before (
esbuild
'sformat
=esm
):After (
esbuild
'sformat
=iife
):Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
package.json
'stype
field tocommonjs
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal
,ci:merged
orci:daily
GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli/src/sandbox-templates.ts
Make sure this PR contains one of the labels below:
Available labels
bug
: Internal changes that fixes incorrect behavior.maintenance
: User-facing maintenance tasks.dependencies
: Upgrading (sometimes downgrading) dependencies.build
: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup
: Minor cleanup style change. Will not show up in release changelog.documentation
: Documentation only changes. Will not show up in release changelog.feature request
: Introducing a new feature.BREAKING CHANGE
: Changes that break compatibility in some way with current major version.other
: Changes that don't fit in the above categories.🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/core
team here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>