-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
ESM: Start migration: use ESM in node #28797
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 48954f0. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
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.
30 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings
After some investigating I found that in the new situation Due to the CLI split PR, most of the code for the CLI is not actually in the core package, which this PR does not touch, therefore the weight loss of the CLI is very low. I've bundled in the above packages in my latest commit, and this does improve a little. An obvious next step would be to ensure |
Works on 29072
What I did
This set storybook on the course of using ESM support in node.
In this PR I've migrated the CLI packages to run their ESM code.
In fact the main storybook CLI is now compiled for only ESM!
This should save some space, though now most of the code is present/moved to
@storybook/core
the impact is not high.I've adjusted the code loading builders to support loading ESM.
The following packages are now ESM only (and
type=module
):builder-vite
create-storybook
storybook
@storybook/cli
Because our code has a lot of references to
require
and__dirname
and the like (which are only supported in node when it's in CJS-mode, I've had to make some adjustments to our bundling mechanism.I think this is OK for now, and likely not something we can move away from until we drop CJS completely.
I think this is backwards compatible.
Everything I changed is internal only, AFAIK.
Maybe there might be an impact on community builders?
Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
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 pull request has been released as version
0.0.0-pr-28797-sha-e221ee7e
. Try it out in a new sandbox by runningnpx storybook@0.0.0-pr-28797-sha-e221ee7e sandbox
or in an existing project withnpx storybook@0.0.0-pr-28797-sha-e221ee7e upgrade
.More information
0.0.0-pr-28797-sha-e221ee7e
norbert/esm-v2
e221ee7e
1724919906
)To request a new release of this pull request, mention the
@storybookjs/core
team.core team members can create a new canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=28797
Greptile Summary
The PR migrates Storybook CLI packages to ESM, updating various package.json files, TypeScript files, and scripts to support ESM. Key changes include replacing
fs-extra
with@ndelangen/fs-extra-unified
, updating ESLint configurations, and modifying code loading builders to support ESM.code/.eslintrc.js
to handle TypeScript and ESM imports, adding rules forimport/no-extraneous-dependencies
andimport/no-unresolved
.package.json
files incode/addons/docs
,code/addons/links
, andcode/builders/builder-vite
to support ESM, including new dependencies like@ndelangen/fs-extra-unified
.@ts-expect-error
incode/addons/essentials/src/actions/manager.ts
to suppress type errors due to missing type definitions.fs-extra
with@ndelangen/fs-extra-unified
andnode:fs/promises
for file operations in multiple files, includingcode/core/scripts/helpers/dependencies.ts
andcode/core/src/builder-manager/index.ts
.code/builders/builder-vite/src/index.ts
to use dynamicimport
statements for ESM compatibility.