Skip to content

feat(kit,nuxt,schema,vite,webpack): migrate to nitropack v3 nightly#27702

Merged
danielroe merged 36 commits intomainfrom
feat/nitro
Jun 26, 2024
Merged

feat(kit,nuxt,schema,vite,webpack): migrate to nitropack v3 nightly#27702
danielroe merged 36 commits intomainfrom
feat/nitro

Conversation

@danielroe
Copy link
Member

@danielroe danielroe commented Jun 19, 2024

🔗 Linked issue

📚 Description

This migrates to a particular version of nitro v3 and h3 v2 nightly releases, for further testing.

More significant breaking changes are coming in h3, along with the following further todos

  • update Nuxt upgrade guide for nitro-related changes
  • update nuxt/test-utils in a forward/backward compatible way
  • remove internal dependencies on event.node
  • remove db0 in Nitro upstream
  • refactor runtimeConfig inside Nuxt

@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@github-actions github-actions bot added the 3.x label Jun 19, 2024
@danielroe danielroe changed the title feat(kit,nuxt,schema,vite,webpack): migrate to nitropaack v3 nightly feat(kit,nuxt,schema,vite,webpack): migrate to nitropack v3 nightly Jun 19, 2024
@socket-security
Copy link

socket-security bot commented Jun 19, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@nuxt/[email protected] None 0 277 kB danielroe
npm/@nuxt/[email protected] None 0 81.7 kB danielroe
npm/@nuxt/[email protected] None 0 53.9 kB danielroe
npm/[email protected] None +1 883 kB pi0
npm/[email protected] environment, filesystem, network Transitive: unsafe +35 3.32 MB pi0
npm/[email protected] None 0 673 kB danielroe
npm/[email protected] environment, filesystem +11 426 kB isaacs
npm/[email protected] None 0 29.6 kB pi0
npm/[email protected] None 0 95.4 kB npm-cli-ops
npm/[email protected] None 0 26.2 kB pi0
npm/[email protected] None +1 26.3 kB antfu
npm/[email protected] None 0 21.9 MB typescript-bot
npm/[email protected] None 0 103 kB pi0
npm/[email protected] None 0 7.87 kB pi0
npm/[email protected] None 0 31.8 kB pi0
npm/[email protected] Transitive: network +2 1.18 MB pi0
npm/[email protected] Transitive: filesystem +11 571 kB antfu
npm/[email protected] filesystem 0 175 kB antfu
npm/[email protected] None +2 87.9 kB pi0
npm/[email protected] environment, eval, filesystem, network, shell, unsafe +1 3.43 MB vitebot
npm/[email protected] None 0 1.4 kB danielroe
npm/[email protected] environment, eval Transitive: filesystem, shell +13 1.7 MB vitestbot
npm/[email protected] None 0 45.6 kB danielroe
npm/[email protected] environment 0 825 kB posva
npm/[email protected] None 0 5.14 kB johnsoncodehk
npm/[email protected] environment, eval 0 2.2 MB yyx990803

🚮 Removed packages: npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

@danielroe
Copy link
Member Author

/trigger release

}
if (ctx.isClient) {
ctx.alias['#internal/nitro'] = resolve(ctx.nuxt.options.buildDir, 'nitro.client.mjs')
ctx.alias['nitro/runtime'] = resolve(ctx.nuxt.options.buildDir, 'nitro.client.mjs')
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just checking it was because of runtime config access right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exactly. This is so we can use isomorphic code that gets replaced with different runtime config code on client.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay! I have an idea to get rid of it!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙌

"@unhead/dom",
"@unhead/shared",
"@unhead/ssr",
"db0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It shouldn't be added by default in the prod bundle seems strange!

@danielroe danielroe requested a review from pi0 June 21, 2024 13:54
@danielroe danielroe marked this pull request as ready for review June 21, 2024 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants