Skip to content

Update all non-major dependencies #64

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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 25, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@babel/core (source) 7.26.10 -> 7.27.1 age adoption passing confidence devDependencies minor
@fluent/bundle (source) 0.18.0 -> 0.19.1 age adoption passing confidence dependencies minor
@fluent/bundle (source) ^0.18.0 -> ^0.19.0 age adoption passing confidence dependencies minor
@vue/compiler-core (source) 3.5.13 -> 3.5.14 age adoption passing confidence devDependencies patch
@vue/compiler-sfc (source) 3.5.13 -> 3.5.14 age adoption passing confidence devDependencies patch
actions/setup-node v4.3.0 -> v4.4.0 age adoption passing confidence action minor
core-js (source) 3.41.0 -> 3.42.0 age adoption passing confidence dependencies minor
nuxt (source) 3.16.1 -> 3.17.4 age adoption passing confidence dependencies minor
typescript (source) 5.8.2 -> 5.8.3 age adoption passing confidence devDependencies patch
vue (source) 3.5.13 -> 3.5.14 age adoption passing confidence dependencies patch
vue-router 4.5.0 -> 4.5.1 age adoption passing confidence dependencies patch
vue-tsc (source) 2.2.8 -> 2.2.10 age adoption passing confidence devDependencies patch
webpack 5.98.0 -> 5.99.9 age adoption passing confidence devDependencies minor
webpack-dev-server 5.2.0 -> 5.2.1 age adoption passing confidence devDependencies patch

Release Notes

babel/babel (@​babel/core)

v7.27.1

Compare Source

👓 Spec Compliance
🐛 Bug Fix
  • babel-plugin-proposal-destructuring-private, babel-plugin-proposal-do-expressions, babel-traverse
  • babel-helper-wrap-function, babel-plugin-transform-async-to-generator
  • babel-helper-remap-async-to-generator, babel-plugin-transform-async-to-generator
  • babel-helper-fixtures, babel-parser
  • babel-generator, babel-parser
    • #​17226 Fill optional AST properties when both estree and typescript parser plugin are enabled (Part 2) (@​JLHwung)
  • babel-parser
  • babel-compat-data, babel-preset-env
  • babel-traverse
  • babel-generator
💅 Polish
  • babel-plugin-bugfix-v8-spread-parameters-in-optional-chaining, babel-plugin-proposal-decorators, babel-plugin-transform-arrow-functions, babel-plugin-transform-class-properties, babel-plugin-transform-destructuring, babel-plugin-transform-object-rest-spread, babel-plugin-transform-optional-chaining, babel-plugin-transform-parameters, babel-traverse
🏠 Internal
  • babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • babel-compat-data, babel-preset-env
  • babel-compat-data, babel-standalone
  • Other
  • babel-register
  • babel-cli, babel-compat-data, babel-core, babel-generator, babel-helper-compilation-targets, babel-helper-fixtures, babel-helper-module-imports, babel-helper-module-transforms, babel-helper-plugin-test-runner, babel-helper-transform-fixture-test-runner, babel-helpers, babel-node, babel-parser, babel-plugin-transform-modules-amd, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-systemjs, babel-plugin-transform-modules-umd, babel-plugin-transform-react-display-name, babel-plugin-transform-regenerator, babel-plugin-transform-runtime, babel-plugin-transform-typeof-symbol, babel-plugin-transform-typescript, babel-preset-env, babel-register, babel-standalone, babel-types
  • babel-plugin-transform-regenerator
  • babel-helpers, babel-plugin-transform-async-generator-functions, babel-plugin-transform-regenerator, babel-preset-env, babel-runtime-corejs3
  • babel-helpers, babel-plugin-transform-regenerator
  • babel-helpers
🔬 Output optimization
  • babel-helpers, babel-plugin-transform-modules-commonjs, babel-runtime-corejs3
  • babel-helpers, babel-plugin-transform-async-generator-functions, babel-plugin-transform-regenerator, babel-preset-env, babel-runtime-corejs3
projectfluent/fluent.js (@​fluent/bundle)

v0.19.1: 2025-04-02

Compare Source

@​fluent/bundle 0.19.1
  • Fix FluentDateTime and FluentNumber primitive conversions (#​641)

v0.19.0: 2025-03-25

Compare Source

@​fluent/bundle 0.19.0
  • Add Temporal support (#​636)
  • Require Node.js 18 or later
vuejs/core (@​vue/compiler-core)

v3.5.14

Compare Source

Bug Fixes
Features
actions/setup-node (actions/setup-node)

v4.4.0

Compare Source

What's Changed
Bug fixes:
Enhancement:
Dependency update:
New Contributors

Full Changelogactions/setup-node@v4...v4.4.0

zloirock/core-js (core-js)

v3.42.0

Compare Source

  • Changes v3.41.0...v3.42.0 (142 commits)
  • Map upsert proposal:
    • Moved to stage 2.7, April 2025 TC39 meeting
    • Validation order of WeakMap.prototype.getOrInsertComputed updated following tc39/proposal-upsert#79
    • Built-ins:
      • Map.prototype.getOrInsert
      • Map.prototype.getOrInsertComputed
      • WeakMap.prototype.getOrInsert
      • WeakMap.prototype.getOrInsertComputed
  • Don't call well-known Symbol methods for RegExp on primitive values following tc39/ecma262#3009:
    • For avoid performance regression, temporarily, only in own core-js implementations
    • Built-ins:
      • String.prototype.matchAll
      • String.prototype.match
      • String.prototype.replaceAll
      • String.prototype.replace
      • String.prototype.search
      • String.prototype.split
  • Added workaround for the Uint8Array.prototype.setFromBase64 bug in some of Linux builds of WebKit
  • Implemented early-error iterator closing following tc39/ecma262#3467, including fix of a WebKit bug, in the following methods:
    • Iterator.prototype.drop
    • Iterator.prototype.every
    • Iterator.prototype.filter
    • Iterator.prototype.find
    • Iterator.prototype.flatMap
    • Iterator.prototype.forEach
    • Iterator.prototype.map
    • Iterator.prototype.reduce
    • Iterator.prototype.some
    • Iterator.prototype.take
  • Fixed missing forced replacement of AsyncIterator helpers
  • Added closing of sync iterator when async wrapper yields a rejection following tc39/ecma262#2600. Affected methods:
  • Added detection for throwing on undefined initial parameter in Iterator.prototype.reduce (see WebKit bug)
  • core-js-compat and core-js-builder API:
    • Added 'intersect' support for targets.esmodules (Babel 7 behavior)
    • Fixed handling of targets.esmodules: true (Babel 7 behavior)
  • Compat data improvements:
nuxt/nuxt (nuxt)

v3.17.4

Compare Source

3.17.4 is a regularly-scheduled patch release.

✅ Upgrading

Our recommendation for upgrading is to run:

npx nuxi@latest upgrade --dedupe

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

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Use Set for circular dep plugin (#​32110)
  • Refactor Array.includes checks to use Sets (#​32133)
  • nuxt: Use shallowRef for primitive values (#​32152)
  • nuxt: Skip route rules processing for empty child array (#​32166)
  • nuxt: Use Intl.Collator instead of localeCompare (#​32167)
🩹 Fixes
  • nuxt: Do not await lazy asyncData inside <ClientOnly> (#​32101)
  • nuxt: Respect cachedData with multiple asyncData calls (#​32099)
  • nuxt: Clear async data after a tick (#​32096)
  • nuxt: Support reactive keys in useLazyAsyncData (#​32092)
  • rspack: Use ts-checker-rspack-plugin (#​32115)
  • nuxt: Clear previous head in island-renderer (#​32100)
  • nuxt: Handle virtual files prefixed with / (#​32129)
  • schema: Remove nitro options from DeepPartial (#​31990)
  • nuxt: Ensure legacy async data remains reactive (#​32134)
  • nuxt: Pass attrs down to single child of <ClientOnly> (#​32131)
  • nuxt: Fix merge conflicts (7044450d4)
  • nuxt: Clone vnode when passing attrs down to client-only (b3acf0c78)
  • vite: Do not replace global with globalThis (#​32130)
  • nuxt: Suppress client-side errors by crawlers (#​32137)
  • nuxt: Use fresh route when <NuxtLayout> first renders (#​24673)
  • nuxt: Add additional logging when skipping error page for bot (68c270083)
  • nuxt: Add watch paths outside srcDir to parcel strategy (#​32139)
📖 Documentation
  • Use emphasis instead of quotes (#​32078)
  • Update useNuxtData default return to undefined (#​32054)
  • Capitalise headings (#​32095)
  • Prefix imports.dirs with alias (0dbf314d9)
  • Mention node v20 is minimum requirement for nuxt setup (#​32148)
  • Use more descriptive link text (d0b1b9d35)
🏡 Chore
✅ Tests
  • Add universal routing tests + clean up output (64178b6f4)
  • nuxt: Add unit tests for watch strategies (#​32138)
  • Resolve watch path (8fb562c04)
  • Use fake timers instead of setTimeout mock (#​32142)
🤖 CI
❤️ Contributors

v3.17.3

Compare Source

3.17.3 is a regularly-scheduled patch release.

✅ Upgrading

Our recommendation for upgrading is to run:

npx nuxi@latest upgrade --dedupe

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

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Pre-calculate extension glob before app resolution (#​32052)
  • nuxt: Improve islands client components chunks (#​32015)
🩹 Fixes
  • nuxt: Preload async layouts (#​32002)
  • nuxt: Handle File within FormData (#​32013)
  • schema: Respect user-provided ignore patterns (#​32020)
  • nuxt: Allow loading virtual files with query params (#​32022)
  • nuxt: Don't use reactive key for useFetch with watch: false (#​32019)
  • nuxt: Do not clear data if custom getCachedData is provided (#​32003)
  • nuxt: Provide nuxtApp for asyncData functions run on server (#​32038)
  • vite: Strip queries when skipping vite transform middleware (#​32041)
  • nuxt: Sort hash sources and files (#​32048)
  • nuxt: Do not suppress chunk import error (#​32064)
💅 Refactors
  • nuxt: Directly access initialised asyncData (e779d6cd5)
📖 Documentation
🤖 CI
  • Convert bug/enhancement labels to issue types (3ff743fe0)
  • Update payload for issue types (791e5f443)
❤️ Contributors

v3.17.2

Compare Source

3.17.2 is a regularly-scheduled patch release.

✅ Upgrading

Our recommendation for upgrading is to run:

npx nuxi@latest upgrade --dedupe

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

👉 Changelog

compare changes

🔥 Performance
  • nuxt: Tree-shake router's handleHotUpdate in production (#​31971)
🩹 Fixes
  • nuxt: Ensure asyncData is initialised before effects run (#​31946)
  • nuxt: Skip view transition if user agent provides one before defining transition (#​31945)
  • nuxt: Improve hashing for complex body in useFetch (#​31963)
  • nuxt: Immediately call asyncData within client-only components (#​31964)
  • nuxt: Don't render errors if event is already handled (#​31966)
  • nuxt: Track whether need to reinit asyncData separately from deps (#​31965)
  • nuxt: Preserve params/meta/matched with universal router (#​31950)
  • nuxt: Respect scroll behavior set by scrollToTop (#​31914)
  • nuxt: Load live data from vfs even if a file exists in buildDir (#​31969)
  • nuxt: Short circuit middleware when validate returns false (#​31967)
  • nuxt: Ensure useAsyncData reactive to key changes when immediate: false (#​31987)
  • nuxt: Resolve real paths imported into virtual files (0bb07f129)
  • webpack: Broaden WarningFilter type (2a79dbd68)
  • schema: Broaden warningIgnoreFilters (a62e808ac)
📖 Documentation
🏡 Chore
✅ Tests
🤖 CI
  • Run docs workflow against pull requests (08f968903)
  • Run tests against node v20 (3c97d3493)
❤️ Contributors

v3.17.1

Compare Source

3.17.1 is the next patch release.

✅ Upgrading

Our recommendation for upgrading is to run:

npx nuxi@latest upgrade --dedupe

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

👉 Changelog

compare changes

🩹 Fixes
  • nuxt: Check if match exists with new unplugin filter (#​31929)
  • nuxt: Reinitialise stale async data (#​31940)
  • nuxt: Skip view transition if user agent is providing one (#​31938)
  • nuxt: Trigger execute when non-immediate fetch key changes (#​31941)
  • nuxt: Don't redirect when route has trailing slash (#​31902)
  • ui-templates: Use escapeHTML from vue (8e4b8d62f)
  • schema: Add @vue/shared dependency (7d445c963)
📦 Build
  • Copy README/LICENSE from repo root (8e287d556)
🏡 Chore
✅ Tests
❤️ Contributors

v3.17.0

Compare Source

👀 Highlights

This release brings a major reworking of the async data layer, a new built-in component, better warnings, and performance improvements!

📊 Data Fetching Improvements

A major reorganization of Nuxt's data fetching layer brings significant improvements to useAsyncData and useFetch.

Although we have aimed to maintain backward compatibility and put breaking changes behind the experimental.granularCachedData flag (disabled by default), we recommend testing your application thoroughly after upgrading. You can also disable experimental.purgeCachedData to revert to the previous behavior if you are relying on cached data being available indefinitely after components using useAsyncData are unmounted.

👉 Read the the original PR for full details (#​31373), but here are a few highlights.

Consistent Data Across Components

All calls to useAsyncData or useFetch with the same key now share the underlying refs, ensuring consistency across your application:

<!-- ComponentA.vue -->
<script setup>
const { data: users, pending } = useAsyncData('users', fetchUsers)
</script>

<!-- ComponentB.vue -->
<script setup>
// This will reference the same data state as ComponentA
const { data: users, status } = useAsyncData('users', fetchUsers)
// When either component refreshes the data, both will update consistently
</script>

This solves various issues where components could have inconsistent data states.

Reactive Keys

You can now use computed refs, plain refs, or getter functions as keys:

const userId = ref('123')
const { data: user } = useAsyncData(
  computed(() => `user-${userId.value}`),
  () => fetchUser(userId.value)
)

// Changing the userId will automatically trigger a new data fetch
// and clean up the old data if no other components are using it
userId.value = '456'
Optimized Data Refetching

Multiple components watching the same data source will now trigger only a single data fetch when dependencies change:

// In multiple components:
const { data } = useAsyncData(
  'users', 
  () => $fetch(`/api/users?page=${route.query.page}`),
  { watch: [() => route.query.page] }
)

// When route.query.page changes, only one fetch operation will occur
// All components using this key will update simultaneously
🎭 Built-In Nuxt Components
<NuxtTime> - A new component for safe time display

We've added a new <NuxtTime> component for SSR-safe time display, which resolves hydration mismatches when working with dates (#​31876):

<template>
  <NuxtTime :datetime="Date.now()" />
</template>

The component accepts multiple time formats and gracefully handles both client and server rendering.

Enhanced <NuxtErrorBoundary>

The <NuxtErrorBoundary> component has been converted to a Single File Component and now exposes error and clearError from the component - as well as in the error slot types, giving you greater ability to handle errors in your templates and via useTemplateRef (#​31847):

<NuxtErrorBoundary @&#8203;error="handleError">
  <template #error="{ error, clearError }">
    <div>
      <p>{{ error.message }}</p>
      <button @&#8203;click="clearError">Try again</button>
    </div>
  </template>
  
  <!-- Content that might error -->
  <MyComponent />
</NuxtErrorBoundary>
🔗 Router Improvements

<NuxtLink> now accepts a trailingSlash prop, giving you more control over URL formatting (#​31820):

<NuxtLink to="/about" trailing-slash>About</NuxtLink>
<!-- Will render <a href="/about/"> -->
🔄 Loading Indicator Customization

You can now customize the loading indicator with new props directly on the component (#​31532):

  • hideDelay: Controls how long to wait before hiding the loading bar
  • resetDelay: Controls how long to wait before resetting loading indicator state
<template>
  <NuxtLoadingIndicator :hide-delay="500" :reset-delay="300" />
</template>
📚 Documentation as a Package

The Nuxt documentation is now available as an npm package! You can install @nuxt/docs to access the raw markdown and YAML content used to build the documentation website (#​31353).

💻 Developer Experience Improvements

We've added several warnings to help catch common mistakes:

  • Warning when server components don't have a root element #​31365
  • Warning when using the reserved runtimeConfig.app namespace #​31774
  • Warning when core auto-import presets are overridden #​29971
  • Error when definePageMeta is used more than once in a file #​31634
🔌 Enhanced Module Development

Module authors will be happy to know:

  • A new experimental.enforceModuleCompatibility allows Nuxt to throw an error when a module is loaded that isn't compatible with it (#​31657). It will be enabled by default in Nuxt v4.
  • You can now automatically register every component exported via named exports from a file with addComponentExports #​27155
🔥 Performance Improvements

Several performance improvements have been made:

  • Switched to tinyglobby for faster file globbing #​31668
  • Excluded .data directory from type-checking for faster builds #​31738
  • Improved tree-shaking by hoisting the purgeCachedData check #​31785

✅ Upgrading

Our recommendation for upgrading is to run:

npx nuxi@latest upgrade --dedupe

This refreshes your lockfile and pulls in all the latest dependencies that Nuxt relies on, especially from the unjs ecosystem.

👉 Changelog

compare changes

🚀 Enhancements
  • nuxt: Accept hideDelay and resetDelay props for loading indicator (#​31532)
  • nuxt: Warn server components need root element (#​31365)
  • docs: Publish raw markdown/yaml docs as @nuxt/docs (#​31353)
  • kit,nuxt: Pa

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f584cb1 to 6bfd824 Compare March 27, 2025 02:01
@renovate renovate bot changed the title Update dependency @fluent/bundle to v0.19.0 Update all non-major dependencies Mar 27, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from cf50fe1 to 3dd9bfc Compare April 7, 2025 22:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from dfffa98 to aa6c459 Compare April 14, 2025 03:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 47a7cad to 3efc050 Compare April 25, 2025 11:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 97b2e49 to e1c1cf8 Compare April 30, 2025 15:58
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from ac2f44d to 69410c1 Compare May 6, 2025 16:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 14183b5 to 94bd7aa Compare May 19, 2025 17:41
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 94bd7aa to d4b9022 Compare May 20, 2025 16:09
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d4b9022 to 6f632c7 Compare May 20, 2025 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

0 participants