Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Snyk] Upgrade vue-router from 3.0.2 to 3.1.2 #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Upgrade vue-router from 3.0.2 to 3.1.2 #2

wants to merge 1 commit into from

Conversation

snyk-bot
Copy link

Snyk have raised this PR to upgrade vue-router from 3.0.2 to 3.1.2.

  • The recommended version is 8 versions ahead of your current version.
  • The recommended version was released 22 days ago, on 2019-08-08.
Release notes

from vue-router GitHub Release Notes

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

The path of the RouteConfig is the same as the alias content, which will cause an infinite loop. router.resolve does not use current route by default Scroll behavior: hash that starts with number Hash mode places # at incorrect location in URL if current query parameters exist on page load implicit params ({ name: 'sub-route' }) don't update when navigating between nested routes
Catch all route with prefix throw Expected "0" to be defined nested router-view renders incorrect component with wrapping keep-alive at root beforeRouteEnter hook's cb is not called (same component across diffrent routes and keep-alive applied ) Typescript: Location interface typing for query should include null abstract mode's router.back() fails if there are 2 consecutive same routes in history stack
1 participant
@snyk-bot