-
Notifications
You must be signed in to change notification settings - Fork 101
feat: use jiti to import/resolve modules
#632
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
Conversation
|
Open in Stackblitz β’ nuxt-cli-playground commit: |
Bundle StatsHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded
Removed
Bigger
Smaller
Unchanged
|
| overrideEnv('development') | ||
| const cwd = resolve(ctx.args.cwd || ctx.args.rootDir) | ||
| showVersions(cwd) | ||
| await showVersions(cwd) |
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.
This was intentionally to block rest of build logic for informational information (iirc)
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.
it wasn't previously async but we could make it non blocking
π Linked issue
β Type of change
π Description
this drops a lot of legacy code from
nuxithat was using cjs utilities to import/resolve paths within nuxt