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

Merged
merged 1 commit into from
Jan 3, 2024
Merged

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

merged 1 commit into from
Jan 3, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 1, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@nuxt/kit (source) ^3.8.2 -> ^3.9.0 age adoption passing confidence
@nuxt/module-builder ^0.5.4 -> ^0.5.5 age adoption passing confidence
@nuxt/schema (source) ^3.8.2 -> ^3.9.0 age adoption passing confidence
@types/node (source) ^18.19.3 -> ^18.19.4 age adoption passing confidence
@typescript-eslint/eslint-plugin (source) ^6.15.0 -> ^6.16.0 age adoption passing confidence
@typescript-eslint/parser (source) ^6.15.0 -> ^6.16.0 age adoption passing confidence
nuxt (source) ^3.8.2 -> ^3.9.0 age adoption passing confidence
pnpm (source) 8.12.1 -> 8.13.1 age adoption passing confidence
prettier-plugin-jsdoc ^1.1.1 -> ^1.3.0 age adoption passing confidence
vue (source) ^3.3.13 -> ^3.4.3 age adoption passing confidence

Release Notes

nuxt/nuxt (@​nuxt/kit)

v3.9.0

Compare Source

3.9.0 is the next minor release.

👀 Highlights

A very merry Christmas to you and yours from all Nuxters involved in this release! 🎁🎄

We have lots of features packed into v3.9.0 and can't wait for you to try them out.

⚡️ Vite 5

This release comes with Vite 5 and Rollup 4 support. Module authors may need to check to ensure that any vite plugins you're creating are compatible with these latest releases.

This comes with a whole host of great improvements and bug fixes - check out the Vite changelog for more info.

✨ Vue 3.4 ready

This release is tested with the latest Vue 3.4 release candidate, and has the necessary configuration to take advantage of new features in Vue 3.4, including debugging hydration errors in production (just set debug: true) in your Nuxt config.

👉 To take advantage, just update your vue version once v3.4 is released, or try out the release candidate today:

{
  "dependencies": {
    "nuxt": "3.9.0",
    "vue": "3.4.0-rc.1",
    "vue-router": "latest"
  }
}
🏝️ Interactive Server Components

This is a highly-experimental update, but it's now possible to play around with interactive components within Nuxt server components. You'll need to enable this new feature additionally to component islands:

export default defineNuxtConfig({
  experimental: {
    componentIslands: {
      selectiveClient: true
    }
  }
})

Now, within a server component, you can specify components to hydrate by using the nuxt-client directive:

<NuxtLink :to="/" nuxt-client />

We're pretty excited about this one - so do let us know how you're using it! 🙏

🔥 Automatic Server Optimisations

We now use Vite's new AST-aware 'define' to perform more accurate replacements on server-side code, meaning code like this will no longer throw an error:

<script setup lang="ts">
if (document) {
  console.log(document.querySelector('div'))
}
</script>

This hasn't been possible until now because we haven't wanted to run the risk of accidentally replacing normal words like document within non-JS parts of your apps. But Vite's new define functionality is powered by esbuild and is syntax-aware, so we feel confident in enabling this functionality. Nevertheless, you can opt out if you need to:

export default defineNuxtConfig({
  hooks: {
    'vite:extendConfig' (config) {
      delete config.define!.document
    }
  }
})
🚦 Granular Loading API

We now have a new hook-based system for <NuxtLoadingIndicator>, including a useLoadingIndicator composable that lets you control/stop/start the loading state. You can also hook into page:loading:start and page:loading:end if you prefer.

You can read more in the docs and in the original PR (#​24010).

🏁 Run single events in callOnce

Sometimes you only want to run code once, no matter how many times you load a page - and you don't want to run it again on the client if it ran on the server.

For this, we have a new utility: callOnce (#​24787).

<script setup>
const websiteConfig = useState('config')

await callOnce(async () => {
  console.log('This will only be logged once')
  websiteConfig.value = await $fetch('https://my-cms.com/api/website-config')
})
</script>

Note that this utility is context-aware so it must be called in component setup function or Nuxt plugin, as with other Nuxt composables.

Read more in the docs.

🚨 Error Types

For a while now, errors returned by useAsyncData and useFetch have been typed pretty generically as Error. We've significantly improved the type possibilities for them to make them more accurate in terms of what you'll actually receive. (We normalise errors with the h3 createError utility under the hood, so they can be serialised from server to client, for example.)

We've tried to implement the type change in a backwards compatible way, but you might notice that you need to update the generic if you're manually configuring the generics for these composables. See (#​24396) for more information, and do let us know if you experience any issues.

🔥 Schema Performance

We've taken some time in this release to make some minor performance improvements, so you should notice some things are a bit faster. This is an ongoing project and we have ideas for improving initial load time of the Nuxt dev server.

✅ 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
  • nuxt: Warn when page uses a layout without <NuxtLayout> (#​24116)
  • kit: Support prepend option for addComponentsDir (#​24309)
  • kit: Allow customising logger options (#​24243)
  • nuxt: Allow readonly option for useCookie (#​24503)
  • nuxt: Add path to error.data when throwing 404 errors (#​24674)
  • kit: Load /module or /nuxt module subpath if it exists (#​24707)
  • nuxt: Layers support for spa loading template (#​24709)
  • nuxt: Expose refresh on islands and server components (#​24261)
  • nuxt: Add dedupe option for data fetching composables (#​24564)
  • vite: Replace browser globals with undefined on server (#​24711)
  • nuxt: Allow plugins to specify dependencies (#​24127)
  • kit: Add new addServerScanDir composable (#​24001)
  • nuxt: Transform setup within defineComponent options (#​24515)
  • nuxt: Allow customising fallback layout (#​24777)
  • nuxt: useRequestHeader utility (#​24781)
  • nuxt: Move loading api behind hooks (#​24010)
  • nuxt: Add callOnce util to allow running code only once (#​24787)
  • nuxt: Allow client components within NuxtIsland (#​22649)
  • schema: Default to bundler module resolution (#​22821)
  • kit,nuxt,vite,webpack: Add toArray util (#​24857)
🔥 Performance
  • vite: Avoid duplicate resolve operation (#​24736)
  • nuxt: Avoid duplicate iterations over layers (#​24730)
  • kit: Avoid duplicate join operation (#​24717)
  • vite: Simplify manifest property acccess (#​24715)
  • nuxt: Don't dedupe fewer than two middleware/plugins (#​24718)
  • schema: Avoid duplicate get operations (#​24734)
  • schema: Use parallel promises (#​24771)
  • nuxt: Avoid duplicate useRuntimeConfig call (#​24843)
  • vite: Avoid duplicate JSON.stringify operation (#​24848)
🩹 Fixes
  • nuxt: Avoid recursive ssr errors (#​24399)
  • nuxt: Improve path resolve for import.d.ts (#​24413)
  • nuxt: Remove experimental reactivityTransform (vue 3.4) (#​24477)
  • nuxt: Ignore manifest when prerendering (#​24504)
  • nuxt: Don't strip literals from template in <DevOnly> (#​24511)
  • vite: Use isBuiltin polyfill for greater node support (#​24512)
  • nuxt: Island components with number prefix (#​24469)
  • nuxt: Use consistent annotations for tree-shaking (#​24514)
  • nuxt: Skip prerendering all pages in hash mode (#​24517)
  • nuxt: Skip router middleware/redirections for islands (#​24421)
  • nuxt: Remove trailing slash before checking if prerendered (#​24516)
  • nuxt: Skip check for <NuxtLayout> usage in islands (#​24529)
  • vite,webpack: Don't add type checker/analyzer when testing (#​24608)
  • nuxt: Do not try auto-install outside of a Nuxt context (#​24605)
  • nuxt: Merge and apply layer hooks (#​24639)
  • nuxt: Only add/remove trailing slash for http protocols (#​23296)
  • nuxt: Ensure error in useAsyncData has correct type (#​24396)
  • nuxt: Add appManifest middleware after modules run (#​24786)
  • nuxt: Revert async transform of setup within defineComponent (#​24784)
  • nuxt: Eager load island components map (#​24584)
  • nuxt: Register override hooks separately (#​24833)
  • nuxt: Add __VUE_PROD_HYDRATION_MISMATCH_DETAILS__ (#​24836)
  • kit: Auto-detect mode from filePath for addComponent (#​24835)
  • schema: Revert bundler module resolution due to lack of support (22ce98d61)
  • kit: Don't add local ~/modules dirs to modulesDir (#​24457)
💅 Refactors
  • nuxt: Use defineComponent to infer prop types for router-link stub (dc0e8347b)
  • nuxt: Opt-in to future jiti.import for schema (#​24526)
  • nuxt: Remove process.* usage in nuxt vue app (#​24749)
  • schema: Introduce future and features namespace (#​24880)
📖 Documentation
🏡 Chore
✅ Tests
  • Re-enable accidentally disabled unit tests 🙈 (b443de230)
  • Add basic benchmark tests (#​24846)
  • Update vitest coverage exclusions (a46b0c876)
🤖 CI
  • Don't skip releases based on commit body (#​24554)
  • Label pull requests based on their target branch (#​24468)
  • Update options for GitHub app token generation (#​24565)
  • Notify nuxt/bridge when composables change (#​24752)
  • Don't run benchmark on main commits by default (064615e8c)
  • Temporarily disable codspeed (a39d311d3)
❤️ Contributors
nuxt/module-builder (@​nuxt/module-builder)

v0.5.5

Compare Source

compare changes

🩹 Fixes
  • Rename RuntimeModuleHooks to ModuleRuntimeHooks (#​194)
  • Use import with extension in generated .d.mts file (#​202)
📖 Documentation
  • Remove reference to ModulePrivateRuntimeConfig (34ee148)
🏡 Chore
  • Add shell emulator for Windows (#​191)
  • Fix example package.json (#​192)
✅ Tests
  • Add root + module type tests (#​198)
🤖 CI
❤️ Contributors
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v6.16.0

Compare Source

Bug Fixes
  • eslint-plugin: [unbound-method] exempt all non-Promise built-in statics (#​8096) (3182959)
Features
  • eslint-plugin: deprecate formatting (meta.type: layout) rules (#​8073) (04dea84)
  • eslint-plugin: deprecate no-extra-semi in favor of ESLint Stylistic equivalent (#​8123) (9368bf3)

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v6.16.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

You can read about our versioning strategy and releases on our website.

pnpm/pnpm (pnpm)

v8.13.1

Minor Changes

  • New commands added for inspecting the store:

    • pnpm cat-index: Prints the index file of a specific package in the store. The package is specified by its name and version:

      pnpm cat-index <pkg name>@&#8203;<pkg version>

    • pnpm cat-file: Prints the contents of a file based on the hash value stored in the index file. For example:

      pnpm cat-file sha512-mvavhfVcEREI7d8dfvfvIkuBLnx7+rrkHHnPi8mpEDUlNpY4CUY+CvJ5mrrLl18iQYo1odFwBV7z/cOypG7xxQ==

    • (EXPERIMENTAL) pnpm find-hash: Lists the packages that include the file with the specified hash. For example:

      pnpm find-hash sha512-mvavhfVcEREI7d8dfvfvIkuBLnx7+rrkHHnPi8mpEDUlNpY4CUY+CvJ5mrrLl18iQYo1odFwBV7z/cOypG7xxQ==

      This command is experimental. We might change how it behaves.

    Related issue: #​7413.

  • A new setting added for symlinking injected dependencies from the workspace, if their dependencies use the same peer dependencies as the dependent package. The setting is called dedupe-injected-deps #​7416.

  • Use --fail-if-no-match if you want the CLI fail if no packages were matched by the command #​7403.

Patch Changes

  • pnpm list --parseable should not print the same dependency multiple times #​7429.
  • Fix error message texts in the pnpm env commands #​7456.
  • Better support for light themed terminals by the pnpm update --interactive command #​7439.
  • Fix EPERM error that occasionally happened on Windows during renames in the store #​7213.
  • Fix error as in update -i -r with Git specifiers #​7415.
  • Added support for boolean values in 'bundleDependencies' package.json fields when installing a dependency. Fix to properly handle 'bundledDependencies' alias #​7411.

Our Gold Sponsors

Our Silver Sponsors
hosseinmd/prettier-plugin-jsdoc (prettier-plugin-jsdoc)

v1.3.0

Compare Source

vuejs/core (vue)

v3.4.3

Compare Source

Bug Fixes
  • compiler-sfc: respect sfc parse options in cache key (b8d58ec)

v3.4.2

Compare Source

Bug Fixes

v3.4.1

Compare Source

Bug Fixes
  • compat: correct enum value for COMPILER_FILTERS feature (#​9875) (77d33e2)
  • defineModel: always default modifiers to empty object (9bc3c7e), closes #​9945
  • defineModel: support local mutation when only prop but no listener is passed (97ce041)
  • types: fix defineModel watch type error (#​9942) (4af8583), closes #​9939
Features

v3.4.0

Compare Source

Read this blog post for an overview of the release highlights.

Potential Actions Needed

  1. To fully leverage new features in 3.4, it is recommended to also update the following dependencies when upgrading to 3.4:

    • Volar / vue-tsc@^1.8.27 (required)
    • @​vitejs/plugin-vue@​^5.0.0 (if using Vite)
    • nuxt@^3.9.0 (if using Nuxt)
    • vue-loader@^17.4.0 (if using webpack or vue-cli)

  2. If using TSX with Vue, check actions needed in Removed: Global JSX Namespace.

  3. Make sure you are no longer using any deprecated features (if you are, you should have warnings in the console telling you so). They may have been removed in 3.4.

Features
Performance Improvements
  • compiler-sfc: avoid sfc source map unnecessary serialization and parsing (f15d2f6)
  • compiler-sfc: remove magic-string trim on script (e8e3ec6)
  • compiler-sfc: use faster source map addMapping (50cde7c)
  • compiler-core: optimize away isBuiltInType (66c0ed0)
  • compiler-core: optimize position cloning (2073236)
  • codegen: optimize line / column calculation during codegen (3be53d9)
  • codegen: optimize source map generation (c11002f)
  • shared: optimize makeMap (ae6fba9)
BREAKING CHANGES
Global JSX Registration Removed

Starting in 3.4, Vue no longer registers the global JSX namespace by default. This is necessary to avoid global namespace collision with React so that TSX of both libs can co-exist in the same project. This should not affect SFC-only users with latest version of Volar.

If you are using TSX, there are two options:

  1. Explicitly set jsxImportSource to 'vue' in tsconfig.json before upgrading to 3.4. You can also opt-in per file by adding a /* @&#8203;jsxImportSource vue */ comment at the top of the file.

  2. If you have code that depends on the presence of the global JSX namespace, e.g. usage of types like JSX.Element etc., you can retain the exact pre-3.4 global behavior by explicitly referencing vue/jsx, which registers the global JSX namespace.

Note that this is a type-only breaking change in a minor release, which adheres to our release policy.

Deprecated Features Removed
  • Reactivity Transform was marked deprecated in 3.3 and is now removed in 3.4. This change does not require a major due to the feature being experimental. Users who wish to continue using the feature can do so via the Vue Macros plugin.
  • app.config.unwrapInjectedRef has been removed. It was deprecated and enabled by default in 3.3. In 3.4 it is no longer possible to disable this behavior.
  • @vnodeXXX event listeners in templates are now a compiler error instead of a deprecation warning. Use @vue:XXX listeners instead.
  • v-is directive has been removed. It was deprecated in 3.3. Use the is attribute with vue: prefix instead.

Configuration

📅 Schedule: Branch creation - "before 2am on monday" (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.

👻 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.

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Jan 1, 2024 •
edited
Loading

⚠️ No Changeset found

Latest commit: 4e90c63

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@netlify Netlify
Copy link

netlify bot commented Jan 1, 2024 •
edited
Loading

✅ Deploy Preview for vintl-nuxt ready!

Name Link
🔨 Latest commit 4e90c63
🔍 Latest deploy log https://app.netlify.com/sites/vintl-nuxt/deploys/659414e580956c0008ffb6e8
😎 Deploy Preview https://deploy-preview-100--vintl-nuxt.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from ca3b911 to ed4483f Compare January 2, 2024 04:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from ed4483f to 4e90c63 Compare January 2, 2024 13:51
@brawaru brawaru merged commit d3a1cd3 into main Jan 3, 2024
6 checks passed
@brawaru brawaru deleted the renovate/all-minor-patch branch January 3, 2024 14:45
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.
1 participant
@brawaru