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.

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

Bump vite and nuxt #38

Merged
merged 1 commit into from
Feb 2, 2024
Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 2, 2024

Bumps vite to 5.0.12 and updates ancestor dependency nuxt. These dependencies need to be updated together.

Updates vite from 5.0.11 to 5.0.12

Changelog

Sourced from vite's changelog.

5.0.12 (2024-01-19)

Commits

Updates nuxt from 3.9.3 to 3.10.0

Release notes

Sourced from nuxt's releases.

v3.10.0

3.10.0 is the next minor/feature release.

👀 Highlights

v3.10 comes quite close on the heels of v3.9, but it's packed with features and fixes. Here are a few highlights.

✨ Experimental shared asyncData when prerendering

When prerendering routes, we can end up refetching the same data over and over again. In Nuxt 2 it was possible to create a 'payload' which could be fetched once and then accessed in every page (and this is of course possible to do manually in Nuxt 3 - see this article).

With #24894, we are now able to do this automatically for you when prerendering. Your useAsyncData and useFetch calls will be deduplicated and cached between renders of your site.

export defineNuxtConfig({ 
  experimental: { 
    sharedPrerenderData: true
  } 
}) 

[!IMPORTANT]
It is particularly important to make sure that any unique key of your data is always resolvable to the same data. For example, if you are using useAsyncData to fetch data related to a particular page, you should provide a key that uniquely matches that data. (useFetch should do this automatically.)

👉 See full documentation.

🆔 SSR-safe accessible unique ID creation

We now ship a useId composable for generating SSR-safe unique IDs (#23368). This allows creating more accessible interfaces in your app. For example:

<script setup>
const emailId = useId()
const passwordId = useId()
</script>
&lt;template>
<form>
<label :for="emailId">Email</label>
<input
:id="emailId"
name="email"
type="email"
>
<label :for="passwordId">Password</label>
<input
:id="passwordId"
name="password"
type="password"
>
</tr></table>

... (truncated)

Commits
  • da3c502 v3.10.0
  • f1fe97f fix(nuxt): prioritise later items in pages:routerOptions hook (#25509)
  • b96fe1e chore: remove extra 'not' in warning message
  • 658a0ff feat(nuxt): useId composable (#23368)
  • 7d65769 chore(deps): update all non-major dependencies (main) (#25342)
  • 0d91e52 chore(nuxt): warn if NuxtPage is not used when pages enabled (#25490)
  • 407fde6 feat(nuxt): experimentally extract route metadata at build time (#25210)
  • 90ca0e8 feat(nuxt): slow down loading indicator when approaching 100% (#25119)
  • ecc4c8e fix(nuxt): prevent initial scroll jump when loading page (#25483)
  • 995acd9 feat(nuxt): allow controlling view transitions in page meta (#25264)
  • Additional commits viewable in compare view

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.

Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) to 5.0.12 and updates ancestor dependency [nuxt](https://github.com/nuxt/nuxt/tree/HEAD/packages/nuxt). These dependencies need to be updated together.


Updates `vite` from 5.0.11 to 5.0.12
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.0.12/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.0.12/packages/vite)

Updates `nuxt` from 3.9.3 to 3.10.0
- [Release notes](https://github.com/nuxt/nuxt/releases)
- [Commits](https://github.com/nuxt/nuxt/commits/v3.10.0/packages/nuxt)

---
updated-dependencies:
- dependency-name: vite
  dependency-type: indirect
- dependency-name: nuxt
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 2, 2024
@cyrilf cyrilf merged commit 8ece6cd into master Feb 2, 2024
0 of 5 checks passed
@cyrilf cyrilf deleted the dependabot/npm_and_yarn/vite-and-nuxt-5.0.12 branch February 2, 2024 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant