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

fix(deps): update dependency nuxt to v3 [security] - autoclosed #276

Closed
wants to merge 1 commit into from
Closed

fix(deps): update dependency nuxt to v3 [security] - autoclosed #276

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jun 21, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
nuxt ^2.15.8 -> ^3.0.0 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2023-3224

Nuxt prior to version 3.4.3 is vulnerable to code injection.

Release Notes

nuxt/nuxt

v3.4.3

Compare Source

3.4.3 is a patch release with the latest bug fixes. 🐞 It is expected that the next release will be v3.5, in approximately two weeks' time.

✅ 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

🩹 Fixes
  • nuxt: Don't call timeEnd unless we're debugging (#​20424)
  • nuxt: Use key to force server component re-rendering (#​19911)
  • nuxt: Add basic typings for <ClientOnly> (f1ded44e8)
  • nuxt: Use event.node.req in cookie utility (#​20474)
  • deps: Relax upper node version constraint (#​20472)
  • nuxi,schema: Support devServer.https: true (#​20498)
  • nuxt: Throw 404 when accessing /__nuxt_error directly (#​20497)
  • nuxt: Use callAsync for executing hooks with context (#​20510)
  • nuxt: Improved typing support for app config (#​20526)
  • nuxt: Call app:error in SSR before rendering error page (#​20511)
  • nuxt: Restrict access to single renderer outside of test/rootDir (#​20543)
  • nuxt: Throw errors when running legacy asyncData (#​20535)
  • nuxt: Transform #components imports into direct component imports (#​20547)
  • nuxt: Return RenderResponse for redirects (#​20496)
📖 Documentation
  • Fix typos on docs homepage (#​20456)
  • Update links to vue-router docs (#​20454)
  • Remove RC reference and add link to vue migration build (#​20485)
  • Add cdn proxy section (#​20408)
  • Add a next steps link to first page of migration docs (#​20512)
  • Add custom fetch composable example (#​20115)
  • Adjust wrong link after repo migration (#​20536)
✅ Tests
🤖 CI
  • Publish edge release with provenance (ec1503731)
  • Run release script with node 18 (0d10e9734)
  • Try releasing nuxt-edge with provenance (753c4c2a3)
  • Run nuxt2 nightly release on node 14 again (48c034cf0)
❤️ Contributors

v3.4.2

Compare Source

3.4.2 is a patch release with the latest bug fixes and performance improvements

✨ What's new?

Apart from the normal bug fixes, we have a couple things we should call out.

  1. 🔥 We're now on Vite 4.3 (#​20405). This was a performance-focused release and hopefully you'll be enjoying the speed improvements! Check out the release announcement for more info.
  2. 👀 It's now possible to experimentally enable @parcel/watcher for the Nuxt dev watcher (#​20179). This may improve performance if you're on Windows. You'll probably also want to install watchman in that case.

✅ 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

🔥 Performance
  • nuxt: Share lazy component definitions (#​20259)
  • Remove unused deps and add implicit deps (#​20356)
  • Allow using @parcel/watcher for dev watcher (#​20179)
🩹 Fixes
  • vite: Set different cache dirs for client/server (#​20276)
  • nuxt: Generate hi-res sourcemaps (#​20280)
  • nuxt: Return type directly if not picking asyncData (#​20288)
  • nuxt: Provide more helpful error when instance unavailable (#​20289)
  • nuxt: Mark useRequestHeaders keys as optional (#​20286)
  • vite: Avoid serving arbitrary file in vite-node middleware (#​20345)
  • nuxt: Swap preloads for json/js payloads (#​20375)
  • nuxt: Handle pages with no content and log warning (#​20373)
  • test-utils: Import jest functions from @jest/globals (#​20360)
  • core,kit: Ensure module transpilation paths are dirs (#​20396)
  • schema: Rely on installed telemetry types (#​19640)
  • cli: Load kit from rootDir when preparing project (#​20401)
  • nuxt: Clone app config on server (#​20278)
💅 Refactors
  • nuxt: Rework and use isJS and isVue utilities consistently (#​20344)
  • vite: Use native isFileServingAllowed util (#​20414)
📖 Documentation
  • Update links on hooks page (#​20296)
  • Add brief information on debugging a nuxt app (#​20282)
  • Fix vue-tsc link (#​20350)
  • Update lint command for the documentation (#​20399)
🏡 Chore
🤖 CI
  • Don't run ci for release branches (f550976f7)
  • Give write access to changelogensets (0518cdbff)
❤️ Contributors

v3.4.1

Compare Source

3.4.1 is a patch release. We've pulled it forward slightly to fix a couple of breaking bugs in 3.4.0.

👉 Changelog

compare changes

🩹 Fixes
  • nuxt: Set config on ssrContext in spa renderer (#​20216)
  • nuxt: Mark entire payload as reactive (#​20218)
  • nuxt: Add missing imports to <NuxtClientFallback> (#​20237)
  • nuxt: Improve handling of redirects within middleware (#​20244)
  • nuxt: Do not redirect when vue-router normalises url (#​20247)
📖 Documentation
  • Add a brief description of transform/pick (#​20186)
✅ Tests
❤️ Contributors

v3.4.0

Compare Source

3.4.0 is a minor (feature) release for Nuxt 3 bringing exciting new features, including support for the View Transitions API, transferring rich JavaScript payloads from server to client - and much more.

👀 Highlights

🪄 View Transitions API Support
CleanShot.2023-04-11.at.18.00.47.mp4

You can see a demo on https://nuxt-view-transitions.surge.sh

You may have noticed that Chromium-based browsers now ship a new web platform API: the View Transitions API. This is an exciting new ability for native browser transitions which (among other things) have the ability to transition between unrelated elements on different pages.

Nuxt now ships with an experimental implementation, which will be under active development during the v3.4 release cycle. See the known issues in the linked PR.

export default defineNuxtConfig({
  experimental: {
    viewTransition: true
  }
})
✨ Payload Enhancements

We've merged a significant change to how Nuxt handles payloads (under an experimental flag). Payloads are used to send data from the server to the client when doing server-side rendering and avoid double data-fetching during the hydration phase.

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

With this new option enabled, this now means that various rich JS types are supported out-of-the-box: regular expressions, dates, Map and Set and BigInt as well as NuxtError - and Vue-specific objects like ref, reactive, shallowRef and shallowReactive.

You can find an example in our test suite.

This is all possible due to Rich-Harris/devalue#​58. For a long time, Nuxt has been using our own fork of devalue owing to issues serialising Errors and other non-POJO objects, but we now have transitioned back to the original.

You can even register your own custom types with a new object-syntax Nuxt plugin:

export default definePayloadPlugin(() => {
  definePayloadReducer('BlinkingText', data => data === '<original-blink>' && '_')
  definePayloadReviver('BlinkingText', () => '<revivified-blink>')
})

You can read more about how this works here.

Note: this only affects payloads of the Nuxt app, that is, data stored within useState, returned from useAsyncData or manually injected via nuxtApp.payload. It does not affect data fetched from Nitro server routes via $fetch or useFetch although this is one area I am keen to explore further.

Preliminary testing shows a significant speed-up: 25% faster in total server response time for a very minimal app with a large JSON payload, but I'd urge you to run your own tests and share the results with us.

As mentioned, we're merging this behind a flag so we can test this broadly and gather feedback on the new approach. The most significant potential change is that the payload is now no longer available on window.__NUXT__ immediately. Instead, we now need to initialise the Nuxt app to parse the payload so any code that accesses __NUXT__ will need to be run in a plugin or later in the Nuxt app lifecycle. Please feel free to raise an issue if you foresee or encounter issues in your projects.

🎁 Object-syntax Nuxt plugins

We now support object-syntax Nuxt plugins for better control over plugin order and easier registration of hooks.

export default defineNuxtPlugin({
  name: 'my-plugin',
  enforce: 'pre', // or 'post'
  async setup (nuxtApp) {
    // this is the equivalent of a normal functional plugin
  },
  hooks: {
    // You can directly register Nuxt app hooks here
    'app:created'() {
      const nuxtApp = useNuxtApp()
      // 
    }
  }
})

In future we plan to enable build optimizations based on the metadata you pass in your Nuxt plugins.

🛠️ Easier Devtools Configuration

It's even easier to enable Nuxt DevTools in your project: just set devtools: true in your nuxt.config file to enable devtools.

export default defineNuxtConfig({
  devtools: true
})

If it's not already installed, Nuxt will prompt to install it locally. This means you no longer need to have Nuxt DevTools enabled globally.

Note: the DevTools is still experimental and under active development, so do be prepared for occasional unexpected behaviour, and please report issues directly to https://github.com/nuxt/devtools 🙏

📚 Layers Improvements

We now support transforming ~/~~/@/@@&#8203; aliases within layers, meaning you now no longer need to use relative paths when importing within layers.

This should mean it is much easier to use a 'normal' Nuxt project as a layer without needing to specially write it as one.

🧸 Better Context Transforms

We now transform certain keys of definePageMeta and defineNuxtComponent which means you should have fewer issues with a missing Nuxt instance. This includes support accessing the Nuxt instance after an await within asyncData and setup functions for those still using the Options API. And you no longer need to wrap middleware and validate with defineNuxtRouteMiddleware when using async functions.

♻️ Ecosystem Updates

As usual, this release will pull in upstream improvements, including the new Consola v3 and Nitropack v2.3.3 (a new minor is expected shortly).

🚨 'Breaking fixes'

We've also taken the opportunity to do some cleanup in this minor release.

  1. Previously it was possible to pass the x-nuxt-no-ssr header (undocumented) to force SPA rendering. We've now disabled this behaviour by default but you can get it back by setting experimental.respectNoSSRHeader to true. Alternatively, you can set event.context.nuxt.noSSR on the server to force SPA rendering.
  2. We've removed the (deprecated) #head alias and also disabled the polyfill for @vueuse/head behaviour by default. (It can still be enabled with experimental.polyfillVueUseHead.)
  3. We've removed the (deprecated) experimental.viteNode option. It can be configured instead with vite.devBundler.
  4. We've deprecated accessing public runtime config without the public key. This was an undocument compatibility measure with Nuxt 2 and we plan to remove it entirely in v3.5.
  5. To fix a bug with our vue-router integration, we now generate a slightly different path matching syntax. If you were relying on the exact path generated, have a look at https://github.com/nuxt/nuxt/pull/19902 for more information.
✅ 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.

With Nuxt v3.4.0, we now advise that you explicitly install the @types/node version that matches your Node version.

👉 Changelog

compare changes

🚀 Enhancements
  • nuxt: Warn in dev when useRoute is used in middleware (#​20050)
  • nuxt: Support disabling watch with useFetch (#​19823)
  • nuxt: Support ~/~~/@/@@&#8203; aliases within layers (#​19986)
  • nuxt: Respect custom dir.pages in page placeholder (#​20079)
  • nuxt: Support vue runtime compiler (#​4762)
  • test-utils: Allow mounting single component for testing (#​5723)
  • nuxt: Experimental option for rich json payloads (#​19205)
  • nuxt: Prompt to install devtools when it's enabled (#​20126)
  • Upgrade to consola v3.x prerelease (#​20141)
  • nuxt: Add experimental View Transitions API support (#​20092)
  • nuxt: Support async transform of object properties (#​20182)
  • nuxt: Support object-syntax plugins (#​20003)
  • nuxt: Add experimentalNoScripts route rule (#​19805)
  • nuxt: Add chokidar watcher debug timing (#​20176)
🔥 Performance
  • head: Disable @vueuse/head polyfill by default (#​20131)
🩹 Fixes
  • nuxt: End route param tokens manually (#​19902)
  • nuxt: Disable x-nuxt-no-ssr header by default (#​20024)
  • kit: Support calling Nuxt 2 modules with module container (#​20023)
  • nuxt: Add types for globally injected $config object (#​20081)
  • nuxt: Throw error on protocol relative path in useFetch (#​20052)
  • nuxt: Add @types/node as a peerDependency (#​20025)
  • nuxt: Test all custom app config keys for any (#​20105)
  • nuxt: Add key to .client component placeholders (#​20093)
  • nuxt: Add undefined type for useCookie return value (4f0b3c722)
  • nuxt: Deprecate old (pre-rc) runtimeConfig (#​20082)
  • cli: Preview nitro build with custom dir config (#​18882)
  • nuxt: Default nitro autoImports to imports.autoImport (#​20180)
  • nuxi, vite: Suppress sourcemap + native fetch warnings (#​20198)
  • schema: Allow ignorePrefix to be changed (#​20202)
💅 Refactors
📖 Documentation
  • Add interop default to dynamic vue import example (8908aa7c5)
  • Add short note about custom imports configuration (#​20073)
  • Re-enable docs linting and update docs (#​20084)
  • Fix type of headers option for useFetch (#​20148)
  • Fix typo in @pinia/nuxt module name (#​20199)
  • Add import to server-side cookies example (#​20197)
🏡 Chore
✅ Tests
🎨 Styles
🤖 CI
❤️ Contributors

v3.3.3

Compare Source

3.3.3 is your regularly scheduled bugfix/patch release.

✅ 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

🩹 Fixes
  • schema: Prefer src to rootDir aliases (#​19937)
  • nuxt: Don't override options signature with schema (#​19934)
  • vite: Allow extending vue config per-environment (#​19968)
  • nuxt: Store payloads in cache without trailing slash (#​19992)
  • webpack: Transpile rest of nuxt runtime directories (#​19936)
  • nuxt: Suppress handled errors (#​20002)
  • vite: Remove separate rollup dependency (#​20013)
  • nuxt: Sync setResponseStatus signature with h3 (#​19987)
  • schema: Add export condition for nuxt2 support (1fd491f1a)
💅 Refactors
  • vite: Use rollup types re-exported from vite (#​20011)
📖 Documentation
🏡 Chore
✅ Tests
  • Skip bundle size test in ecosystem-ci suites (434e2013e)
  • Bump bundle size test by 100 bytes (5785908ec)
🤖 CI
  • Run docs linting step on node 18 (1ae5b2c58)
❤️ Contributors

v3.3.2

Compare Source

3.3.2 is a patch release with plenty of bug fixes.

✅ 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

🔥 Performance
  • nuxt: Experimentally disable vue server renderer nitro endpoint (#​19825)
🩹 Fixes
  • kit: Provide name to performance.mark() (#​19687)
  • nuxt: Unpause DOM updates on suspense resolve (#​19740)
  • kit: Handle node 14 performance behaviour (#​19733)
  • webpack: Transpile app directory (#​19773)
  • nuxt: Unset context after app is created (#​19753)
  • cli: Watch dist and register restart hook after nuxt is ready (#​19736)
  • nuxt: Ignore falsy modules (#​19684)
  • nuxt: Use h3 utilities to set response status/code (#​19713)
  • nuxt: Add temporary augmentation for webstorm (and docs) (#​19400)
  • nuxt: Handle external navigation to api routes (#​19829)
  • nuxt: Observe slot element in custom nuxt-link (#​19802)
  • nuxt: Directly render server components (#​19605)
  • vite: Support multiple rollup entries (#​19842)
  • nuxt: Ignore schema types that eval to any (#​19835)
  • nuxt: Use prerender cache for islands (#​19822)
  • nuxt: Add missing import in islands template (#​19870)
  • kit: Check if nuxt is restarting before updating templates (#​19830)
  • test-utils: Allow overriding nitro options (#​19872)
  • kit: Add legacy entrypoints for pre v3.3 usage (#​19874)
📖 Documentation
🏡 Chore
✅ Tests
🤖 CI
❤️ Contributors

v3.3.1

Compare Source

3.3.0 is a minor (feature) release with lots of new features to play with. 3.3.1 was a swiftly following release to patch an issue with nuxi on Windows.

👀 Highlights

✨ Local module development DX

We've landed a raft of changes to enable local modules and improve DX. We now auto-scan your ~/modules folder and register top level files there as modules in your project (https://github.com/nuxt/nuxt/pull/19394). When these files are changed, we'll automatically restart the nuxt server.

  export default defineNuxtConfig({
    modules: [
      '@&#8203;nuxtjs/tailwindcss',
-     '~/modules/purge-comments'
    ]
  })

We also now expose nuxt/kit for easy access to kit composables in your local project without having to install @nuxt/kit (https://github.com/nuxt/nuxt/pull/19422).

♻️ Restarting Nuxt

You can add files to the watch array to automatically restart the server (https://github.com/nuxt/nuxt/pull/19530). This is likely to be particularly useful for module authors. You can also trigger a restart of the Nuxt server with the new restart hook (https://github.com/nuxt/nuxt/pull/19084). We also landed a couple of fixes on restarting the Nuxt server which should improve your experience when developing.

🔥 Performance improvements

We've increased static asset maxAge to 1yr as a matter of best practice (https://github.com/nuxt/nuxt/pull/19335), and support tree-shaking more of your build (https://github.com/nuxt/nuxt/pull/19508). We also now support preloading <NuxtLink>s with a route in object-syntax (https://github.com/nuxt/nuxt/pull/19120).

CleanShot 2023-03-14 at 12 19 50

We also track how long it takes each module you use to perform its setup, and warn if it takes too long. You can see all these values by running your dev server with DEBUG=1

You can also opt-in to some of Nuxt's internal optimisations by configuring composables to be treeshaken in a particular environment (https://github.com/nuxt/nuxt/pull/19383), or to have magic keys automatically injected (https://github.com/nuxt/nuxt/pull/19490) - primarily useful for module authors.

🐛 Error handling

We now handle chunk errors by default (https://github.com/nuxt/nuxt/pull/19086), meaning if your site updates with a redeploy, we automatically handle reloading it on navigation. You can disable this and handle it yourself with the new reloadNuxtApp composable. You can also set experimental.restoreState to preserve some of your app state across reloads.

We also have a new experimental error handling component: <NuxtClientFallback> (https://github.com/nuxt/framework/pull/8216) which can capture errors rendering on server, replace them with fallback content, and granularly trigger rerendering the part with an error on the client. This can be enabled with experimental.clientFallback - feedback very welcome!

⚡️ Head improvements

We've migrated to use unhead directly (https://github.com/nuxt/nuxt/pull/19519) - and automatically tree-shake server-only head composables like useServerHead from your client build (https://github.com/nuxt/nuxt/pull/19576), meaning you can have great SEO without needing to include meta tag logic that's relevant only for crawlers in your client build.

There's also a new useHeadSafe composable that handles santising untrusted user input (https://github.com/nuxt/nuxt/pull/19548).

🪵 Better logging in browser DevTools

Working with the Chrome DevTools team, we've landed a couple of features across the unjs + Nuxt ecosystem meaning we now have first-class support for hiding Nuxt internal stack traces from logs in your (Chromium-based, for now) browser (https://github.com/nuxt/nuxt/pull/19243). We also landed a couple of improvements with stacktraces involving Nuxt hooks (https://github.com/unjs/hookable/pull/69 and https://github.com/unjs/hookable/pull/68) implementing console.createTask.

Before After
CleanShot 2023-03-14 at 11 55 00 CleanShot 2023-03-14 at 11 52 27
💪 Type improvements

Types for server API routes are now more correct - with non-serialisable types stripped out of the return type (https://github.com/unjs/nitro/pull/1002).

We also now type more of NuxtApp and correctly type unknown injections for greater type-safety (https://github.com/nuxt/nuxt/pull/19643).

CleanShot 2023-03-14 at 11 59 58

And if you were struggling with correct types when using transform + default with Nuxt data fetching composables, fear no more - we now infer the types correctly (https://github.com/nuxt/nuxt/pull/19487).

⚗️ Nitro enhancements

This release comes with Nitro v2.3, which brings lots of improvements of its own. Check out the release for more info.

We now support useAppConfig in nitro server routes (https://github.com/nuxt/nuxt/pull/19489) - a long-awaited change. Now useAppConfig is consistently available throughout your app for non-runtime configuration from layers, modules, etc.

We've also added a nitro:build:public-assets hook to allow modifying assets output from nitro's prerender/build phase (https://github.com/nuxt/nuxt/pull/19638).

🛠️ Build changes

As part of moving towards first-class support for PNP and pnpm support without --shamefully-hoist, we've dropped support for some internal (deprecated) utilities using CJS resolve patterns (https://github.com/nuxt/nuxt/pull/19537, https://github.com/nuxt/nuxt/pull/19608). We also now resolve dependencies like nuxt, @nuxt/kit and more using ESM search-paths. We'll be keeping a close eye on this.

We're also preparing the groundwork for support of new TypeScript Node16 module resolution (https://github.com/nuxt/nuxt/issues/19606), and as part of this have changed the format of our runtime output (using .js instead of .mjs extensions, providing types fields for subpath exports, and more).

🗺️ Custom config schema (advanced)

We've been testing out an experimental feature to allow modules and users to extend the Nuxt config schema (https://github.com/nuxt/nuxt/issues/15592), and we've now enabled this by default (https://github.com/nuxt/nuxt/pull/19172). We expect this will be particularly useful for module and layer/theme authors, and should result in some nicer DX for their users.

Changelog

compare changes

🚀 Enhancements
  • nuxi: Enforce consistent casing in filenames (#​19088)
  • nuxi: Reload nuxt when restart hook is called (#​19084)
  • nuxt: Scan composables with star export (#​19249)
  • nuxt: Add versions to runtime nuxtApp (#​19064)
  • vite: Add node_modules and buildDir to x_google_ignoreList (#​19243)
  • nuxi: Cli wrapper for self restart (#​18641)
  • schema: Allow adding page routes without a matching file (#​19173)
  • nuxt: Add support for nuxt/kit subpath for local use (#​19422)
  • nuxt: Auto-register modules in ~/modules (#​19394)
  • nuxt: Enable config schema by default (#​19172)
  • kit,nuxt: Add component priority to allow overriding (#​19252)
  • nuxt: Enable preloading object-syntax routes (#​19120)
  • nuxt: Support trailingSlashBehavior in defineNuxtLink (#​19458)
  • nuxt: Allow configuring treeshakeable composables (#​19383)
  • nuxi,schema: Add support for setting nuxt logLevel (#​19369)
  • nuxt: Support custom keyed composables (#​19490)
  • nuxi: Programmatically pass nuxt config overrides (to dev) (#​19371)
  • vite: Use custom logger to show vite logs (#​19523)
  • nuxt: Enable chunk error handling by default (#​19086)
  • nuxt: Add <NuxtClientFallback> component (#​8216)
  • nuxt: Add watch option and refactor dev server restarting (#​19530)
  • nuxt: Add useHeadSafe and remove layer around head imports (#​19548)
  • kit, schema: Measure module setup timings (#​18648)
  • nuxt: Support app config for server routes (#​19489)
  • nuxt: Add nitro:build:public-assets hook (#​19638)
🔥 Performance
  • nuxt: Increase static asset maxAge to 1yr (#​19335)
  • vite: Mark more core functions as side-effect free (#​19508)
  • nuxt: Drop @vueuse/head dependency (#​19519)
  • nuxt: Tree-shake server composables + prefer server head (#​19576)
🩹 Fixes
  • nuxt: Clear loading indicator on unmount (#​19340)
  • nuxt: Deprecate scanning directory index plugins (#​18418)
  • nuxt: Prevent fallthrough attributes on custom NuxtLink (#​19379)
  • schema: Update vite import.meta types (#​19338)
  • vite: Omit / from sourcemapIgnoreList for windows support (73ade185b)
  • nuxt: Pass transform options to component loader plugin (#​19414)
  • nuxi: Avoid top-level await in wrapper (44068420d)
  • nuxt: Add kit.* files to published package (#​19430)
  • nuxt: Don't print layout warning if page is not ssr (#​19434)
  • kit: Match commit hashes of other lengths (#​19450)
  • nuxi: Handle different kind of shutdown signals (#​19485)
  • nuxt: Exclude nitro output dir from type checking (#​19532)
  • vite: Allow disabling clear screen behaviour (#​19531)
  • nuxt: Only log boot errors on client-side (#​19553)
  • nuxt: Dedupe payload cache by payload url (#​19563)
  • nuxt: Provide node16-style type exports (#​18431)
  • nuxt: Avoid injecting adhoc modules in schema (#​19607)
  • nuxt: Improve types for data fetching with transform (#​19487)
  • nuxi: Resolve kit from nuxt modules dir (#​19601)
  • nuxt,schema: Merge custom and resolved app configs (#​19602)
  • nuxt: Resolve builder using esm syntax (#​19608)
  • nuxt: Exclude boolean from inline module definitions (#​19621)
  • schema: Show payloadExtraction warning only when unset (#​18516)
  • nuxt: Mark non-augmented NuxtApp properties as unknown (#​19643)
  • nuxt: Fix default injection type for plugins (#​19669)
💅 Refactors
  • nuxi: Hard restart with communication channel (#​19423)
  • kit,nuxi: Resolve module paths using node algorithm (#​19537)
  • nuxt: Let mlly handle search paths (#​19635)
📖 Documentation
  • Use consistent indentation in examples (#​19342)
  • Update esm link (c35104c76)
  • Add frontmatter note for docs readme to remove from live preview (008426cd3)
  • Add edge banners on versions and modules (#​19448)
  • Add local modules ordering (5977adb4d)
  • Fix link to nitro routeRules (#​19455)
  • Fix dead link to useSeoMeta guide (#​19463)
  • Update devServer.https example (#​19486)
  • Add info ~/server/utils directory in ~/utils page (#​19500)
  • Update addComponent jsdoc comment (#​19503)
  • Update cli docs for --log-level (06b9233b1)
  • Update pr template to include jsdoc annotations (#​19511)
  • Add new release cycle info (#​19509)
  • Fix local modules (c4222b1f6)
  • Update nitro plugins url (#​19547)
  • Ui components - pinceau migration (#​19533)
  • Update $fetch documentation (#​19356)
  • Move prerequisites into a summary (e0cb950f0)
  • Remove note since already in code block for pnpm (d67a873c4)
  • Add nuxt 2 to nuxt 3 workshop (2905282de)
  • Update various nitro links (#​19562)
  • Use consistent page name in example (#​19583)
  • Add missing backquotes (#​19590)
  • Remove reference to beta/rc/coming soon (4ad5c959e)
  • Warn about modules with side-effects (#​19592)
  • Mention config file name before code block (#​19634)
🏡 Chore
  • Bump edge version based on commits (#​19397)
  • Add branch to edge release script (171288586)
  • Add chore to type of change in pr template (#​19420)
  • Mark @nuxt/test-utils package as external group (#​19419)
  • Restrict commit hash strings to 8 chars (abcd27ae0)
  • deps: ⚠️ Update dependency fork-ts-checker-webpack-plugin to v8 (main) (#​19468)
  • Force minor bumps at most (0b82f6751)
  • nuxt: Update to new hasProtocol options format (#​19555)
  • Improve internal type safety (#​19599)
  • Refresh lockfile (#​19653)
  • Constrain nitro to minor version (88a5f38de)
  • Bump package versions (615750614)
✅ Tests
🤖 CI
⚠️ Breaking Changes
  • deps: ⚠️ Update dependency fork-ts-checker-webpack-plugin to v8 (main) (#​19468)
❤️ Contributors

Configuration

📅 Schedule: Branch creation - "" (UTC), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

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

@renovate renovate bot changed the title fix(deps): update dependency nuxt to v3 [security] fix(deps): update dependency nuxt to v3 [security] - autoclosed Jun 22, 2023
@renovate renovate bot closed this Jun 22, 2023
@renovate renovate bot deleted the renovate/npm-nuxt-vulnerability branch June 22, 2023 21:28
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
0 participants