⚠️ Dependabot is rebasing this PR ⚠️

If you make any changes to it yourself then they will take precedence over the rebase.

Bumps size-limit and @size-limit/preset-small-lib. These dependencies needed to be updated together. Updates size-limit from 4.5.7 to 4.6.0 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/ai/size-limit/blob/master/CHANGELOG.md">size-limit's changelog</a>.</em></p> <blockquote> <h1>Change Log</h1> <p>This project adheres to <a href="http://semver.org/">Semantic Versioning</a>.</p> <h2>4.6</h2> <ul> <li>Added <code>--hide-passed</code> argument (by Kristján Oddsson).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ai/size-limit/commit/ba62e7613d18ac55959095441bd90b92d84b31ff"><code>ba62e76</code></a> Release 4.6 version</li> <li><a href="https://github.com/ai/size-limit/commit/68329de3dc54c190cb2bde138e8b1338050706d1"><code>68329de</code></a> Add --hide-passed to help</li> <li><a href="https://github.com/ai/size-limit/commit/5ca7f7d744138b6925eb5b1af15ef61e515be254"><code>5ca7f7d</code></a> Update dependencis</li> <li><a href="https://github.com/ai/size-limit/commit/edb7d993d3a91ba3421c8edd7b13a1c8bcfc97e1"><code>edb7d99</code></a> Add <code>--hide-passed</code> flag to only output failed checks (<a href="https://github-redirect.dependabot.com/ai/size-limit/issues/199">#199</a>)</li> <li><a href="https://github.com/ai/size-limit/commit/84d9d8785d08528b1d1530780710337333d7462c"><code>84d9d87</code></a> Bump bl from 4.0.2 to 4.0.3 (<a href="https://github-redirect.dependabot.com/ai/size-limit/issues/198">#198</a>)</li> <li><a href="https://github.com/ai/size-limit/commit/659e2d08a090b249f5f0b3e1af2814b8f4ded8b5"><code>659e2d0</code></a> Stabilize tests</li> <li>See full diff in <a href="https://github.com/ai/size-limit/compare/4.5.7...4.6.0">compare view</a></li> </ul> </details> <br />

Updates @size-limit/preset-small-lib from 4.5.7 to 4.6.0 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/ai/size-limit/blob/master/CHANGELOG.md">@size-limit/preset-small-lib's changelog</a>.</em></p> <blockquote> <h1>Change Log</h1> <p>This project adheres to <a href="http://semver.org/">Semantic Versioning</a>.</p> <h2>4.6</h2> <ul> <li>Added <code>--hide-passed</code> argument (by Kristján Oddsson).</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ai/size-limit/commit/ba62e7613d18ac55959095441bd90b92d84b31ff"><code>ba62e76</code></a> Release 4.6 version</li> <li><a href="https://github.com/ai/size-limit/commit/68329de3dc54c190cb2bde138e8b1338050706d1"><code>68329de</code></a> Add --hide-passed to help</li> <li><a href="https://github.com/ai/size-limit/commit/5ca7f7d744138b6925eb5b1af15ef61e515be254"><code>5ca7f7d</code></a> Update dependencis</li> <li><a href="https://github.com/ai/size-limit/commit/edb7d993d3a91ba3421c8edd7b13a1c8bcfc97e1"><code>edb7d99</code></a> Add <code>--hide-passed</code> flag to only output failed checks (<a href="https://github-redirect.dependabot.com/ai/size-limit/issues/199">#199</a>)</li> <li><a href="https://github.com/ai/size-limit/commit/84d9d8785d08528b1d1530780710337333d7462c"><code>84d9d87</code></a> Bump bl from 4.0.2 to 4.0.3 (<a href="https://github-redirect.dependabot.com/ai/size-limit/issues/198">#198</a>)</li> <li><a href="https://github.com/ai/size-limit/commit/659e2d08a090b249f5f0b3e1af2814b8f4ded8b5"><code>659e2d0</code></a> Stabilize tests</li> <li>See full diff in <a href="https://github.com/ai/size-limit/compare/4.5.7...4.6.0">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

Bumps node-fetch from 2.6.0 to 2.6.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/bitinn/node-fetch/releases">node-fetch's releases</a>.</em></p> <blockquote> <h2>v2.6.1</h2> <p><strong>This is an important security release. It is strongly recommended to update as soon as possible.</strong></p> <p>See <a href="https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md#v261">CHANGELOG</a> for details.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md">node-fetch's changelog</a>.</em></p> <blockquote> <h2>v2.6.1</h2> <p><strong>This is an important security release. It is strongly recommended to update as soon as possible.</strong></p> <ul> <li>Fix: honor the <code>size</code> option after following a redirect.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/node-fetch/node-fetch/commit/b5e2e41b2b50bf2997720d6125accaf0dd68c0ab"><code>b5e2e41</code></a> update version number</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/2358a6c2563d1730a0cdaccc197c611949f6a334"><code>2358a6c</code></a> Honor the <code>size</code> option after following a redirect and revert data uri support</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/8c197f8982a238b3c345c64b17bfa92e16b4f7c4"><code>8c197f8</code></a> docs: Fix typos and grammatical errors in README.md (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/686">#686</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/1e99050f944ac435fce26a9549eadcc2419a968a"><code>1e99050</code></a> fix: Change error message thrown with redirect mode set to error (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/653">#653</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/244e6f63d42025465796e3ca4ce813bf2c31fc5b"><code>244e6f6</code></a> docs: Show backers in README</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/6a5d192034a0f438551dffb6d2d8df2c00921d16"><code>6a5d192</code></a> fix: Properly parse meta tag when parameters are reversed (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/682">#682</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/47a24a03eb49a49d81b768892aee10074ed54a91"><code>47a24a0</code></a> chore: Add opencollective badge</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/7b136627c537cb24430b0310638c9177a85acee1"><code>7b13662</code></a> chore: Add funding link</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/5535c2ed478d418969ecfd60c16453462de2a53f"><code>5535c2e</code></a> fix: Check for global.fetch before binding it (<a href="https://github-redirect.dependabot.com/bitinn/node-fetch/issues/674">#674</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/1d5778ad0d910dbd1584fb407a186f5a0bc1ea22"><code>1d5778a</code></a> docs: Add Discord badge</li> <li>Additional commits viewable in <a href="https://github.com/bitinn/node-fetch/compare/v2.6.0...v2.6.1">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~akepinski">akepinski</a>, a new releaser for node-fetch since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Bumps @vue/test-utils from 2.0.0-beta.3 to 2.0.0-beta.4. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/vuejs/vue-test-utils/commits/HEAD/packages/test-utils">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

@fotijr I meant CSS, sorry, like postcss or any other plugin. Vue doesn't parse the CSS after all

@dependabot rebase

@dependabot rebase

@dependabot rebase

@dependabot rebase

@dependabot rebase

@dependabot rebase

@dependabot help!

@dependabot rebase

@dependabot rebase

@dependabot rebase

@dependabot rebase

@dependabot @recreate

I'm trying to use ESM file directly from unpkg.com. The problem is that pinia.esm.js and pinia.esm.min.js both include import { ref, watch, computed } from '@vue/composition-api';.

Is this intentional? I'm actually trying it with freshly published vue 3 build.

I see that @vue/composition-api is defined as global in rollup config. Maybe for vue 3 we'd need another build that doesn't rely on @vue/composition-api.

@dependabot rebase

@dependabot recreate

@dependabot rebase

Bumps rollup from 2.28.1 to 2.28.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rollup/rollup/releases">rollup's releases</a>.</em></p> <blockquote> <h2>v2.28.2</h2> <p><em>2020-09-24</em></p> <h3>Bug Fixes</h3> <ul> <li>Fix a source of possible variable name conflicts when using preserveModules with SystemJS (<a href="https://github-redirect.dependabot.com/rollup/rollup/issues/3796">#3796</a>)</li> </ul> <h3>Pull Requests</h3> <ul> <li><a href="https://github-redirect.dependabot.com/rollup/rollup/pull/3792">#3792</a>: add documentation for output.PreserveModulesRoot (<a href="https://github.com/davidroeca">@davidroeca</a>)</li> <li><a href="https://github-redirect.dependabot.com/rollup/rollup/pull/3796">#3796</a>: Fix SystemJS default variable conflict (<a href="https://github.com/lukastaegert">@lukastaegert</a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rollup/rollup/blob/master/CHANGELOG.md">rollup's changelog</a>.</em></p> <blockquote> <h2>2.28.2</h2> <p><em>2020-09-24</em></p> <h3>Bug Fixes</h3> <ul> <li>Fix a source of possible variable name conflicts when using preserveModules with SystemJS (<a href="https://github-redirect.dependabot.com/rollup/rollup/issues/3796">#3796</a>)</li> </ul> <h3>Pull Requests</h3> <ul> <li><a href="https://github-redirect.dependabot.com/rollup/rollup/pull/3792">#3792</a>: add documentation for output.PreserveModulesRoot (<a href="https://github.com/davidroeca">@davidroeca</a>)</li> <li><a href="https://github-redirect.dependabot.com/rollup/rollup/pull/3796">#3796</a>: Fix SystemJS default variable conflict (<a href="https://github.com/lukastaegert">@lukastaegert</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rollup/rollup/commit/351e1d02697df4e195d38d65dc384a3da1b711fc"><code>351e1d0</code></a> 2.28.2</li> <li><a href="https://github.com/rollup/rollup/commit/2535853d838846412b1a15cd0d8dc2fab7212ea4"><code>2535853</code></a> Update changelog</li> <li><a href="https://github.com/rollup/rollup/commit/72417f4b0c64cbbb44761e3519a4d175f4d99efb"><code>72417f4</code></a> Fix SystemJS default variable conflict (<a href="https://github-redirect.dependabot.com/rollup/rollup/issues/3796">#3796</a>)</li> <li><a href="https://github.com/rollup/rollup/commit/6a974a785d2248cf19d032e14ef33b156d947be2"><code>6a974a7</code></a> add documentation for output.PreserveModulesRoot (<a href="https://github-redirect.dependabot.com/rollup/rollup/issues/3792">#3792</a>)</li> <li>See full diff in <a href="https://github.com/rollup/rollup/compare/v2.28.1...v2.28.2">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

Bumps rollup-plugin-typescript2 from 0.27.2 to 0.27.3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ezolenko/rollup-plugin-typescript2/releases">rollup-plugin-typescript2's releases</a>.</em></p> <blockquote> <h2>0.27.3</h2> <p>PR <a href="https://github-redirect.dependabot.com/ezolenko/rollup-plugin-typescript2/issues/243">#243</a></p> <p>Updating dependencies</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ezolenko/rollup-plugin-typescript2/commit/2cace3fd80b3436b063bf8a7db246657c42c5c03"><code>2cace3f</code></a> - updating dependencies</li> <li><a href="https://github.com/ezolenko/rollup-plugin-typescript2/commit/c183d330239c90a797d4d1c6fed5a40c483794b9"><code>c183d33</code></a> stop roll() from failing if the new cache folder is not created (<a href="https://github-redirect.dependabot.com/ezolenko/rollup-plugin-typescript2/issues/243">#243</a>)</li> <li><a href="https://github.com/ezolenko/rollup-plugin-typescript2/commit/dcf59ac4882ffe7019387596518cfa66ab87910e"><code>dcf59ac</code></a> - package version</li> <li>See full diff in <a href="https://github.com/ezolenko/rollup-plugin-typescript2/compare/0.27.2...0.27.3">compare view</a></li> </ul> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

<!-- Please don't delete this template -->

Close #2606 v3.4.5 fixed a bug with redirections on SSR, I added the catch to the initial push since onReady should still catch the error

<!-- PULL REQUEST TEMPLATE --> <!-- (Update "[ ]" to "[x]" to check a box) -->

Summary

What kind of change does this PR introduce? (check at least one)

• [ ] Bugfix
• [ ] Feature
• [ ] Code style update
• [ ] Refactor
• [ ] Docs
• [ ] Build-related changes
• [ ] Other, please describe:

If changing the UI of default theme, please provide the before/after screenshot:

Does this PR introduce a breaking change? (check one)

• [ ] Yes
• [ ] No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• [ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)

You have tested in the following browsers: (Providing a detailed version will be better.)

• [ ] Chrome
• [ ] Firefox
• [ ] Safari
• [ ] Edge
• [ ] IE

If adding a new feature, the PR's description includes:

• [ ] A convincing reason for adding this feature
• [ ] Related documents have been updated
• [ ] Related tests have been updated

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

Version

3.0.0

Reproduction link

https://github.com/FrankFang/vue-bug-1

Steps to reproduce

1. git clone https://github.com/FrankFang/vue-bug-1.git
2. cd vue-bug-1
3. yarn
4. yarn dev
5. open http://127.0.0.1:3000

What is expected?

I expect the page reads Message from HelloWorld.vue Message from HelloWorld.vue

What is actually happening?

The page reads Message from HelloWorld.vue Message from App.vue

HelloWorld.vue and HelloWorldUsingSetup.vue should be consistent

<!-- generated by vue-issues. DO NOT REMOVE -->

You cannot have a prop and a data property (or any other property that is directly available through this or on the template, with the same name. There is already a warning on the console about duplicated names

What problem does this feature solve?

I struggle to encapsulate functionality into components, because it's difficult to access methods in the slot rendered in the parent`s scope.

Maybe we could add a possibility to bind the methods to the slot?

What does the proposed API look like?

Would this be an anti-pattern?

Child-Component:

<slot v-bind="this.methods" />
...
methods: {
  childMethod()
}

Usage:

<child-component v-slot:default="$" >
  {{  $.childMethod(someValue) }}>
<

<!-- generated by vue-issues. DO NOT REMOVE -->

Tou can still bind the methods on the slot. You should do it per case and be explicit. It's better not to expose methods on a slot but it might solve some use cases

I think the only one expected to work on a render function should be onTestedEvent

Version

2.6.11

Reproduction link

https://jsfiddle.net/Soviut/0nmfpz9h/4/

Steps to reproduce

• Note the component emits an $event along with an extra argument string
• Click the "no prevent" button
• Note that the message is passed and is displayed
• Click the "has prevent" button
• Note that the message is undefined and clears the display

Both buttons also log to the console for more detailed output.

What is expected?

Additional arguments would be passed when event modifiers are used.

What is actually happening?

Additional arguments are being ignored/removed.

<!-- generated by vue-issues. DO NOT REMOVE -->

Duplicate of https://github.com/vuejs/vue/issues/10867

Version

3.0.0

Reproduction link

https://github.com/fotijr/spacevg

Steps to reproduce

1. Remove the !important flag at this line.
2. Run yarn dev.
3. View the generated CSS and see that both liftoff and firstLanding animation names are in the CSS.
4. Run yarn build.
5. View the generated CSS, and see the animation is reduced to a shorthand of animation: 1s linear forwards liftoff;. Notably the firstLanding animation is now missing.

What is expected?

CSS should be functionally the same between development and builds.

What is actually happening?

firstLanding animation is not applied in the build. It appears to be lost when the build translates animation properties into shorthand format.

I worked around the issue by adding the !important flag in this PR. I disabled autoprefixer to verify it wasn't causing the issue.

Also, I know I'm using animations a bit differently. I wrote about why I built this and some Safari issues I had to work around.

<!-- generated by vue-issues. DO NOT REMOVE -->

This issue seems to be caused by one of the cas libs, so please open an issue there. You are also sharing your whole project as a reproduction which makes it really hard for us to check

createWebHistory wrong spelling

What problem does this feature solve?

https://github.com/vuejs/vue-router-next/blob/28b40746ddbd5af4d8f6518c4c9868f0d0599436/src/navigationGuards.ts#L258

What does the proposed API look like?

componentPromise = componentPromise.catch((err) => {
  console.error(err)
  return null
})

<!-- generated by vue-issues. DO NOT REMOVE -->

Version

4.0.0-beta.12

Reproduction link

https://github.com/JounQin/serverless-study/blob/master/src/router.ts#L11

Steps to reproduce

1. run yarn dev, works as expected with .then(Comp => Comp.default)
2. remove .then(Comp => Comp.default), [Vue warn]: Component is missing template or render function. will be logged from @vue/server-renderer, and no route content will be server rendered, and client side route will do the job

What is expected?

Without .then(Comp => Comp.default), the async route on sever should also work

What is actually happening?

Inconsistent between client and server

<!-- generated by vue-issues. DO NOT REMOVE -->

This is an upstream bug as commented in the linked issue. I added a test at 65c18db

Here is my package.json in vue cli 4.5.6

{
  "name": "test-app2",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "serve": "vue-cli-service serve",
    "build": "vue-cli-service build",
    "lint": "vue-cli-service lint"
  },
  "dependencies": {
    "bootstrap-vue": "^2.17.3",
    "core-js": "^3.6.5",
    "vue": "^3.0.0-0",
    "vue-router": "^4.0.0-0",
    "vuex": "^4.0.0-0"
  },
  "devDependencies": {
    "@vue/cli-plugin-babel": "~4.5.0",
    "@vue/cli-plugin-eslint": "~4.5.0",
    "@vue/cli-plugin-router": "~4.5.0",
    "@vue/cli-plugin-vuex": "~4.5.0",
    "@vue/cli-service": "~4.5.0",
    "@vue/compiler-sfc": "^3.0.0-0",
    "@vue/eslint-config-prettier": "^6.0.0",
    "babel-eslint": "^10.1.0",
    "eslint": "^6.7.2",
    "eslint-plugin-prettier": "^3.1.3",
    "eslint-plugin-vue": "^7.0.0-0",
    "node-sass": "^4.12.0",
    "prettier": "^1.19.1",
    "sass-loader": "^8.0.2"
  }
}

But when i install bootstrap by following the doc. It is showing this error

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.

What is this for?

Version

4.0.0-beta.12

Reproduction link

https://codesandbox.io/s/infallible-solomon-hoge9

What is expected?

Transition does not always happen on initial rendering of a node if there is no attribute "appear"

What is actually happening?

The transition is always performed on the initial render of the node.

<!-- generated by vue-issues. DO NOT REMOVE -->

This is expected and mentioned in the migration guide!

Thank you!

Version

4.0.0-beta.12

Reproduction link

https://jsfiddle.net/9tvd4hw6/ (simple example - not working using vue & vue-router next) https://jsfiddle.net/z9qsbrLh/2/ (advanced - not working using vue & vue-router next) https://jsfiddle.net/yor1f3q0/1/ (working example using vue next without vue-router next) https://jsfiddle.net/o5zL7sm4/ (working example using vue 2 & vue router 3)

Steps to reproduce

• Create a simple vue app inside a variable as a string with minimal VueRouter setup using CDN
• Ex. var myVueNextCodeWithRouter = <script src="unpkg.com/..."/><div id="app#>...</div><router-link to=".../>...<script/>...
• Store code in a variable using: var codeForIframe = 'data:text/html' + myVueNextCodeWithRouter;
• Append code as src to an iframe

<iframe id="hey"></iframe>
<script>
let code = 'data:text/html,' + encodeURIComponent(`
<script src="https://unpkg.com/[email protected]/dist/vue.global.js"></` + `script>
<script src="https://unpkg.com/[email protected]/dist/vue-router.global.js"></` + `script>
<div id="app">
  <p>
    <router-link to="/">Go to Home</router-link>
    <router-link to="/about">Go to About</router-link>
  </p>
  <router-view></router-view>
</div>
<script>
const Home = { template: '<div>Home</div>' }
const About = { template: '<div>About</div>' }

const routes = [
  { path: '/', component: Home },
  { path: '/about', component: About },
]

const router = VueRouter.createRouter({
  history: VueRouter.createWebHashHistory(),
  routes
})

const app = Vue.createApp({})
app.use(router)

app.mount('#app')
</` + `script>
`);
let iframe = document.getElementById('hey')
iframe.src = code
</script>

What is expected?

It should run the app in iframe with routing

What is actually happening?

It throws a warning, destroys the render process and displays the source code instead.

The app works fine in iframe using vue next without next VueRouter: https://jsfiddle.net/yor1f3q0/1/ It does also work with VueRouter v3 for both History and Hash mode: https://jsfiddle.net/o5zL7sm4/ This render method is used to isolate a Vue App in an iframe with source code reactivity for working with Vue Components with Visual editing of Vue components.

<!-- generated by vue-issues. DO NOT REMOVE -->

Version

3.4.4

Reproduction link

https://github.com/j0Shi82/vue-router-issue-3329

Steps to reproduce

• pull repo
• install nodejs
• run npm install or yarn install
• run npm run-script start or yarn run start
• navigate to http://localhost:8085/one

What is expected?

Shows http://localhost:8085/two

What is actually happening?

Server Error 500

This is a follow-up to https://github.com/vuejs/vue-router/issues/3329 with a working reproduction and a little more information about what is actually causing the issue.

I'm not sure this is a bug or just an edge case that you have to work around yourself. It's caused by combining SSR, async route components, and redirects within navigation guards. I tried dodging async routes on the server and only using them on the client bundle (to still get the benefit of code-splitting), but that led to hydration errors.

Possible workarounds are switching to static route components, avoiding redirects within navigation guards, or using the router.push api instead of next. In our own application we went for the third choice on the server, but had to add additional logic to prevent hydration errors and handle the history mode correctly.

Either way it might make sense to go over the official SSR guide to better communicate this issue.

<!-- generated by vue-issues. DO NOT REMOVE -->

Thanks!

Version

3.0.0

Reproduction link

https://codepen.io/none

Steps to reproduce

1. install @vue/server/renderer
2. use code as packages/server-render/readme.md shows
3. start koa server
4. TypeError: Cannot destructure property createComponentInstance of 'undefined' or 'null'. showed in terminal.

What is expected?

ssr success

What is actually happening?

ssrUtils is null so can't read https://github.com/vuejs/vue-next/blob/5ae7380b4a9144c6a2873d0181a0f21a9a090018/packages/server-renderer/src/render.ts#L32 from none

<!-- generated by vue-issues. DO NOT REMOVE -->

I tried the example on the readme and it doesn't throw an error. Please don't open issues without a reproduction

Version

3.0.0

Reproduction link

https://codepen.io/lolmedo/pen/qBZvxpQ

Steps to reproduce

VueJS 3 project created with Vue CLI, edited with Visual Studio Code.

This code: export default class Home extends Vue { message: string; constructor() { super(); this.message = ""; } }

Produces these runtime error messages in the browser: [Vue warn]: Unhandled error during execution of setup function at <Home onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< undefined > > at <RouterView> at <App> runtime-core.esm-bundler.js:38 [Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/vue-next at <Home onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< undefined > > at <RouterView> at <App> runtime-core.esm-bundler.js:38 Uncaught (in promise) TypeError: can't convert undefined to object VueImpl vue-class-component.esm-bundler.js:257 _createSuperInternal Babel Home Home.vue:14 setup vue-class-component.esm-bundler.js:340 callWithErrorHandling runtime-core.esm-bundler.js:154

What is expected?

Being able to use full typescript support with type definitions and variable initialization in the class constructor. This is supported in VueJS v2

What is actually happening?

Getting the following errors on browser: [Vue warn]: Unhandled error during execution of setup function at <Home onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< undefined > > at <RouterView> at <App> runtime-core.esm-bundler.js:38 [Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/vue-next at <Home onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< undefined > > at <RouterView> at <App> runtime-core.esm-bundler.js:38 Uncaught (in promise) TypeError: can't convert undefined to object VueImpl vue-class-component.esm-bundler.js:257 _createSuperInternal Babel Home Home.vue:14 setup vue-class-component.esm-bundler.js:340 callWithErrorHandling runtime-core.esm-bundler.js:154

<!-- generated by vue-issues. DO NOT REMOVE -->

Please open the bug in vue-class-component repository

I'm still learning about Vue 3, and try to use Vuefire for my upcoming projects. Then, I am experiencing with the official examples from vuejs.org (https://codesandbox.io/s/github/vuejs/vuejs.org/tree/master/src/v2/examples/vue-20-firebase-validation) which is using Vue 2. Then, I am trying to use Vue 3, but the binding function doesn't work:

update with latest packages <script src="https://unpkg.com/vue@next"></script> <script src="https://unpkg.com/[email protected]/dist/vuefire.js"></script> <script src="https://www.gstatic.com/firebasejs/7.2.1/firebase.js"></script>

then <script> var emailRE = /^(([^<>()[\]\\.,;:\s@\"]+(\.[^<>()[\]\\.,;:\s@\"]+)*)|(\".+\"))@((\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\])|(([a-zA-Z\-0-9]+\.)+[a-zA-Z]{2,}))$/; // Setup Firebase var config = { apiKey: "AIzaSyAi_yuJciPXLFr_PYPeU3eTvtXf8jbJ8zw", authDomain: "vue-demo-537e6.firebaseapp.com", databaseURL: "https://vue-demo-537e6.firebaseio.com" }; firebase.initializeApp(config); var usersRef = firebase.database().ref("users"); // create Vue app const app = createApp({ // initial data data() { return { newUser: { name: "", email: "" } }, users: [] }, // firebase binding // https://github.com/vuejs/vuefire firebase: { users: usersRef }, // computed property for form validation state computed: { validation: function () { return { name: !!this.newUser.name.trim(), email: emailRE.test(this.newUser.email) }; }, isValid: function () { var validation = this.validation; return Object.keys(validation).every(function (key) { return validation[key]; }); } }, // methods methods: { addUser: function () { if (this.isValid) { usersRef.push(this.newUser); this.newUser.name = ""; this.newUser.email = ""; } }, removeUser: function (user) { usersRef.child(user[".key"]).remove(); } } }).mount("#app");

Thanks for your reading

I have started developing it but it isn't finished. It will probably be out in the following week. I have the work on a private repository before moving it to a different branch on this repo