Skip to content

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

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
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

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

wants to merge 1 commit into from
+13,487 −6,242

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 24, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@changesets/cli (source) ^2.26.1 -> ^2.29.2 age adoption passing confidence
@emotion/css (source) ^11.10.6 -> ^11.13.5 age adoption passing confidence
@emotion/server (source) ^11.10.0 -> ^11.11.0 age adoption passing confidence
@nuxt/kit (source) ^3.4.2 -> ^3.17.1 age adoption passing confidence
@nuxt/module-builder ^0.3.0 -> ^0.8.4 age adoption passing confidence
@nuxt/schema (source) ^3.4.2 -> ^3.17.1 age adoption passing confidence
@nuxt/test-utils ^3.4.2 -> ^3.18.0 age adoption passing confidence
@nuxtjs/eslint-config-typescript ^12.0.0 -> ^12.1.0 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) ^5.59.0 -> ^5.62.0 age adoption passing confidence
eslint (source) ^8.39.0 -> ^8.57.1 age adoption passing confidence
eslint-plugin-promise ^6.1.1 -> ^6.6.0 age adoption passing confidence
nuxt (source) ^3.4.2 -> ^3.17.1 age adoption passing confidence
vitest (source) ^0.30.1 -> ^0.34.6 age adoption passing confidence

Release Notes

changesets/changesets (@​changesets/cli)

v2.29.2

Compare Source

Patch Changes

v2.29.1

Compare Source

Patch Changes

v2.29.0

Compare Source

Minor Changes

v2.28.1

Compare Source

Patch Changes

v2.28.0

Compare Source

Minor Changes
Patch Changes

v2.27.12

Compare Source

Patch Changes

v2.27.11

Compare Source

Patch Changes

v2.27.10

Compare Source

Patch Changes

v2.27.9

Compare Source

Patch Changes

v2.27.8

Compare Source

Patch Changes

v2.27.7

Compare Source

Patch Changes

v2.27.6

Compare Source

Patch Changes

v2.27.5

Compare Source

Patch Changes

v2.27.4

Compare Source

Patch Changes

v2.27.3

Compare Source

Patch Changes
  • #​1357 18c966a Thanks @​Andarist! - Fixed an issue with changeset status executed without since argument. It should now correctly use the configured base branch as the default value.

v2.27.2

Compare Source

Patch Changes

v2.27.1

Compare Source

Patch Changes
  • #​1267 86cfff1 Thanks @​Andarist! - Make ./bin.js available through package.json#exports to fix compatibility with changesets/action.

v2.27.0

Compare Source

Minor Changes
Patch Changes

v2.26.2

Compare Source

Patch Changes
emotion-js/emotion (@​emotion/css)

v11.13.5

Compare Source

Patch Changes

v11.13.4

Compare Source

Patch Changes

v11.13.0

Compare Source

Minor Changes

  • #​3198 d8ff8a5 Thanks @​Andarist! - Migrated away from relying on process.env.NODE_ENV checks to differentiate between production and development builds.

    Development builds (and other environment-specific builds) can be used by using proper conditions (see here). Most modern bundlers/frameworks already preconfigure those for the user so no action has to be taken.

    Default files should continue to work in all environments.

  • #​3215 a9f6912 Thanks @​Andarist! - Added edge-light and workerd conditions to package.json manifest to better serve users using Vercel Edge and Cloudflare Workers.

Patch Changes

v11.12.0

Compare Source

Minor Changes
  • #​2815 65a1eea Thanks @​srmagura! - Automatic labeling at runtime is now an opt-in feature. Define globalThis.EMOTION_RUNTIME_AUTO_LABEL = true before Emotion gets initialized to enable it.
Patch Changes

v11.11.2

Compare Source

Patch Changes
  • #​3057 8f665262 Thanks @​emmatown! - Fix @emotion/css/create-instance types in TypeScript module resolution modes that support the exports field

v11.11.0

Compare Source

Minor Changes
Patch Changes

v11.10.8

Compare Source

Patch Changes
nuxt/nuxt (@​nuxt/kit)

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 directo

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 changed the title chore(deps): update devdependency @typescript-eslint/eslint-plugin to ^5.59.1 chore(deps): update all non-major dependencies Apr 28, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 5523f1a to 72e1cf0 Compare May 3, 2023 21:10
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from f2b36bc to 3c37859 Compare May 8, 2023 21:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 49584a3 to c2ce777 Compare May 21, 2023 17:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 84f23e1 to 5a0b4c7 Compare May 29, 2023 19:26
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from d2918c1 to c66334c Compare June 6, 2023 02:17
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from bceba55 to 789d2ff Compare June 12, 2023 18:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from c5f53f1 to 9e613d2 Compare June 19, 2023 17:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from cd46bca to f4d26e1 Compare November 7, 2024 20:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 1b6d997 to 04f1807 Compare November 20, 2024 10:23
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 177d649 to e0e407c Compare December 6, 2024 14:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 6a94615 to b875928 Compare December 25, 2024 01:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 0094aac to cd6859e Compare January 12, 2025 00:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from b32e7e5 to c5f8419 Compare January 15, 2025 18:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from ffe5591 to 94e3be3 Compare January 29, 2025 10:39
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from a48a2eb to 0b14aa9 Compare February 21, 2025 13:35
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 914557e to 38890ff Compare March 8, 2025 21:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 38890ff to 4d6f8c1 Compare March 19, 2025 17:58
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4d6f8c1 to 57a6e60 Compare April 1, 2025 15:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from d1da3bb to 2355874 Compare April 16, 2025 20:22
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from ae80714 to 8157346 Compare April 29, 2025 01:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 8157346 to 58dde74 Compare May 3, 2025 17:13
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.
0 participants