Bump vite and nuxt in /Websites/browserbench.org/Speedometer3.1/resources/newssite/news-nuxt #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removes vite. It's no longer used after updating ancestor dependency nuxt. These dependencies need to be updated together.
Removes
vite
Updates
nuxt
from 3.5.2 to 3.19.1Release notes
Sourced from nuxt's releases.
... (truncated)
Commits
544a76f
v3.19.1cd33431
fix(nuxt): render relative importmap entry path if required (#33146)1035236
fix(nuxt): include core auto-imports fromimports:sources
in override warni...f37afc7
fix(nuxt): print route middleware path in warning (#33136)408a388
fix(nuxt): include trace in dev-timeuseRoute
usage warning (#33039)0d5696d
fix(nuxt): ignore #components import mapping inside packages that use it inte...2cd3b09
docs: add JSDoc fornavigateTo
(#21442)4acd3be
fix(nuxt): migrate to AST-aware tree-shaking + route injection (#33128)f88701b
fix(nuxt): prefer accessingglobalThis
overwindow
(#33125)e6d162c
fix(nuxt): correct relative path of auto imported components (#33122)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for nuxt since your current version.
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
.Dependabot commands and options
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 show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@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.