@vue/compat 3.5.44 → 3.5.45
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/dist/vue.cjs.js +322 -127
- package/dist/vue.cjs.prod.js +300 -123
- package/dist/vue.esm-browser.js +315 -120
- package/dist/vue.esm-browser.prod.js +10 -10
- package/dist/vue.esm-bundler.js +316 -121
- package/dist/vue.global.js +315 -120
- package/dist/vue.global.prod.js +10 -10
- package/dist/vue.runtime.esm-browser.js +310 -119
- package/dist/vue.runtime.esm-browser.prod.js +4 -4
- package/dist/vue.runtime.esm-bundler.js +311 -120
- package/dist/vue.runtime.global.js +310 -119
- package/dist/vue.runtime.global.prod.js +4 -4
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -24,11 +24,11 @@ While we've tried hard to make the migration build mimic Vue 2 behavior as much
|
|
|
24
24
|
|
|
25
25
|
Please note that the migration build aims to cover only publicly documented Vue 2 APIs and behavior. If your application fails to run under the migration build due to reliance on undocumented behavior, it is unlikely that we'll tweak the migration build to cater to your specific case. Consider refactoring to remove reliance on the behavior in question instead.
|
|
26
26
|
|
|
27
|
-
A word of caution: if your application is large and complex, migration will likely be a challenge even with the migration build. If your app is unfortunately not suitable for upgrade, do note that we are planning to backport Composition API and some other Vue 3 features to the 2.7 release
|
|
27
|
+
A word of caution: if your application is large and complex, migration will likely be a challenge even with the migration build. If your app is unfortunately not suitable for upgrade, do note that we are planning to backport Composition API and some other Vue 3 features to the 2.7 release.
|
|
28
28
|
|
|
29
29
|
If you do get your app running on the migration build, you **can** ship it to production before the migration is complete. Although there is a small performance/size overhead, it should not noticeably affect production UX. You may have to do so when you have dependencies that rely on Vue 2 behavior, and cannot be upgraded/replaced.
|
|
30
30
|
|
|
31
|
-
The migration build will be provided starting with 3.1, and will continue to be published alongside the 3.2 release line. We do plan to eventually stop publishing the migration build in a future minor version
|
|
31
|
+
The migration build will be provided starting with 3.1, and will continue to be published alongside the 3.2 release line. We do plan to eventually stop publishing the migration build in a future minor version, so you should still aim to switch to the standard build before then.
|
|
32
32
|
|
|
33
33
|
## Upgrade Workflow
|
|
34
34
|
|