Repository navigation
fix: dev server errors and dev:prepare warnings - #1493
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
commit: |
Bundle sizeClient 806.5 kB (no change) · Server 1.67 MB No route loads 100 B more or less before it renders. No prerendered URL's initial load or HTML changes by 100 B or more. Brotli sizes. Changes under 100 B are left out of the tables. Measured by nuxt-bundle-analyzer for |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
nr dev:prepareprinted several warnings and one error on every run,nr devcrashed, and the first page load in dev triggered a dependency re-optimization and full reload. The root.nuxtrcenabled@nuxtjs/i18nin all three apps without locales, nuxt-llms had no domain in the layer and the playground, the workspaceh3: 1.15.11override forceddevframe(loaded by@nuxt/fonts) onto h3 v1 although it needs v2, and six client dependencies were only found by Vite at runtime..nuxtrc:nuxt typecheck layerpasses without the i18n module, so the playground no longer needsi18n: falselayer/.nuxtrcwithsite.urlso nuxt-llms has a domain when the layer is prepared alonesite.urlin the playground and mark it"type": "module"h3@1, so onlydevframeand@devframes/agenticresolve h3 2.0.8@comark/vueand@comark/vue/plugins/shikiin the layer (used by the always-registeredAssistantComark), and@ai-sdk/vue,ai,@vercel/analytics,@vercel/speed-insightsin the docs appEvidence
pnpm run dev:preparewarnings after the change:nr devbefore:nr devafter:First visit to
/enin dev before:After, with the Vite deps cache cleared: no runtime discovery, no reload, no console errors on
/enand/en/getting-started/installation.pnpm run typecheckexits 0, and a type error added on purpose makes it exit 2.pnpm run docs:buildcompletes.Notes
addCustomTabdeprecation comes from@nuxt/icon2.6.3 (latest) and needs an upstream fix.NUXT_B7002still lists@nuxtjs/mdc > …entries added by the mdc module.ELI5
A settings file meant for one folder was being applied to the whole project, which made some tools complain. A version pin meant for older packages was also forcing a newer tool onto a version it can't use, which stopped the dev server from starting. The dev server now also prepares a few libraries up front instead of discovering them mid-page and reloading.
🤖 Generated with Amp, reviewed by @larbish before opening.