@vue/compat 3.5.16 → 3.6.0-alpha.2
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 +0 -2
- package/dist/vue.cjs.js +2057 -1585
- package/dist/vue.cjs.prod.js +1761 -1369
- package/dist/vue.esm-browser.js +2046 -1573
- package/dist/vue.esm-browser.prod.js +9 -9
- package/dist/vue.esm-bundler.js +2117 -1589
- package/dist/vue.global.js +1981 -1508
- package/dist/vue.global.prod.js +9 -9
- package/dist/vue.runtime.esm-browser.js +8159 -1617
- package/dist/vue.runtime.esm-browser.prod.js +9 -3
- package/dist/vue.runtime.esm-bundler.js +8244 -1644
- package/dist/vue.runtime.global.js +8147 -1605
- package/dist/vue.runtime.global.prod.js +9 -3
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -41,7 +41,6 @@ The following workflow walks through the steps of migrating an actual Vue 2 app
|
|
|
41
41
|
### Installation
|
|
42
42
|
|
|
43
43
|
1. Upgrade tooling if applicable.
|
|
44
|
-
|
|
45
44
|
- If using custom webpack setup: Upgrade `vue-loader` to `^16.0.0`.
|
|
46
45
|
- If using `vue-cli`: upgrade to the latest `@vue/cli-service` with `vue upgrade`
|
|
47
46
|
- (Alternative) migrate to [Vite](https://vitejs.dev/) + [vite-plugin-vue2](https://github.com/underfin/vite-plugin-vue2). [[Example commit](https://github.com/vuejs/vue-hackernews-2.0/commit/565b948919eb58f22a32afca7e321b490cb3b074)]
|
|
@@ -160,7 +159,6 @@ The following workflow walks through the steps of migrating an actual Vue 2 app
|
|
|
160
159
|
5. After fixing the errors, the app should be able to run if it is not subject to the [limitations](#known-limitations) mentioned above.
|
|
161
160
|
|
|
162
161
|
You will likely see a LOT of warnings from both the command line and the browser console. Here are some general tips:
|
|
163
|
-
|
|
164
162
|
- You can filter for specific warnings in the browser console. It's a good idea to use the filter and focus on fixing one item at a time. You can also use negated filters like `-GLOBAL_MOUNT`.
|
|
165
163
|
|
|
166
164
|
- You can suppress specific deprecations via [compat configuration](#compat-configuration).
|