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

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

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 27, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@algolia/cache-in-memory ^4.14.2 -> ^4.24.0 age adoption passing confidence
@algolia/recommend (source) ^4.12.2 -> ^4.24.0 age adoption passing confidence
@algolia/requester-fetch ^4.23.2 -> ^4.24.0 age adoption passing confidence
@docsearch/css (source) ^3.0.0 -> ^3.9.0 age adoption passing confidence
@docsearch/js (source) ^3.0.0 -> ^3.9.0 age adoption passing confidence
@nuxt/kit (source) ^3.7.0 -> ^3.16.0 age adoption passing confidence
algoliasearch (source) ^4.11.0 -> ^4.24.0 age adoption passing confidence
metadata-scraper ^0.2.49 -> ^0.2.61 age adoption passing confidence
nuxt (source) 3.0.0-rc.4 -> 3.16.0 age adoption passing confidence
typescript (source) ^5.2.2 -> ^5.8.2 age adoption passing confidence
vue-instantsearch ^4.3.2 -> ^4.20.5 age adoption passing confidence

Release Notes

algolia/algoliasearch-client-javascript (@​algolia/cache-in-memory)

v4.24.0

Compare Source

v4.23.3

Compare Source

v4.23.2

Compare Source

v4.23.1

Compare Source

v4.23.0

Compare Source

v4.22.1

Compare Source

v4.22.0

Compare Source

Why

The trending-facets API only returns type string for facetValue.

A follow-up on #​1494 as other models return items/hits which are of type RecordWithObjectID

However, trending-facets model returns a list of TrendingFacetHit which (by definition) don't have an objectID property.

How

To simplify the code, we can remove the type argument TObject for trending-facets

Impact

If you're not using TypeScript or the trending-facets model, there is nothing to change. You can ignore the following.

Otherwise, you will need to remove the type argument passed to getTrendingFacets and the code goes from this:

type FacetType = {
  facetName: string;
  facetValue: string;
}
const { results } = await client.getTrendingFacets<FacetType>(/**/)

To this:

const { results } = await client.getTrendingFacets(/**/)

v4.21.1

Compare Source

v4.21.0

Compare Source

algolia/docsearch (@​docsearch/css)

v3.9.0

Compare Source

Features

3.8.3 (2025-01-21)

Bug Fixes

3.8.2 (2024-12-17)

Bug Fixes

3.8.1 (2024-12-16)

Bug Fixes

v3.8.3

Compare Source

Bug Fixes

v3.8.2

Compare Source

Bug Fixes

v3.8.1

Compare Source

Bug Fixes

v3.8.0

Compare Source

This version introduces a new type DocSearchTransformClient to allow the transformSearchClient to use either the lite client, or the full algoliasearch client.
Users are encouraged to use the lite client (import { liteClient } from 'algoliasearch/lite) to reduce bundle size.

Bug Fixes
Features

v3.7.0

Compare Source

Bug Fixes

3.6.3 (2024-10-31)

3.6.2 (2024-09-27)

Bug Fixes

3.6.1 (2024-07-16)

Bug Fixes

v3.6.3

Compare Source

v3.6.2

Compare Source

Bug Fixes

v3.6.1

Compare Source

Bug Fixes

v3.6.0

Compare Source

Bug Fixes
Features

3.5.2 (2023-08-11)

Fixes
  • Updates algoliasearch package version (cc90789)
  • Adds search-insights as options peer dependency (cc90789)

3.5.1 (2023-06-15)

Features
nuxt/nuxt (@​nuxt/kit)

v3.16.0

Compare Source

👀 Highlights

There's a lot in this one!

⚡️ A New New Nuxt

Say hello to create-nuxt, a new tool for starting Nuxt projects (big thanks to @​devgar for donating the package name)!

It's a streamlined version of nuxi init - just a sixth of the size and bundled as a single file with all dependencies inlined, to get you going as fast as possible.

Starting a new project is as simple as:

npm create nuxt

screenshot of create nuxt app

Special thanks to @​cmang for the beautiful ASCII-art. ❤️

Want to learn more about where we're headed with the Nuxt CLI? Check out our roadmap here, including our plans for an interactive modules selector.

🚀 Unhead v2

We've upgraded to unhead v2, the engine behind Nuxt's <head> management. This major version removes deprecations and improves how context works:

  • For Nuxt 3 users, we're shipping a legacy compatibility build so nothing breaks
  • The context implementation is now more direct via Nuxt itself
// Nuxt now re-exports composables while properly resolving the context
export function useHead(input, options = {}) {
  const unhead = injectHead(options.nuxt)
  return head(input, { head: unhead, ...options })
}

If you're using Unhead directly in your app, keep in mind:

  1. Import from Nuxt's auto-imports or #app/composables/head instead of @unhead/vue
  2. Importing directly from @unhead/vue might lose async context

Don't worry though - we've maintained backward compatibility in Nuxt 3, so most users won't need to change anything!

If you've opted into compatibilityVersion: 4, check out our upgrade guide for additional changes.

🔧 Devtools v2 Upgrade

Nuxt Devtools has leveled up to v2 (#​30889)!

You'll love the new features like custom editor selection, Discovery.js for inspecting resolved configs (perfect for debugging), the return of the schema generator, and slimmer dependencies.

One of our favorite improvements is the ability to track how modules modify your Nuxt configuration - giving you X-ray vision into what's happening under the hood.

👉 Discover all the details in the Nuxt DevTools release notes.

⚡️ Performance Improvements

We're continuing to make Nuxt faster, and there are a number of improvements in v3.16:

  1. Using exsolve for module resolution (#​31124) along with the rest of the unjs ecosystem (nitro, c12, pkg-types, and more) - which dramatically speeds up module resolution
  2. Smarter module resolution paths (#​31037) - prioritizes direct imports for better efficiency
  3. Eliminated duplicated Nitro alias resolution (#​31088) - leaner file handling
  4. Streamlined loadNuxt by skipping unnecessary resolution steps (#​31176) - faster startups
  5. Adopt oxc-parser for parsing in Nuxt plugins (#​30066)

All these speed boosts happen automatically - no configuration needed!

Shout out to CodSpeed with Vitest benchmarking to measure these improvements in CI - it has been really helpful.

To add some anecdotal evidence, my personal site at roe.dev loads 32% faster with v3.16, and nuxt.com is 28% faster. I hope you see similar results! ⚡️

🕰️ Delayed Hydration Support

We're very pleased to bring you native delayed/lazy hydration support (#​26468)! This lets you control exactly when components hydrate, which can improve initial load performance and time-to-interactive. We're leveraging Vue's built-in hydration strategies - check them out in the Vue docs.

<template>
  <!-- Hydrate when component becomes visible in viewport -->
  <LazyExpensiveComponent hydrate-on-visible />
  
  <!-- Hydrate when browser is idle -->
  <LazyHeavyComponent hydrate-on-idle />
  
  <!-- Hydrate on interaction (mouseover in this case) -->
  <LazyDropdown hydrate-on-interaction="mouseover" />
  
  <!-- Hydrate when media query matches -->
  <LazyMobileMenu hydrate-on-media-query="(max-width: 768px)" />
  
  <!-- Hydrate after a specific delay in milliseconds -->
  <LazyFooter :hydrate-after="2000" />
</template>

You can also listen for when hydration happens with the @hydrated event:

<LazyComponent hydrate-on-visible @&#8203;hydrated="onComponentHydrated" />

Learn more about lazy hydration in our components documentation.

🧩 Advanced Pages Configuration

You can now fine-tune which files Nuxt scans for pages (#​31090), giving you more control over your project structure:

export default defineNuxtConfig({
  pages: {
    // Filter specific files or directories
    pattern: ['**/*.vue'],
  }
})
🔍 Enhanced Debugging

We've made debugging with the debug option more flexible! Now you can enable just the debug logs you need (#​30578):

export default defineNuxtConfig({
  debug: {
    // Enable specific debugging features
    templates: true,
    modules: true,
    watchers: true,
    hooks: {
      client: true,
      server: true,
    },
    nitro: true,
    router: true,
    hydration: true,
  }
})

Or keep it simple with debug: true to enable all these debugging features.

🎨 Decorators Support

For the decorator fans out there (whoever you are!), we've added experimental support (#​27672). As with all experimental features, feedback is much appreciated.

export default defineNuxtConfig({
  experimental: {
    decorators: true
  }
})
function something (_method: () => unknown) {
  return () => 'decorated'
}

class SomeClass {
  @&#8203;something
  public someMethod () {
    return 'initial'
  }
}

const value = new SomeClass().someMethod()
// returns 'decorated'
📛 Named Layer Aliases

It's been much requested, and it's here! Auto-scanned local layers (from your ~~/layers directory) now automatically create aliases. You can access your ~~/layers/test layer via #layers/test (#​30948) - no configuration needed.

If you want named aliases for other layers, you can add a name to your layer configuration:

export default defineNuxtConfig({
  $meta: {
    name: 'example-layer',
  },
})

This creates the alias #layers/example-layer pointing to your layer - making imports cleaner and more intuitive.

🧪 Error Handling Improvements

We've greatly improved error messages and source tracking (#​31144):

  1. Better warnings for undefined useAsyncData calls with precise file location information
  2. Error pages now appear correctly on island page errors (#​31081)

Plus, we're now using Nitro's beautiful error handling (powered by youch) to provide more helpful error messages in the terminal, complete with stacktrace support.

Nitro now also automatically applies source maps without requiring extra Node options, and we set appropriate security headers when rendering error pages.

📦 Module Development Improvements

For module authors, we've added the ability to augment Nitro types with addTypeTemplate (#​31079):

// Inside your Nuxt module
export default defineNuxtModule({
  setup(options, nuxt) {
    addTypeTemplate({
      filename: 'types/my-module.d.ts',
      getContents: () => `
        declare module 'nitropack' {
          interface NitroRouteConfig {
            myCustomOption?: boolean
          }
        }
      `
    }, { nitro: true })
  }
})
⚙️ Nitro v2.11 Upgrade

We've upgraded to Nitro v2.11. There are so many improvements - more than I can cover in these brief release notes.

👉 Check out all the details in the Nitro v2.11.0 release notes.

📦 New unjs Major Versions

This release includes several major version upgrades from the unjs ecosystem, focused on performance and smaller bundle sizes through ESM-only distributions:

  • unenv upgraded to v2 (full rewrite)
  • db0 upgraded to v0.3 (ESM-only, native node:sql, improvements)
  • ohash upgraded to v2 (ESM-only, native node:crypto support, much faster)
  • untyped upgraded to v2 (ESM-only, smaller install size)
  • unimport upgraded to v4 (improvements)
  • c12 upgraded to v3 (ESM-only)
  • pathe upgraded to v2 (ESM-only)
  • cookie-es upgraded to v2 (ESM-only)
  • esbuild upgraded to v0.25
  • chokidar upgraded to v4

✅ Upgrading

As usual, 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: Upgrade @nuxt/devtools to v2 (#​30889)
  • nuxt: Granular debug options (#​30578)
  • nuxt: Add type hints for NuxtPage (#​30704)
  • nuxt: Support tracking changes to nuxt options by modules (#​30555)
  • nuxt: Allow disabling auto-imported polyfills (#​30332)
  • schema: Add runtime + internal type validation (#​30844)
  • kit,nuxt,schema: Support experimental decorators syntax (#​27672)
  • kit,nuxt: Allow multiple nuxts to run in one process (#​30510)
  • kit: Add named layer aliases (#​30948)
  • kit,nuxt,vite: directoryToURL to normalise paths (#​30986)
  • nuxt: Allow forcing start/set in loading indicator (#​30989)
  • nuxt: Allow specifying glob patterns for scanning pages/ (#​31090)
  • nuxt: Add types for default NuxtLink slot (#​31104)
  • nuxt: Delayed/lazy hydration support (#​26468)
  • vite: Add vite's modulepreload polyfill (#​31164)
  • nuxt: Show source file when warning about undefined useAsyncData (#​31144)
  • kit,nuxt: Augment nitro types with addTypeTemplate (#​31079)
  • kit,nuxt: Resolve template imports from originating module (#​31175)
  • nuxt: Use oxc-parser instead of esbuild + acorn (#​30066)
  • nuxt: Upgrade to unhead v2 (#​31169)
  • nuxt: Align nuxt error handling with nitro (#​31230)
🔥 Performance
  • nuxt: Remove duplicated nitro alias resolution (#​31088)
  • kit: Try non-subpath routes first to resolve nuxt modules (#​31037)
  • nuxt: Migrate to use exsolve for module resolution (#​31124)
  • kit: Skip extra module resolution step in loadNuxt (#​31176)
🩹 Fixes
  • nuxt: Ensure <NuxtLayout> fallback prop is typed (#​30832)
  • nuxt: Assign slot to be rendered for client components (#​30768)
  • nuxt,vite: Do not override vite import conditions (#​30887)
  • nuxt: Prevent keepalive cache reset (#​30807)
  • nuxt: Remove div wrapper in client-only pages (#​30425)
  • schema: Update type import to nitropack (aba75bd5a)
  • vite: Use resolveId from vite-node to resolve deps (#​30922)
  • schema: Normalise additional experimental options (63e0c342c)
  • nuxt: Delete existing properties in app config HMR (#​30918)
  • schema: Return null from resolve functions (d68e8ce57)
  • schema: Check if app.head.meta values are undefined (#​30959)
  • nuxt: Make shared/ directories available within layers (#​30843)
  • kit: Ensure nuxt is loaded from cwd rather than parent dir (#​30910)
  • ui-templates: Remove extra <pre> when rendering dev errors (9aab69ec4)
  • nuxt: Use tsx loader for jsx blocks as well (#​31014)
  • Remove unimplemented page:transition:start type (#​31040)
  • kit: Expose module dependency errors (#​31035)
  • nuxt: Deprioritise layer css imports (#​31020)
  • nuxt: Ensure provide / inject work in setup of defineNuxtComponent (#​30982)
  • nuxt: Decode URI components in cache driver methods (#​30973)
  • nuxt: Use _ for NuxtIsland name on server pages (#​31072)
  • nuxt: Use ohash to calculate legacy async data key without hash (#​31087)
  • nuxt,schema: Resolve shared dir from config (#​31091)
  • kit,schema: Set esbuild target for experimental decorators (#​31089)
  • nuxt: Set nuxt.options.pages to detected configuration (#​31101)
  • nuxt: Warn when definePageMeta does not receive an object (#​31156)
  • nuxt: Fix nitro import statements for v2 (151cf7d49)
  • nuxt: Update path to no-ssr middleware handler (a99c59fbd)
  • nuxt: Align type of custom navigate with vue-router (7a1934509)
  • nuxt: Show error page on island page error (#​31081)
  • nuxt: Do not render payloads if disabled, and correct regexp (#​31167)
  • nuxt: Add backwards-compatible serialisation for nuxt.options.pages (fa480e0a0)
  • ui-templates: Escape inline scripts correctly in ui templates (39c2b0a2c)
  • nuxt: Add back fallback nuxtlink type signature (a8856de59)
  • kit: Provide default extensions in resolveModule (6fb5c9c15)
  • nuxt: Provide default extensions in resolveTypePath (a0f9ddfe2)
  • nuxt: Strip query before generating payload url (34ddc2d2f)
  • schema: Resolve workspaceDir to closest git config (7a2fbce01)
  • kit: Include declaration files when resolving compilerOptions.paths (835e89404)
  • nuxt: Consolidate head component context (#​31209)
  • nuxt: Resolve shared externals to absolute paths (#​31227)
  • nuxt: Skip deep merge in dev mode for prototype keys (#​31205)
  • schema: Use RawVueCompilerOptions for unresolved tsconfig (#​31202)
  • nuxt: Ensure externals are resolved first (#​31235)
  • nuxt: Ensure we strip all chars in payload url (4f067f601)
  • nuxt: Exempt nitro from import protections (#​31246)
  • nuxt: Normalise error url to pathname (87b69c9ae)
  • nuxt: Ensure head components are reactive (#​31248)
  • nuxt: Preserve query/hash when calling navigateTo with replace (#​31244)
  • nuxt: Apply ignore rules to nitro devStorage (#​31233)
  • nuxt: Fall back to wasm if oxc native bindings are missing (#​31190)
  • nuxt: Pass useFetch function name on server for warning (#​31213)
  • vite: Prevent overriding server build chunks (89a29e760)
  • nuxt: Strip query in x-nitro-prerender header (2476cab9a)
💅 Refactors
  • nuxt: Prefer logical assignment operators (#​31004)
  • nuxt: Use isEqual from ohash/utils (2e27cd30c)
  • nuxt: Update to noScripts route rule (#​31083)
  • nuxt: Re-organize internal runtime/nitro files (#​31131)
  • nuxt: Explicitly type internal request fetch (54cb80319)
  • nuxt: Use relative imports (1bce3dc3b)
  • nuxt: Early return island response (#​31094)
📖 Documentation
  • Tiny typo (#​30799)
  • Fix typo (#​30817)
  • Remove backslashes in spaLoadingTemplate example (#​30830)
  • Update path to nuxt binary (8992c4ea0)
  • Add nuxt lifecycle (#​30726)
  • Add additional information about NuxtPage (#​30781)
  • Improve navigateTo docs with clearer structure and examples (#​30876)
  • Add auto import info about shared utils (#​30858)
  • Fix typo and improve data fetching examples (#​30935)
  • Clarify that local layers are scanned from rootDir (27e356fe6)
  • Fix typo (#​30963)
  • Update links to unhead sources (6c520ef74)
  • Fix typo (#​30971)
  • Add tips on how to override layers aliases (#​30970)
  • Add description for vue:setup and app:data:refresh hooks (#​31001)
  • Mention requirement to wrap middleware in defineNuxtRouteMiddleware (#​31005)
  • Add port option to preview command (#​30999)
  • Remove link to deleted nuxt 2 section (#​31077)
  • Link to the scripts releases page (#​31095)
  • Add .nuxtrc documentation (#​31093)
  • Fix typo in example command (#​31112)
  • Explain why headers not forwarded when using $fetch on the server (#​31114)
  • Fix links to nitro directory structure (5a696176d)
  • Update to use create nuxt command (fe82af4c9)
  • Update getCachedData types (#​31208)
  • Update code example for nightly release to default to 3x (a243f8fcf)
  • Clarify lifecycle behavior of <NuxtPage> during page changes (#​31116)
  • Mention workaround for typedPages in unhoisted pnpm setups (#​31262)
📦 Build
  • nuxt: Add subpath imports for type support (8ef3fcc4d)
🏡 Chore
✅ Tests

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 2 times, most recently from 4ede3ed to e24c2e4 Compare October 31, 2023 14:55
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from e24c2e4 to 2404e69 Compare November 6, 2023 13:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 4939e99 to 6e5ee82 Compare November 20, 2023 22:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 72b21ad to 8365153 Compare December 12, 2023 15:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 46e1e4e to 7861d97 Compare December 19, 2023 16:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7861d97 to 44a8a8f Compare December 25, 2023 18:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 9adb81d to 5447b94 Compare January 9, 2024 11:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from b5289f7 to a890cbc Compare January 17, 2024 14:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from aceaa03 to 99ec04b Compare January 30, 2024 16:27
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 15d78fb to 2427592 Compare February 6, 2024 15:45
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 9245612 to beb9c91 Compare February 14, 2024 16:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 4504c28 to 4c3039d Compare February 28, 2024 17:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 2d00842 to 7b70c31 Compare March 7, 2024 01:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 048b33d to 43df840 Compare October 24, 2024 14:06
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 585cef9 to 7923d26 Compare November 6, 2024 14:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 03219eb to 1787ca2 Compare November 14, 2024 11:32
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 4c78884 to cb68b8f Compare November 22, 2024 17:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from b02fd88 to 52ee6e9 Compare December 17, 2024 17:28
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 52ee6e9 to bb61061 Compare December 25, 2024 01:02
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 7368a0b to 3e3e19c Compare January 8, 2025 20:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 6f06302 to 1db81b1 Compare January 21, 2025 16:31
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from dcb8a0b to a89f83a Compare January 29, 2025 10:31
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a89f83a to 463e7eb Compare February 19, 2025 09:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 0dab11b to a1ac4dd Compare March 4, 2025 13:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a1ac4dd to a38193d Compare March 7, 2025 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants