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 #3

Merged
merged 1 commit into from
Oct 29, 2023
Merged

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

merged 1 commit into from
Oct 29, 2023

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 29, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nuxt/content ^2.8.5 -> ^2.9.0 age adoption passing confidence
@nuxthq/studio (source) ^1.0.0 -> ^1.0.2 age adoption passing confidence
@nuxtjs/algolia ^1.9.0 -> ^1.10.0 age adoption passing confidence
@types/node (source) ^20.8.2 -> ^20.8.9 age adoption passing confidence
@vueuse/integrations (source) ^10.4.1 -> ^10.5.0 age adoption passing confidence
@vueuse/nuxt (source) ^10.4.1 -> ^10.5.0 age adoption passing confidence
eslint (source) ^8.50.0 -> ^8.52.0 age adoption passing confidence
focus-trap ^7.5.3 -> ^7.5.4 age adoption passing confidence
nuxt ^3.7.4 -> ^3.8.0 age adoption passing confidence
pnpm (source) 8.8.0 -> 8.10.0 age adoption passing confidence
vite-plugin-inspect ^0.7.40 -> ^0.7.41 age adoption passing confidence
vue (source) ^3.3.4 -> ^3.3.7 age adoption passing confidence

Release Notes

nuxt/content (@​nuxt/content)

v2.9.0

Compare Source

compare changes

🚀 Enhancements
🩹 Fixes
📖 Documentation
❤️ Contributors
nuxtlabs/studio.nuxt.com (@​nuxthq/studio)

v1.0.2

Compare Source

v1.0.1

Compare Source

nuxt-modules/algolia (@​nuxtjs/algolia)

v1.10.0: 1.10.0

Compare Source

1.10.0

This is a new minor update of the Algolia module for Nuxt with several features, bugfixes, and new docs.

✅ Migration Guide

This version includes ⚠️ breaking changes but don't worry, we have prepared migration guide for you 😉

In the previous version, DocSearch component had few props set by default like lang and langAttribute. This was causing bugs for users so instead of that we decided to remove them and give full control of the props to you.

Check out the documentation for it here

What's Changed

New Contributors

Full Changelog: nuxt-modules/algolia@v1.9.0...v1.10.0

vueuse/vueuse (@​vueuse/integrations)

v10.5.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
eslint/eslint (eslint)

v8.52.0

Compare Source

Features

  • 70648ee feat: report-unused-disable-directive to report unused eslint-enable (#​17611) (Yosuke Ota)

Bug Fixes

  • 5de9637 fix: Ensure shared references in rule configs are separated (#​17666) (Nicholas C. Zakas)
  • dcfe573 fix: add preceding semicolon in suggestions of no-object-constructor (#​17649) (Francesco Trotta)

Documentation

  • 476d58a docs: Add note about invalid CLI flags when using flat config. (#​17664) (Nicholas C. Zakas)
  • 660ed3a docs: Plugin flat config migration guide (#​17640) (Nicholas C. Zakas)
  • a58aa20 docs: fix examples for several rules (#​17645) (Milos Djermanovic)
  • 179929b docs: Remove trailing newline from the code of Playground links (#​17641) (Francesco Trotta)
  • f8e5c30 docs: Update README (GitHub Actions Bot)
  • b7ef2f3 docs: Enable pretty code formatter output (#​17635) (Nicholas C. Zakas)
  • 0bcb9a8 docs: Fix syntax errors in rule examples (#​17633) (Francesco Trotta)
  • 61b9083 docs: Make no-continue example code work (#​17643) (Zhongyuan Zhou)
  • 9fafe45 docs: upgrade to 11ty 2.0 (#​17632) (Percy Ma)
  • ff8e4bf docs: Update README (GitHub Actions Bot)
  • fab249a docs: Update README (GitHub Actions Bot)
  • 392305b docs: Update no-irregular-whitespace and fix examples (#​17626) (Francesco Trotta)
  • 6b8acfb docs: Add real whitespace to no-trailing-spaces examples (#​17630) (Francesco Trotta)
  • 1000187 docs: Fix examples in unicode-bom (#​17631) (Francesco Trotta)
  • 000290c docs: Update README (GitHub Actions Bot)

Chores

v8.51.0

Compare Source

Features

  • 0a9c433 feat: Add --no-warn-ignored CLI option for flat config (#​17569) (Domantas Petrauskas)
  • 977e67e feat: logical-assignment-operators to report expressions with 3 operands (#​17600) (Yosuke Ota)

Bug Fixes

  • f976b2f fix: make rule severity case-sensitive in flat config (#​17619) (Milos Djermanovic)
  • 0edfe36 fix: Ensure crash error messages are not duplicated (#​17584) (Nicholas C. Zakas)
  • dd79abc fix: eslint-disable to be able to parse quoted rule names (#​17612) (Yosuke Ota)
  • d2f6801 fix: Ensure correct code path for && followed by ?? (#​17618) (Nicholas C. Zakas)

Documentation

  • ee5be81 docs: default to sourceType: "module" in rule examples (#​17615) (Francesco Trotta)
  • 1aa26df docs: Add more examples for multiline-ternary (#​17610) (George Ashiotis)
  • 47d0b44 docs: Update README (GitHub Actions Bot)
  • dbf831e docs: use generated og image (#​17601) (Percy Ma)
  • 1866da5 docs: Update README (GitHub Actions Bot)

Chores

focus-trap/focus-trap (focus-trap)

v7.5.4

Compare Source

Patch Changes
nuxt/nuxt (nuxt)

v3.8.0

Compare Source

👀 Highlights

We have a lot of exciting features in v3.8, and can't wait for you to try it out.

💻 Nuxi improvements

Just to remind you, we're now using the new Nuxt CLI which is now versioned separately. There are some exciting improvements there to follow, so do check out the latest releases. (For example, we now share the same port with the Vite websocket, meaning better support for docker containers in development.)

🚨 Built-in Nuxt DevTools

Nuxt DevTools v1.0.0 is out and we now think it's ready to be shipped as a direct dependency of Nuxt.

👉 You can check out the release notes for more information - and stay tuned for an article detailing our roadmap for the future.

📸 Nuxt Image auto-install

We've now made <NuxtImg> and <NuxtPicture> first-class built-in components, documenting them and auto-installing @nuxt/image the first time that they are used (#​23717).

autoinstall2.mp4

We would definitely advise using @nuxt/image if you're using images in your site; it can apply optimisations to make your site more performant.

📂 Deeper layout scanning

🚨 This is a behaviour change so do take care with this one: 🚨

We now support scanning layouts within subfolders in ~/layouts in the same way as we do with ~/components.

File | Layout name
-- | --
~/layouts/desktop/default.vue | 'desktop-default'
~/layouts/desktop-base/base.vue | 'desktop-base'
~/layouts/desktop/index.vue | 'desktop'

See #​20190 for more information

📊 App Manifest

We now support a built-in app manifest (see #​21641), which generates a manifest at /_nuxt/builds/meta/<buildId>.json.

Initially this enables loading payloads only for prerendered routes, if a site is static (preventing 404s). It also enables client-side route rules. To begin with, only redirect route rules will have an effect; they will now redirect when performing client-side navigation. (More coming soon...!)

The app manifest also enables future enhancements including detection of outdated deployments by checking /_nuxt/builds/latest.json.

You can switch off this behaviour if you need to (but do let us know if you have any issues):

export default defineNuxtConfig({
  experimental: {
    appManifest: false
  }
})
🤝 Scope and context improvements

We now define a 'scope' for Nuxt composables executed in plugins (#​23667), which allows running synchronous cleanup before navigating away from your site, using the Vue onScopeDispose lifecycle method. This should fix an edge case with cookies (#​23697) and also improves memory management, for example in Pinia stores (#​23650). You can read more about Vue effect scopes.

We also now support native async context for the Vue composition API (#​23526). In case you're unaware, we support native async context on Node and Bun, enabled with experimental.asyncContext. This can help address issues with missing a Nuxt instance. But it didn't previously affect missing Vue instances.

If you experience issues with 'Nuxt instance unavailable', enabling this option may solve your issues, and once we have cross-runtime support we are likely to enable it by default.

export default defineNuxtConfig({
  experimental: {
    asyncContext: true
  }
})
🔗 NuxtLink defaults

We've supported defining your own NuxtLink components with the defineNuxtLink utility. We now support customising the options for the built-in <NuxtLink>, directly in your nuxt.config file (#​23724). This can enable you to enforce trailing slash behaviour across your entire site, for example.

export default defineNuxtConfig({
  experimental: {
    defaults: {
      nuxtLink: {
        activeClass: 'nuxt-link-active',
        trailingSlash: 'append'
      }
    }
  }
})
⚡️ Data fetching improvements: deep and caching

We have two very significant new features for useAsyncData and useFetch:

  1. You can now set deep: false to prevent deep reactivity on the data object returned from these composables (#​23600). It should be a performance improvement if you are returning large arrays or objects. The object will still update when refetched; it just won't trigger reactive effects if you change a property deep within the data.
  2. You can now use the getCachedData option to handle custom caching for these composables (#​20747)
const nuxtApp = useNuxtApp()
const { data } = await useAsyncData(() => { /* fetcher */ }, {
  // this will not refetch if the key exists in the payload
  getCachedData: key => nuxtApp.payload.static[key] ?? nuxtApp.payload.data[key]
})

We also support configuring some default values for these composables in an app-wide way (#​23725):

export default defineNuxtConfig({
  experimental: {
    defaults: {
      useAsyncData: {
        deep: false
      },
      useFetch: {
        retry: false,
        retryDelay: 100,
        retryStatusCodes: [500],
        timeout: 100
      }
    }
  }
})
🔢 Layer improvements

We now more carefully load layer plugins (#​22889 and #​23148) and middleware (#​22925 and #​23552) in the order of the layers, always loading your own plugins and middleware last. This should mean you can rely on utilities that layers may inject.

We've also added a test suite to cover these layer resolution changes.

And probably one of the most significant changes - if you are using remote layers we now clone these within your node_modules/ folder (#​109) so layers can use dependencies with your project. See c12 release notes for full details.

😴 Nightly release channel

Every commit to the main branch of Nuxt is automatically deployed to a new release, for easier testing before releases. We've renamed this from the 'edge release channel' to the 'nightly release channel' to avoid confusion with edge deployments. And probably also with Microsoft Edge (though I haven't heard that anyone was confused with that one!)

➡️ nuxt3 is now nuxt-nightly
➡️ nuxi-edge is now nuxi-nightly
➡️ @​nuxt/kit-edge is now @​nuxt/kit-nightly

... and so on.

You can read more about how it works.

⚗️ Nitro v2.7

Nitro v2.7 has been released with lots of improvements and bug fixes - do check out the full changelog.

🔥 One of the most significant is that we now save ~40% of bundle size in production by using native fetch (which is supported in Node 18+) (#​1724). So if possible, we'd recommend you update your Node version to at least 18.

💪 Type import changes

🚨 This is likely to need code changes in your project 🚨

Vue requires that type imports be explicit (so that the Vue compiler can correctly optimise and resolve type imports for props and so on). See core Vue tsconfig.json.

We've therefore taken the decision to turn on verbatimModuleSyntax by default in Nuxt projects, which will throw a type error if types are imported without an explicit type import. To resolve it you will need to update your imports:

- import { someFunction, SomeOptions } from 'some-library'
+ import { someFunction } from 'some-library'
+ import type { SomeOptions } from 'some-library'

You may also encounter modules in the Nuxt ecosystem that need to be updated; please open an issue for those modules. I'm also very happy to help if you're encountering any problems with this, if you're a module author. Just tag me and I'll take a look.

If for whatever reason you need to undo this change in your project you can set the following configuration:

export default defineNuxtConfig({
  typescript: {
    tsConfig: {
      compilerOptions: {
        verbatimModuleSyntax: false
      }
    }
  }
})

However, we'd recommend only doing that temporarily, as Vue does need this option to be set for best results.

✅ Upgrading

As usual, our recommendation for upgrading is to run:

nuxi upgrade

👉 Changelog

compare changes

🚀 Enhancements
  • kit: Add addServerImports and addServerImportsDir (#​23288)
  • nuxt: Warn when nesting nuxt links when SSR on dev (#​23286)
  • nuxt: Add prerenderRoutes ssr composable (#​22863)
  • nuxt: Enable appManifest by default (#​23448)
  • nuxt: Native async-context in vue's withAsyncContext (#​23526)
  • nuxt: Auto-install optional features on StackBlitz (#​23607)
  • kit,nuxt,vite,webpack: Support -nightly extension (#​23508)
  • nuxt: Add @nuxt/devtools as dependency and enable (#​23576)
  • nuxt: Support deep: false for data composables (#​23600)
  • nuxt: Custom cache support for data fetching composables (#​20747)
  • nuxt: Scan and register layouts in nested folders (#​20190)
  • nuxt: Prompt to autoinstall @nuxt/image when it is used (#​23717)
  • nuxt: Allow configuring default <NuxtLink> options (#​23724)
  • nuxt: Allow customising defaults for data composables (#​23725)
🔥 Performance
  • vite: Don't print server compressed size after vite build (#​23359)
  • nuxt: Verbatim module syntax + restrict type discovery (#​23447)
🩹 Fixes
  • nuxt: Initialise asyncData errors with null (#​23428)
  • nuxt: Apply scoped styles to islands (#​23386)
  • nuxt: Rename stub to avoid shadowing vue-router (#​23440)
  • nuxt: Stringify cookie values before broadcasting them (#​23449)
  • kit: Don't force config.autoImport in addServerImports (#​23472)
  • nuxt: Ignore prefix if clearNuxtState called w/o keys (#​23483)
  • nuxt: Decrement hydration count when rendering no route (#​23476)
  • nuxt: Compute fetch cache key with headers (#​23462)
  • nuxt: Mock hookable methods on nuxt 2 (#​23502)
  • kit: Revert accidental change to addPrerenderRoutes name (#​23509)
  • nuxt: Use test/dev as manifest buildId when appropriate (#​23512)
  • nuxt: Don't print warnings for unresolved ids (#​23604)
  • nuxt: Use import alias when checking if plugin is wrapped (#​23617)
  • nuxt: Tree shake all occurrences of <DevOnly> (#​23466)
  • nuxt: Give priority to later middleware when deduping (#​23552)
  • nuxt: Clear cookie BroadcastChannel when scope is disposed (#​23664)
  • nuxt: Provide global scope for nuxt plugin context (#​23667)
  • nuxt: Resolve type error in options of useFetch (#​23693)
  • webpack: Remove lodash-es + simplify postcss resolution (#​23692)
  • nuxt: Skip hydration mismatches with client components (#​19231)
  • nuxt: Write cookie values before navigating away (#​23697)
  • nuxt: Refetch both undefined/null values in useAsyncData (#​23351)
  • nuxt: Don't mark redirected routes as prerendered (#​23707)
  • nuxt: Respect custom export in component transform (#​23715)
  • nuxt: Don't use prerenderedAt to override app manifest (#​23781)
  • nuxt: Restore prerenderedAt behaviour pending next patch (108b1bdf7)
📖 Documentation
  • Mention listhen options on nuxi dev page (#​23415)
  • Add examples for index.ts files on server routes (#​23390)
  • Improve data fetching section (#​23420)
  • Remove duplicated arrows (#​23436)
  • Extend description of handler for useAsyncData (#​23389)
  • Clarify bridge needs nitro to use runtimeConfig (#​23454)
  • Fix typo in README (#​23500)
  • Clarify that bridge.typescript option must be set. (#​23503)
  • Use html instead of xml for highlight (45c1e7f51)
  • Fix component library example in docs (#​23596)
  • Typo in modules (#​23602)
  • Reword local module info (#​23557)
  • Add server concept (#​23372)
  • Improve nuxt kit section (#​22375)
  • Update additional mentions to nightly release channel (c63f9a95d)
  • Rename /edge-channel page to /nightly-release-channel (#​23648)
  • Add section about computed url for data fetching (#​23605)
  • Fix typo (#​23656)
  • Remove extraneous brace (b9cb08cda)
  • Fix other issues with routeRules example (818dc626c)
  • Fix typo (#​23716)
  • Update types for useFetch/useAsyncData (#​23730)
  • Add info about <NuxtImg> and <NuxtPicture> (#​23741)
  • Update to new website (#​23743)
  • Remove redundant trailing slashes from links (#​23744)
  • Fix broken link (#​23750)
🏡 Chore
  • Fix various typos and update to US English (#​23580)
  • Add description field for packages (#​23734)
  • Bump nuxt devtools to 1.0 (#​23752)
  • Allow markdownlint upgrades (3d779fcf3)
  • Remove huntr + encourage GitHub vulnerability reporting (#​23754)
  • Refresh lockfile (#​23755)
  • Update to nitropack 2.7.0 (#​23780)
  • Upgrade to c12 1.5 with configurable layers (#​23782)
✅ Tests
  • nuxt: Add test suite for app resolution behaviour (#​23520)
  • Update prerender test (8d62c2add)
🤖 CI
  • Retry failing links 6 times (ad2a900fd)
  • Only dedupe dependencies if they affect bundle size (#​23736)
❤️ Contributors
pnpm/pnpm (pnpm)

v8.10.0

Compare Source

Minor Changes

  • Support for multiple architectures when installing dependencies #​5965.

    You can now specify architectures for which you'd like to install optional dependencies, even if they don't match the architecture of the system running the install. Use the supportedArchitectures field in package.json to define your preferences.

    For example, the following configuration tells pnpm to install optional dependencies for Windows x64:

    {
  "pnpm": {
    "supportedArchitectures": {
      "os": ["win32"],
      "cpu": ["x64"]
    }
  }
}

    Whereas this configuration will have pnpm install optional dependencies for Windows, macOS, and the architecture of the system currently running the install. It includes artifacts for both x64 and arm64 CPUs:

    {
  "pnpm": {
    "supportedArchitectures": {
      "os": ["win32", "darwin", "current"],
      "cpu": ["x64", "arm64"]
    }
  }
}

    Additionally, supportedArchitectures also supports specifying the libc of the system.

  • The pnpm licenses list command now accepts the --filter option to check the licenses of the dependencies of a subset of workspace projects #​5806.

Patch Changes

  • Allow scoped name as bin name #​7112.

  • When running scripts recursively inside a workspace, the logs of the scripts are grouped together in some CI tools. (Only works with --workspace-concurrency 1)

  • Print a warning when installing a dependency from a non-existent directory #​7159

  • Should fetch dependency from tarball url when patching dependency installed from git #​7196

  • pnpm setup should add a newline at the end of the updated shell config file #​7227.

  • Improved the performance of linking bins of hoisted dependencies to node_modules/.pnpm/node_modules/.bin #​7212.

  • Wrongful ELIFECYCLE error on program termination #​7164.

  • pnpm publish should not pack the same file twice sometimes #​6997.

    The fix was to update npm-packlist to the latest version.

Our Gold Sponsors

Our Silver Sponsors

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.

@sarvex sarvex merged commit e7d1776 into main Oct 29, 2023
0 of 3 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch October 29, 2023 09:59
@sonarcloud
Copy link

sonarcloud bot commented Oct 29, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

imgbot bot pushed a commit that referenced this pull request Oct 29, 2023
@sarvex
Merge pull request #3 from sarvex/renovate/all-minor-patch
551043a 
chore(deps): update all non-major dependencies
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.

None yet
1 participant
@sarvex