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 - autoclosed #87

Closed
wants to merge 1 commit into from
Closed

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

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 23, 2023 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nuxt/kit ^3.3.1 -> ^3.5.0 age adoption passing confidence
eslint-webpack-plugin ^4.0.0 -> ^4.0.1 age adoption passing confidence
pnpm (source) 7.30.0 -> 7.32.4 age adoption passing confidence

Release Notes

nuxt/nuxt

v3.5.0

Compare Source

3.5.0 is a minor (feature) release with lots of new features to play with.

👀 Highlights

⚡️ Vue 3.3 released!

Vue 3.3 has been released, with lots of exciting features, particularly around type support. This also brings a significant improvement to data fetching when navigating between nested pages (https://github.com/nuxt/nuxt/pull/20777), thanks to @​antfu and @​baiwusanyu-c.

  • new defineOptions macro
  • 'generic' components
  • typed slots and using external types in defineProps
  • ... and more

Read the full release announcement for more details.

🙌 Nitropack v2.4

We've been working on lots of improvements to Nitro and these have landed already in Nitro v2.4 - you may already have this upgrade, which contains a lot of bug fixes, updates to the module worker format for Cloudflare, Vercel KV support and more.

One note: if you're deploying to Vercel or Netlify and want to benefit from incremental static regeneration, you should now update your route rules:

routeRules: {
--  '/blog/**': { swr: 3000 },
++  '/blog/**': { isr: 3000 },
}

Read the full release notes.

💖 New defaults

Rich JSON payload serialisation is now enabled by default (https://github.com/nuxt/nuxt/pull/19205, https://github.com/nuxt/nuxt/pull/20770). This is both faster and allows serialising complex objects in the payload passed from the Nuxt server to client (and also when extracting payload data for prerendered sites).

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.

🛝 Interactive server components

This feature should be considered highly experimental, but thanks to some great work from @​huang-julien we now support interactive content within server components via slots (https://github.com/nuxt/nuxt/pull/20284).

You can follow the server component roadmap at https://github.com/nuxt/nuxt/issues/19772.

⏰ Environment config

You can now configure fully typed, per-environment overrides in your nuxt.config:

export default defineNuxtConfig({
  $production: {
    routeRules: {
      '/**': { isr: true }
    }
  },
  $development: {
    //
  }
})

If you're authoring layers, you can also use the $meta key to provide metadata that you or the consumers of your layer might use.

Read more: https://github.com/nuxt/nuxt/pull/20329.

💪 Fully typed pages

You can benefit from fully typed routing within your Nuxt app via this experimental integration with https://github.com/posva/unplugin-vue-router - thanks to some great work from @​posva! Out of the box, this will enable typed usage of navigateTo, <NuxtLink>, router.push() and more. You can even get typed params within a page by using const route = useRoute('route-name').

export default defineNuxtConfig({
  experimental: {
    typedPages: true
  }
})
🔎 'Bundler' module resolution

We now have full support within Nuxt for the bundler strategy of module resolution. We would recommend adopting this if possible. It has type support for subpath exports, for example, but more exactly matches the behaviour of build tools like Vite and Nuxt than Node16 resolution.

export default defineNuxtConfig({
  typescript: {
    tsConfig: {
      compilerOptions: {
        moduleResolution: 'bundler'
      }
    }
  }
})

This turns on TypeScript's ability to 'follow' Node subpath exports. For example, if a library has a subpath export like mylib/path that is mapped to mylib/dist/path.mjs then the types for this can be pulled in from mylib/dist/path.d.ts rather than requiring the library author to create mylib/path.d.ts.

⚗️ Separate server types

We plan to improve clarity within your IDE between the 'nitro' and 'vue' part of your app, and we've shipped the first part of this via a separate generated tsconfig.json for your ~/server directory (https://github.com/nuxt/nuxt/pull/20559). You can use by adding an additional ~/server/tsconfig.json with the following content:

{
  "extends": "../.nuxt/tsconfig.server.json"
}

Although right now these values won't be respected when type checking, you should get better type hints in your IDE.

💀 Deprecations

Although we have not typed or documented the build.extend hook from Nuxt 2, we have been calling it within the webpack builder. We are now explicitly deprecating this and will remove it in a future minor version.

✅ 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

🚀 Enhancements
  • kit: Add prepend option to addImportsDir (#​20307)
  • nuxt: Add scoped helper for clearing error within boundary (#​20508)
  • nuxt: Auto import 'watchPostEffect' and 'watchSyncEffect' from vue (#​20279)
  • vite: Introduce vite:configResolved hook (#​20411)
  • webpack: Introduce webpack:configResolved hook (#​20412)
  • kit: Allow vite and webpack plugins to be prepended (#​20403)
  • nuxt: Add layer meta and env overrides to config types (#​20329)
  • test-utils: Add option to configure test server port (#​20443)
  • nuxt: Allow access to components within app (#​20604)
  • kit: Support passing getter to addVitePlugin and addWebpackPlugin (#​20525)
  • cli: Allow greater control of nuxi analyze from cli (#​20387)
  • nuxt: Add nuxtApp.runWithContext (#​20608)
  • deps: Upgrade to nitropack v2.4 (#​20688)
  • nuxt: Add experimental typedPages option (#​20367)
  • nuxt: Add apps to nuxt build-time instance (#​20637)
  • cli: Allow passing overrides to other nuxi commands (#​20760)
  • schema: Enable rich json payloads by default (#​20770)
  • deps: Update vue to v3.3 (#​20478)
  • nuxt: Use runWithContext within callWithNuxt (#​20775)
  • nuxt: Add useRequestURL helper (#​20765)
  • nuxt: Allow fallback production content in <DevOnly> (#​20817)
  • kit: addBuildPlugin for builder-agnostic implementation (#​20587)
  • nuxt: Allow keeping fallback for NuxtClientFallback (#​20336)
  • nuxt: Support separate server tsconfig (#​20559)
  • nuxt: Full scoped slots support for server components (#​20284)
  • nuxt: Support parallel plugins (#​20460)
🩹 Fixes
  • nuxt: Remove backwards-compatible runtimeConfig proxy (#​20340)
  • nuxt: Add @nuxt/devtools module before core modules (#​20595)
  • nuxt: Properly handle query for component wrapper (#​20591)
  • nuxt: Skip payload extraction for island context (#​20590)
  • nuxt: Remove internal <FragmentWrapper> (#​20607)
  • nuxt: Ensure useError is called with nuxt app context (#​20585)
  • nuxt: Run page meta plugin on all pages (and only pages) (#​20628)
  • nuxt, vite: Ignore nuxt_component ssr style and isVue (#​20679)
  • webpack: Warn when using deprecated build.extend hook (#​20605)
  • nuxt: Allow resolving client nuxt app to singleton (#​20639)
  • nuxt: Generate empty sourcemaps for wrappers (#​20744)
  • nuxt: Prevent treeshaking hooks with composable names (#​20745)
  • kit: Prefer esm resolution for modules to install (#​20757)
  • vite: Expand fs.allow dirs to include app files (#​20755)
  • nuxt: Deduplicate global components before registration (#​20743)
  • nuxt: Remove webstorm compatibility augmentation (0258acdc8)
  • nuxt: Enable suspensible behaviour for nested pages (#​20777)
  • cli: Hard-reload nuxt when .env changes (#​20501)
  • nuxt: Avoid destructuring error prop (works around upstream bug) (#​20795)
  • nuxt: Always inline styles for server/island components (#​20599)
  • nuxt: Allow serialising undefined refs (#​20828)
  • nuxt: Transform client fallbacks directly on SFCs (#​20835)
  • vite: Dedupe/optimize more vue core deps (#​20829)
  • nuxt: Get fallback for <DevOnly> from parsed html (#​20840)
  • nuxt: Ensure all dir parts are present in component name (#​20779)
  • nuxt: Allow pages:extend to enable pages module (#​20806)
  • nuxt: Stop loading indicator on vue errors (#​20738)
  • nuxt: Add types for webpack/vite environments (#​20749)
  • nuxt: Pass from + savedPosition to first scrollBehavior (#​20859)
💅 Refactors
  • schema: Move runtimeCompiler option out of experimental (#​20606)
  • kit: Use esm utils for resolvePath (#​20756)
📖 Documentation
  • Fix typo (#​20577)
  • Update tailwind configuration guide (#​20598)
  • Fix fetch composable examples (#​20603)
  • Note that useCookie does not share state (#​20665)
  • Selective pre-rendering options (#​20670)
  • Ensure we guard all navigateTo examples (#​20678)
  • Add useSeoMeta and useServerSeoMeta pages (#​20656)
  • Recommend <NuxtLayout> when migrating error.vue (#​20690)
  • Add lagon to presets list (#​20706)
  • Add await before lazy composable examples (7e7e006e9)
  • Add missing step migrating to pinia (#​20778)
  • Server directory improvements (d53cc604d)
🏡 Chore
✅ Tests
  • Test with bundler module resolution (#​20629)
🤖 CI
  • Run autofix on renovate branches (af75f18cf)
  • Run 2.x nightly release on node 16 (a81f9e4c8)
  • Add conditional for node 16 test (aee1218e6)
  • Set max memory for nuxt2 release script globally (d1a5719cb)
  • Add workflow to release branches (bc28d536c)
  • Update pr condition (f8c7b34bd)
  • Update repo 🤣 (f88c1e645)
  • Allow specifying tag for edge releases (5fdb6a6d6)
  • Comment with link to tag of released version (f945cb197)
  • Pass tag as argument (1aec0e503)
  • Release edge versions of labelled prs (cdc42d044)
❤️ Contributors

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
webpack-contrib/eslint-webpack-plugin

v4.0.1

Compare Source

pnpm/pnpm

v7.32.4

Compare Source

Patch Changes

  • pnpm link -g <pkg-name> should not modify the package.json file #​4341.
  • Node.js range specified through the engines field should match prerelease versions #​6509.
  • pnpm publish --otp should work #​6514.

Our Gold Sponsors

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title chore(deps): update pnpm to v7.30.1 chore(deps): update pnpm to v7.30.1 - autoclosed Mar 24, 2023
@renovate renovate bot closed this Mar 24, 2023
@renovate renovate bot deleted the renovate/all-minor-patch branch March 24, 2023 00:57
@renovate renovate bot changed the title chore(deps): update pnpm to v7.30.1 - autoclosed chore(deps): update pnpm to v7.30.1 Mar 24, 2023
@renovate renovate bot reopened this Mar 24, 2023
@renovate renovate bot restored the renovate/all-minor-patch branch March 24, 2023 17:18
@renovate renovate bot changed the title chore(deps): update pnpm to v7.30.1 chore(deps): update all non-major dependencies Mar 24, 2023
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from cd84673 to 365a44e Compare March 27, 2023 19:42
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 76a10ad to 979ae7a Compare April 4, 2023 02:05
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 79a0d6f to 8997f15 Compare April 13, 2023 14:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 566cd01 to ec53614 Compare April 20, 2023 17:39
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ec53614 to 8c38a2d Compare April 28, 2023 20:00
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from a769d2a to a758037 Compare May 9, 2023 21:19
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from a758037 to eb5aa2f Compare May 16, 2023 13:51
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from eb5aa2f to c541b84 Compare May 18, 2023 11:33
@renovate renovate bot changed the title chore(deps): update all non-major dependencies chore(deps): update all non-major dependencies - autoclosed May 18, 2023
@renovate renovate bot closed this May 18, 2023
@renovate renovate bot deleted the renovate/all-minor-patch branch May 18, 2023 12:08
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