You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the v4 release, we have an opportunity to simplify our current list of 'experimental' features:
remove treeshakeClientOnly experimental option (enabled by default since v3.0.0)
remove configSchema option (enabled by default since v3.3.0)
remove polyfillVueUseHead (disabled since v3.4.0) - implementable in user-land with plugin
remove respectNoSSRHeader (disabled since v3.4.0) - implementable in user-land with server middleware
I would also like to remove renderJsonPayloads option (enabled by default since v3.5.0) but there seem to be a number of repositories using it and I think we need to investigate why and help them migrate to JSON payloads first.
In addition, I think we can consider enabling the following options by default sooner than 4.x:
polyfillVueUseHead can definitely be removed, @vueuse/head has been sunset for almost a year
headNext may also be worth removing if we're considering moving things under the module key meta, the Capo implementation can be enabled by default in the next Unhead release
Happy with all the considerations 👍🏻
Especially enabling more of the options (as they can be easily disabled if things go "wrong")
For each removed feature/flag which could be a user-land implementation it'd be great to give an example in the release notes / migration guide / blog post, so people can easily "migrate" if they need said behavior.
With the v4 release, we have an opportunity to simplify our current list of 'experimental' features:
treeshakeClientOnly
experimental option (enabled by default since v3.0.0)configSchema
option (enabled by default since v3.3.0)polyfillVueUseHead
(disabled since v3.4.0) - implementable in user-land with pluginrespectNoSSRHeader
(disabled since v3.4.0) - implementable in user-land with server middlewareI would also like to remove
renderJsonPayloads
option (enabled by default since v3.5.0) but there seem to be a number of repositories using it and I think we need to investigate why and help them migrate to JSON payloads first.In addition, I think we can consider enabling the following options by default sooner than 4.x:
headNext
(cc: @harlan-zw - what do you think?)scanPageMeta
sharedPrerenderData
Thoughts welcome 🙏
The text was updated successfully, but these errors were encountered: