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 dependency nuxt to v3.14.159 #482

Merged
merged 2 commits into from
Nov 10, 2024
Merged

chore(deps): update dependency nuxt to v3.14.159 #482

merged 2 commits into from
Nov 10, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 10, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
nuxt (source) 3.13.2 -> 3.14.159 age adoption passing confidence

Release Notes

nuxt/nuxt (nuxt)

v3.14.159

Compare Source

3.14.159 is a hotfix release to address regressions in v3.14.

We're leaning into the π theme - future patch releases of this minor version will just continue adding digits. (Sorry for any inconvenience! 😆)

👉 Changelog

compare changes

🩹 Fixes
  • nuxt: Update nitropack preset directory (#​29780)
  • kit: Fall back to meta version if there's no module.json (#​29793)
  • kit: Use mlly to resolve module paths to avoid cjs fallback (#​29799)
  • webpack,rspack: Add adapter for webpack-dev-middleware (#​29806)
  • nuxt: Remove null-byte prefix for virtual files (#​29809)
  • kit: Convert module path to file url before reading meta (fb833ac64)
📖 Documentation
🏡 Chore
❤️ Contributors

v3.14.0

Compare Source

3.14.0 is the next minor release.

👀 Highlights

Behind the scenes, a lot has been going on in preparation for the release of Nuxt v4 (particularly on the unjs side with preparations for Nitro v3!)

⚡️ Faster starts powered by jiti

Loading the nuxt config file, as well as modules and other build-time code, is now powered by jiti v2. You can see more about the release in the jiti v2 release notes, but one of the most important pieces is native node esm import (where possible), which should mean a faster start. ✨

📂 Shared folder for code and types shared with client/server

You should never import Vue app code in your nitro code (or the other way around). But this has meant a friction point when it comes to sharing types or utilities that don't rely on the nitro/vue contexts.

For this, we have a new shared/ folder (#​28682). You can't import Vue or nitro code into files in this folder, but it produces auto-imports you can consume throughout the rest of your app.

If needed you can use the new #shared alias which points to this folder.

The shared folder is alongside your server/ folder. (If you're using compatibilityVersion: 4, this means it's not inside your app/ folder.)

🦀 rspack builder

We're excited to announce a new first-class Nuxt builder for rspack. It's still experimental but we've refactored the internal Nuxt virtual file system to use unplugin to make this possible.

Let us know if you like it - and feel free to raise any issues you experience with it.

👉 To try it out, you can use this starter - or just install @nuxt/rspack-builder and set builder: 'rspack' in your nuxt config file.

✨ New composables

We have new useResponseHeader and useRuntimeHook composables (#​27131 and #​29741).

🔧 New module utilities

We now have a new addServerTemplate utility (#​29320) for adding virtual files for access inside nitro runtime routes.

🚧 v4 changes

We've merged some changes which only take effect with compatibilityVersion: 4, but which you can opt-into earlier.

  1. previously, if you had a component like ~/components/App/Header.vue this would be visible in your devtools as <Header>. From v4 we ensure this is <AppHeader>, but it's opt-in to avoid breaking any manual <KeepAlive> you might have implemented. (#​28745).

  2. Nuxt scans page metadata from your files, before calling pages:extend. But this has led to some confusing behaviour, as pages added at this point do not end up having their page metadata respected. So we now do not scan metadata before calling pages:extend. Instead, we have a new pages:resolved hook, which is called after pages:extend, after all pages have been augmented with their metadata. I'd recommend opting into this by setting experimental.scanPageMeta to after-resolve, as it solves a number of bugs.

🗺️ Roadmap to v3.15

They didn't quite make it in time for v3.14 but for the next minor release you can expect (among other things):

✅ Upgrading

As usual, our recommendation for upgrading is to run:

npx nuxi@latest 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
  • deps: Upgrade to latest version of jiti (#​27995)
  • kit,nuxt,vite,webpack: Reimplement cjs utils using jiti (#​29073)
  • nuxt: Normalise component names to match nuxt pattern (#​28745)
  • kit,schema: Add addServerTemplate utility (#​29320)
  • nuxt: Add useResponseHeader composable (#​27131)
  • rspack,webpack: Add rspack builder (#​29142)
  • nuxt,schema: pages:resolved hook + scan meta post extend (#​28861)
  • nuxt: Allow enabling route props in definePageMeta (#​29586)
  • schema,nuxt: Add shared/ folder and #shared alias (#​28682)
  • nuxt: Allow chunk error or manifest update -> reload (#​28160)
  • nuxt: Add useRuntimeHook composable (#​29741)
🔥 Performance
  • nuxt: Remove unneeded second call to useNuxtApp (#​29514)
  • vite: Avoid redundant postcss plugins overwrite (#​29619)
  • kit,nuxt,vite,webpack: Hoist regex patterns (#​29620)
🩹 Fixes
  • nuxt: Simplify plugin InjectionType template conditional (#​29023)
  • nuxt: Access server build from webpack memfs (#​29027)
  • nuxt: Do not resolve non-absolute component paths (#​29036)
  • nuxt: Defer unsetting error handler until suspense resolves (#​29037)
  • nuxt: Pass DOMException as fetch abort exception (#​29058)
  • vite: Don't force protocol if disabled devServer.https (#​29049)
  • nuxt: Empty nitro buildDir in dev mode (#​29068)
  • nuxt: Don't resolve relative import type paths for deps (#​29069)
  • kit: Handle passing 'bare' relative paths to modules (c7fecd8a1)
  • kit: Try resolving module path from each node_modules dir (70a622d43)
  • kit,vite,webpack: Resolve postcss paths from each modules dir (#​29096)
  • kit,vite,webpack: Strip node_modules/ from parent urls (5bd42c893)
  • nuxt: Add crossorigin attribute for stylesheets (#​29138)
  • nuxt: Use routeRules to hint pages to prerender (#​29172)
  • nuxt: Pass absolute external link urls to link:prefetch (#​29321)
  • nuxt: Error on build when required module is missing (#​29287)
  • nuxt: Prevent 404 when hitting component test endpoint (cb725f014)
  • nuxt: Avoid throwing 404 error before middleware finishes (#​29054)
  • schema: Use ConfigLayer type from c12 (#​29370)
  • nuxt: Fix nested page types in typedPages (#​29352)
  • nuxt: Allow islands to manipulate head client-side (#​29186)
  • vite: Dim repeat count in logs (#​29392)
  • schema: Mark configFile as required in layer type (3bbcd7d21)
  • nuxt: Remove vue compiler hints from auto import (#​29713)
  • vite: Update signature for createIsExternal (686be8168)
  • nuxt: Respect existing props value in definePageMeta (#​29683)
  • schema: Hoist nitropack/types to ensure api routes are typed (54096875e)
💅 Refactors
  • nuxt: Use addBuildPlugin internally (#​29157)
  • nuxt,schema,vite,webpack: Use unplugin for vfs (#​29165)
📖 Documentation
  • Use defineNuxtComponent instead of defineComponent (#​29011)
  • Remove duotone icons for clarity (#​29040)
  • Fix typo (#​29045)
  • Remove specific Nuxt 4 release date (#​29151)
  • Remove redundant newlines and indentations (#​29190)
  • Add links to short videos from daniel (#​29185)
  • Fix comments typo in auto-imports example (#​29195)
  • Add missing word (#​29230)
  • Add a section about useRequestFetch and event.$fetch (#​29099)
  • Add example of typing custom useFetch errors (#​29253)
  • Ensure manifest code snippet works with pnpm (#​29273)
  • Consistent directory structure (#​29292)
  • Update to new ofetch headers for interceptors (#​29118)
  • Mention upgrading third-party configs (#​27768)
  • Improve explanation of ssr + data fetching (#​29010)
  • Add a description for .env.test (#​29398)
  • Add section on 'updateAppConfig' in the 'app.config' page (#​29397)
  • Add example to navigateTo util (#​29611)
  • Remove mockImplementation() call (#​29669)
  • Update lifecycle hooks (#​29678)
  • Type cast api plugin in custom usefetch example (#​29756)
  • Correct some errors about proxying headers with $fetch (#​29755)
  • Add information on --envName flag (#​28909)
  • Add error expectation (09885b87e)
📦 Build
  • ui-templates: Switch to beasties (1b5391182)
🏡 Chore
✅ Tests
🤖 CI
❤️ Contributors

Configuration

📅 Schedule: Branch creation - "before 12pm on Sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate Renovate
Copy link
Contributor Author

renovate bot commented Nov 10, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock
node:fs:1363
  const result = binding.mkdir(
                         ^

Error: ENOENT: no such file or directory, mkdir '/home/ubuntu/.cache/node/corepack/v1'
    at mkdirSync (node:fs:1363:26)
    at getTemporaryFolder (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:21486:27)
    at download (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:21760:21)
    at installVersion (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:21854:61)
    at async Engine.ensurePackageManager (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:22310:32)
    at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:22410:25)
    at async Object.runMain (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:23096:5) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'mkdir',
  path: '/home/ubuntu/.cache/node/corepack/v1'
}

Node.js v22.11.0

@favna favna merged commit 01c0c37 into main Nov 10, 2024
5 checks passed
@favna favna deleted the renovate/all-minor-patch branch November 10, 2024 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@renovate-approve-2 renovate-approve-2[bot] renovate-approve-2[bot] approved these changes

@renovate-approve renovate-approve[bot] renovate-approve[bot] approved these changes

@favna favna favna approved these changes

Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@favna