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

chore(deps): update all non-major dependencies #2528

Merged
merged 1 commit into from
Feb 2, 2024
Merged

chore(deps): update all non-major dependencies #2528

merged 1 commit into from
Feb 2, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 26, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@iconify-json/ph ^1.1.10 -> ^1.1.11 age adoption passing confidence
@iconify-json/simple-icons ^1.1.89 -> ^1.1.90 age adoption passing confidence
@nuxt/kit (source) ^3.9.3 -> ^3.10.0 age adoption passing confidence
@nuxt/schema (source) 3.9.3 -> 3.10.0 age adoption passing confidence
@nuxt/test-utils 3.10.0 -> 3.11.0 age adoption passing confidence
@​nuxt/ui-pro ^0.7.3 -> ^0.7.5 age adoption passing confidence
@nuxtjs/tailwindcss ^6.11.1 -> ^6.11.2 age adoption passing confidence
husky ^9.0.6 -> ^9.0.10 age adoption passing confidence
lint-staged ^15.2.0 -> ^15.2.1 age adoption passing confidence
listhen ^1.5.6 -> ^1.6.0 age adoption passing confidence
nuxt (source) 3.9.3 -> 3.10.0 age adoption passing confidence
nuxt (source) ^3.9.3 -> ^3.10.0 age adoption passing confidence
pnpm (source) 8.14.3 -> 8.15.1 age adoption passing confidence
shikiji (source) ^0.10.1 -> ^0.10.2 age adoption passing confidence
vitest (source) ^1.2.1 -> ^1.2.2 age adoption passing confidence

Release Notes

nuxt/nuxt (@​nuxt/kit)

v3.10.0

Compare Source

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>

<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"
    >
  </form>
</template>
✍️ Extending app/router.options

It's now possible for module authors to inject their own router.options files (#​24922). The new pages:routerOptions hook allows module authors to do things like add custom scrollBehavior or add runtime augmenting of routes.

👉 See full documentation.

Client-side Node.js support

We now support (experimentally) polyfilling key Node.js built-ins (#​25028), just as we already do via Nitro on the server when deploying to non-Node environments.

That means that, within your client-side code, you can import directly from Node built-ins (node: and node imports are supported). However, nothing is globally injected for you, to avoid increasing your bundle size unnecessarily. You can either import them where needed.

import { Buffer } from 'node:buffer'
import process from 'node:process'

Or provide your own polyfill, for example, inside a Nuxt plugin.

// ~/plugins/node.client.ts
import { Buffer } from 'node:buffer'
import process from 'node:process'

globalThis.Buffer = Buffer
globalThis.process = process

export default defineNuxtPlugin({})

This should make life easier for users who are working with libraries without proper browser support. However, because of the risk in increasing your bundle unnecessarily, we would strongly urge users to choose other alternatives if at all possible.

🍪 Better cookie reactivity

We now allow you to opt-in to using the CookieStore. If browser support is present, this will then be used instead of a BroadcastChannel to update useCookie values reactively when the cookies are updated (#​25198).

This also comes paired with a new composable, refreshCookie which allows manually refreshing cookie values, such as after performing a request. See full documentation.

🏥 Detecting anti-patterns

In this release, we've also shipped a range of features to detect potential bugs and performance problems.

  • We now will throw an error if setInterval is used on server (#​25259).
  • We warn (in development only) if data fetch composables are used wrongly (#​25071), such as outside of a plugin or setup context.
  • We warn (in development only) if you are not using <NuxtPage /> but have the vue-router integration enabled (#​25490). (<RouterView /> should not be used on its own.)
🧂 Granular view transitions support

It's now possible to control view transitions support on a per-page basis, using definePageMeta (#​25264).

You need to have experimental view transitions support enabled first:

export default defineNuxtConfig({
  experimental: {
    viewTransition: true
  },
  app: {
    // you can disable them globally if necessary (they are enabled by default)
    viewTransition: false
  }
})

And you can opt in/out granularly:

// ~/pages/index.vue
<script setup lang="ts">
definePageMeta({
  viewTransition: false
})
</script>

Finally, Nuxt will not apply View Transitions if the user's browser matches prefers-reduced-motion: reduce (#​22292). You can set viewTransition: 'always'; it will then be up to you to respect the user's preference.

🏗️ Build-time route metadata

It's now possible to access routing metadata defined in definePageMeta at build-time, allowing modules and hooks to modify and change these values (#​25210).

export default defineNuxtConfig({
  experimental: {
    scanPageMeta: true
  }
})

Please, experiment with this and let us know how it works for you. We hope to improve performance and enable this by default in a future release so modules like @nuxtjs/i18n and others can provide a deeper integration with routing options set in definePageMeta.

📦 Bundler module resolution

With #​24837, we are now opting in to the TypeScript bundler resolution which should more closely resemble the actual way that we resolve subpath imports for modules in Nuxt projects.

'Bundler' module resolution is recommended by Vue and by Vite, but unfortunately there are still many packages that do not have the correct entries in their package.json.

As part of this, we opened 85 PRs across the ecosystem to test switching the default, and identified and fixed some issues.

If you need to switch off this behaviour, you can do so. However, please consider raising an issue (feel free to tag me in it) in the library or module's repo so it can be resolved at source.

export default defineNuxtConfig({
  future: {
    typescriptBundlerResolution: false
  }
})

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade --force

This will refresh your lockfile as well, and ensures that you pull in updates from other dependencies that Nuxt relies on, particularly in the unjs ecosystem.

-->

👉 Changelog

compare changes

🚀 Enhancements
  • nuxt: tryUseNuxtApp composable (#​25031)
  • nuxt: Add experimental sharedPrerenderData option (#​24894)
  • schema: Default to bundler module resolution (#​24837)
  • nuxt: Warn if data fetch composables are used wrongly (#​25071)
  • nuxt: Add pages:routerOptions hook (#​24922)
  • Experimental client-side Node.js compatibility (#​25028)
  • nuxt: Throw error if setInterval is used on server (#​25259)
  • nuxt: refreshCookie + experimental CookieStore support (#​25198)
  • nuxt: Allow controlling view transitions in page meta (#​25264)
  • nuxt: Slow down loading indicator when approaching 100% (#​25119)
  • nuxt: Experimentally extract route metadata at build time (#​25210)
  • nuxt: useId composable (#​23368)
🔥 Performance
  • vite: Avoid endsWith when checking for whitespace (#​24746)
🩹 Fixes
  • nuxt: Disable View Transitions if prefers-reduced-motion (#​22292)
  • nuxt: Add declaration file with correct node16 imports (#​25266)
  • nuxt: Allow omitting fallback in island response (#​25296)
  • schema: Remove defineModel option as it is now stable (#​25306)
  • nuxt: Overwrite island payload instead of merging (#​25299)
  • vite: Pass hidden sourcemap values to vite (#​25329)
  • nuxt: Use named import for lazy components (#​25286)
  • nuxt: Deprecate boolean values for dedupe (#​25334)
  • nuxt: Use default export for raw components (#​25282)
  • nuxt: Handle plugin dependencies with mixed load state (#​25318)
  • nuxt: Preserve instance.attrs in client-only components (#​25381)
  • nuxt: Stop tracking suspense when error hydrating page (#​25389)
  • nuxt: Add router.options files in definite order (#​25397)
  • nuxt: Do not rerun synchronous callOnce callbacks (#​25431)
  • nuxt: Remove dynamic nuxt-client within template code (#​25464)
  • nuxt: Add runtime check to filter plugins in dependsOn (#​25409)
  • nuxt: Improve global/payload error type with NuxtError (#​25398)
  • vite: Extract styles for shared chunks (#​25455)
  • nuxt: Avoid vue-router warning with routeRule redirect (#​25391)
  • nuxt: Improve return type of useRequestEvent (#​25480)
  • nuxt: Match nitro + nuxt useRuntimeConfig signatures (#​25440)
  • nuxt: Prevent initial scroll jump when loading page (#​25483)
  • nuxt: Prioritise later items in pages:routerOptions hook (#​25509)
💅 Refactors
  • nuxt: Remove currentRoute non-ref warning (#​25337)
📖 Documentation
  • Explain how to auto-install git layer deps (#​24250)
  • Fix eslint link (87641c867)
  • Fix typo (#​25326)
  • nuxt: Add @since annotations to exported composables (#​25086)
  • Add emphasis to useAsyncData explanation (#​25392)
  • Add separate docs page for error.vue (#​25320)
  • Add explanation about layout usage in error.vue (#​25396)
  • Use .cjs extension for ecosystem.config (#​25459)
  • Add fuller explanation in routeRules example of swr/isr (#​25436)
  • Warn that island client components don't support slots (#​25454)
  • Updated addPluginTemplate example to add filename property (#​25468)
  • Update link to vercel edge network overview (e01fb7ac3)
  • Remove unnecessary warning on sharedPrerenderData (b0f50bec1)
  • Add more documentation for pages:routerOptions (46b533671)
🏡 Chore
  • Fix typo in warning log (#​25265)
  • nuxt: Warn if NuxtPage is not used when pages enabled (#​25490)
  • Remove extra 'not' in warning message (b96fe1ece)
✅ Tests
🤖 CI
  • Only release from main repo (#​25354)
  • Label pull request based on type in title (#​25404)
  • Wrap PR base label in quotes (#​25432)
  • Update extracting PR labels' names (#​25437)
  • Skip adding PR labels if there are none to add (#​25475)
  • Update changelog with github tags/handles of users (60ab5deb0)
  • Import $fetch (a1fb399eb)
❤️ Contributors
nuxt/test-utils (@​nuxt/test-utils)

v3.11.0

Compare Source

compare changes

🚀 Enhancements
  • vitest-environment: Add support for in-source testing (#​651)
🩹 Fixes
  • runtime: Reset modules after nuxt setup runs (#​726)
✅ Tests
  • Add example of mocking vue-router (e293cea1)
  • Add example of mocking nuxt useRoute (fe465193)
❤️ Contributors
nuxt-modules/tailwindcss (@​nuxtjs/tailwindcss)

v6.11.2

Compare Source

compare changes

🩹 Fixes
  • viewer: Handle redirect and callback await, thank you danielroe :) (734ef1c)
📖 Documentation
❤️ Contributors
typicode/husky (husky)

v9.0.10

Compare Source

v9.0.9

Compare Source

v9.0.8

Compare Source

v9.0.7

Compare Source

okonet/lint-staged (lint-staged)

v15.2.1

Compare Source

Patch Changes
  • #​1387 e4023f6 Thanks @​iiroj! - Ignore stdin of spawned commands so that they don't get stuck waiting. Until now, lint-staged has used the default settings to spawn linter commands. This means the stdin of the spawned commands has accepted input, and essentially gotten stuck waiting. Now the stdin is ignored and commands will no longer get stuck. If you relied on this behavior, please open a new issue and describe how; the behavior has not been intended.
unjs/listhen (listhen)

v1.6.0

Compare Source

compare changes

🚀 Enhancements
  • Experimental websocket support (#​158)
🏡 Chore
  • Update lockfile (ebef2d1)
  • Remove ws from shared args for now (d115045)
❤️ Contributors
pnpm/pnpm (pnpm)

v8.15.1

Compare Source

Patch Changes

  • Use the object-hash library instead of node-object-hash for hashing keys of side-effects cache #​7591.
  • bundledDependencies should never be added to the lockfile with false as the value #​7576.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v8.15.0

Compare Source

Minor Changes

  • When the license field does not exist in package.json but a license file exists, try to match and extract the license name #​7530.

Patch Changes

  • Running pnpm update -r --latest will no longer downgrade prerelease dependencies #​7436.
  • --aggregate-output should work on scripts executed from the same project #​7556.
  • Prefer hard links over reflinks on Windows as they perform better #​7564.
  • Reduce the length of the side-effects cache key. Instead of saving a stringified object composed from the dependency versions of the package, use the hash calculated from the said object #​7563.
  • Throw an error if pnpm update --latest runs with arguments containing versions specs. For instance, pnpm update --latest foo@next is not allowed #​7567.
  • Don't fail in Windows CoW if the file already exists #​7554.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors
antfu/shikiji (shikiji)

v0.10.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
vitest-dev/vitest (vitest)

v1.2.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@cloudflare-pages Cloudflare Pages
Copy link

cloudflare-pages bot commented Jan 26, 2024 •
edited
Loading

Deploying with  Cloudflare Pages  Cloudflare Pages

Latest commit: 5475c16
Status: ✅  Deploy successful!
Preview URL: https://3ddc2cb9.nuxt-content-1il.pages.dev
Branch Preview URL: https://renovate-all-minor-patch.nuxt-content-1il.pages.dev

View logs

@renovate renovate bot changed the title chore(deps): update dependency shikiji to ^0.10.2 chore(deps): update all non-major dependencies Jan 26, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from 7b83ffd to 4c64bc0 Compare February 1, 2024 21:11
@farnabaz farnabaz merged commit d922f2e into main Feb 2, 2024
3 checks passed
@farnabaz farnabaz deleted the renovate/all-minor-patch branch February 2, 2024 13:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@farnabaz farnabaz farnabaz approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@farnabaz