This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
refactor(nuxt)!: cleanup schema and split nuxt 2 types #8487
Merged
Conversation
This file contains 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
|
β Deploy Preview for nuxt3-docs canceled.
|
This also resolves nuxt/nuxt#15006, right? |
7 tasks
danielroe
reviewed
Oct 26, 2022
Co-authored-by: Daniel Roe <daniel@roe.dev>
(this PR has probably some more breaking changes and unwanted regressions as well. merging earlier to find them out via edge channel) |
Merged
8 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
π Linked issue
Resolves nuxt/nuxt#14135, resolves nuxt/nuxt#15006, resolves nuxt/nuxt#15199
β Type of change
π Description
Initially, we started Nuxt 3 project by documenting all possible configs from Nuxt 2 into
@nuxt/schema
alongside with@nuxt/bridge
code. Over time it becomes both complex to maintain and also confusing UX because you can see auto-completion of options fromnuxt.config
that are not working with Nuxt 3.Changes by this PR:
@nuxt/bridge-schema
Β bridge#597)@nuxt/bridge-schema
Β bridge#597)@version
filter is removed from schema. Adding back for future schema versioning as@nuxt
or@constraints
Breaking changes:
nuxt.config
serverMiddleware
config is not supported anymore (useserverHandlers
ordevServerHandlers
)addServerMiddleware
kit utility is removedwebpack:devMiddleware
andwebpack:hotMiddleware
hooks unsupportedbuild:compile
andbuild:compiled
hooks renamed towebpack:compile
andwebpack:compiled
build:resources
hook is unsupported (usevite:compiled
andwebpack:compiled
)build:before
,build:done
,modules:before
andmodules:done
take no argumentsbundler:change
,bundler:error
,bundler:done
andbundler:progress
hooks renamed withwebpack:
prefixoptions.env
andoptions.target
, andoptions.build.quite
are not used anymore by webpack builderπ Checklist