refactor(kit,nuxt)!: drop support for nuxt 2 and compiling templates with ejs #27706
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
📚 Description
This finally enables and removes the opt-out for removing template compilation (#26925), as well as dropping support for Nuxt v2 in kit utilities.
The new major version of Nuxt Kit (v4) will not contain shims for interacting with Bridge or Nuxt 2 projects. If you are using any of the following functions from Nuxt Kit they will no longer provide backwards compatibility:
defineNuxtModule
checkNuxtCompatibility
addLayout
extendPages
(Modules that need v2 compatibility can continue to depend on Nuxt Kit v3.)
In addition, when adding templates support is now dropped for compiling EJS syntax with
lodash-template
.