Vite
v5.1.0-beta.4

#vite

5.1.0-beta.4 (2024-01-26)

● perf: lazy load rollup during dev (#15621) (6f88a90), closes #15621

● perf: use workspace root for fs cache (#15712) (8815763), closes #15712

● chore: remove unneeded normalizePath (#15713) (92f2747), closes #15713

● chore(proxy): update proxy error info (#15678) (09bd58d), closes #15678

● feat: enable fs.cachedChecks by default (#15704) (a05c709), closes #15704

● feat(optimizer): holdUntilCrawlEnd option (#15244) (b7c6629), closes #15244

● fix: normalize prettify url (#15705) (98bc3dc), closes #15705

● fix: windows add/delete file (3a7b650)

● fix(build): build error message output twice (#15664) (74382b9), closes #15664

● fix(hmr): pass id in parseImports for better debugging DX (#15707) (fb4bddc), closes #15707

● fix(node): remove timestamp query of staticImportedUrls (#15663) (6c4bf26), closes #15663

● fix(preview): set isPreview true (#15695) (93fce55), closes #15695

Vite
v5.1.0-beta.5

#vite

5.1.0-beta.5 (2024-01-27)

● fix: do not init optimizer during build (#15727) (a08f646), closes #15727

● fix(deps): update all non-major dependencies (#15675) (4d9363a), closes #15675

NuxtJS
v3.10.0

#nuxt3.10.0 is the next minor/feature release.

👀 Highlights

v3.10 comes quite close on the heels of v3.9, but it's packed with features and fixes. Here are a few highlights.

✨ Experimental shared asyncData when prerendering

When prerendering routes, we can end up refetching the same data over and over again. In Nuxt 2 it was possible to create a 'payload' which could be fetched once and then accessed in every page (and this is of course possible to do manually in Nuxt 3 - see this article).

With #24894, we are now able to do this automatically for you when prerendering. Your useAsyncData and useFetch calls will be deduplicated and cached between renders of your site.

export defineNuxtConfig({
  experimental: {
    sharedPrerenderData: true
  }
}) 

Important

It is particularly important to make sure that any unique key of your data is always resolvable to the same data. For example, if you are using useAsyncData to fetch data related to a particular page, you should provide a key that uniquely matches that data. (useFetch should do this automatically.)

👉 See full documentation.

🆔 SSR-safe accessible unique ID creation

We now ship a useId composable for generating SSR-safe unique IDs (#23368). This allows creating more accessible interfaces in your app. For example:
">

<script setup>
const emailId = useId()
const passwordId = useId()
>script>

<template>
  <form>
    <label :for="emailId">Email>label>
    <input
      :id="emailId"
      name="email"
      type="email"
    >
    <label :for="passwordId">Password>label>
    <input
      :id="passwordId"
      name="password"
      type="password"
    >
  >form>
>template>

✍️ Extending app/router.options

It's now possible for module authors to inject their own router.options files (#24922). The new pages:routerOptions hook allows module authors to do things like add custom scrollBehavior or add runtime augmenting of routes.

👉 See full documentation.

Client-side Node.js support

We now support (experimentally) polyfilling key Node.js built-ins (#25028), just as we already do via Nitro on the server when deploying to non-Node environments.

That means that, within your client-side code, you can import directly from Node built-ins (node: and node imports are supported). However, nothing is globally injected for you, to avoid increasing your bundle size unnecessarily. You can either import them where needed.

import { Buffer } from 'node:buffer'
import process from 'node:process'

Or provide your own polyfill, for example, inside a Nuxt plugin.

// ~/plugins/node.client.ts
import { Buffer } from 'node:buffer'
import process from 'node:process'

globalThis.Buffer = Buffer
globalThis.process = process

export default defineNuxtPlugin({})

This should make life easier for users who are working with libraries without proper browser support. However, because of the risk in increasing your bundle unnecessarily, we would strongly urge users to choose other alternatives if at all possible.

🍪 Better cookie reactivity

We now allow you to opt-in to using the CookieStore. If browser support is present, this will then be used instead of a BroadcastChannel to update useCookie values reactively when the cookies are updated (#25198).

This also comes paired with a new composable, refreshCookie which allows manually refreshing cookie values, such as after performing a request. See full documentation.

🏥 Detecting anti-patterns

In this release, we've also shipped a range of features to detect potential bugs and performance problems.

● We now will throw an error if setInterval is used on server (#25259).
● We warn (in development only) if data fetch composables are used wrongly (#25071), such as outside of a plugin or setup context.
● We warn (in development only) if you are not using but have the vue-router integration enabled (#25490). ( should not be used on its own.)

🧂 Granular view transitions support

It's now possible to control view transitions support on a per-page basis, using definePageMeta (#25264).

You need to have experimental view transitions support enabled first:

export default defineNuxtConfig({
  experimental: {
    viewTransition: true
  },
  app: {
    // you can disable them globally if necessary (they are enabled by default)
    viewTransition: false
  }
})

And you can opt in/out granularly:
definePageMeta({ viewTransition: false }) ">

// ~/pages/index.vue
<script setup lang="ts">
definePageMeta({
  viewTransition: false
})
script>

Finally, Nuxt will not apply View Transitions if the user's browser matches prefers-reduced-motion: reduce (#22292). You can set viewTransition: 'always'; it will then be up to you to respect the user's preference.

🏗️ Build-time route metadata

It's now possible to access routing metadata defined in definePageMeta at build-time, allowing modules and hooks to modify and change these values (#25210).

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

Please, experiment with this and let us know how it works for you. We hope to improve performance and enable this by default in a future release so modules like @nuxtjs/i18n and others can provide a deeper integration with routing options set in definePageMeta.

📦 Bundler module resolution

With #24837, we are now opting in to the TypeScript bundler resolution which should more closely resemble the actual way that we resolve subpath imports for modules in Nuxt projects.

'Bundler' module resolution is recommended by Vue and by Vite, but unfortunately there are still many packages that do not have the correct entries in their package.json.

As part of this, we opened 85 PRs across the ecosystem to test switching the default, and identified and fixed some issues.

If you need to switch off this behaviour, you can do so. However, please consider raising an issue (feel free to tag me in it) in the library or module's repo so it can be resolved at source.

export default defineNuxtConfig({
  future: {
    typescriptBundlerResolution: false
  }
})

✅ 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: tryUseNuxtApp composable (#25031)
● nuxt: Add experimental sharedPrerenderData option (#24894)
● schema: Default to bundler module resolution (#24837)
● nuxt: Warn if data fetch composables are used wrongly (#25071)
● nuxt: Add pages:routerOptions hook (#24922)
● Experimental client-side Node.js compatibility (#25028)
● nuxt: Throw error if setInterval is used on server (#25259)
● nuxt: refreshCookie + experimental CookieStore support (#25198)
● nuxt: Allow controlling view transitions in page meta (#25264)
● nuxt: Slow down loading indicator when approaching 100% (#25119)
● nuxt: Experimentally extract route metadata at build time (#25210)
● nuxt: useId composable (#23368)

🔥 Performance

● vite: Avoid endsWith when checking for whitespace (#24746)

🩹 Fixes

● nuxt: Disable View Transitions if prefers-reduced-motion (#22292)
● nuxt: Add declaration file with correct node16 imports (#25266)
● nuxt: Allow omitting fallback in island response (#25296)
● schema: Remove defineModel option as it is now stable (#25306)
● nuxt: Overwrite island payload instead of merging (#25299)
● vite: Pass hidden sourcemap values to vite (#25329)
● nuxt: ...

This is fine.
I will try fix it. In my configuration this should create a post on telegra.ph by length limit.
Idk why this isn't work 🤡.

vue-i18n-next
v9.9.1

#vue_i18n #i18n #vue_i18n_next

What's Changed

🐛 Bug Fixes

● fix: key-value style messages broken after merging (#1717) by @chojnicki in #1718

📝️ Documentations

● chore(typo): update injection.md by @quentinmcq in #1716
● Update syntax.md by @hinogi in #1701

New Contributors

● @chojnicki made their first contribution in #1718
● @quentinmcq made their first contribution in #1716
● @hinogi made their first contribution in #1701

Full Changelog: v9.9.0...v9.9.1

Vuetify
v3.5.2

#vuetify

🔧 Bug Fixes

● date: format dayOfMonth with NumberFormat instead of DateTimeFormat (d0136e0), closes #18093
● group: use index as value if not provided (#19119) (1a23d47), closes #19107
● VColorPicker: parse partial input in the current mode (8c01536), closes #18977
● VDataTable: use header height from density (f23bcb0), closes #18795
● VDatePicker: use start of month for month model (9eb82db), closes #19087 #19116
● VDatePicker: don't truncate day names in other locales (9ceade2), closes #19013
● VDatePicker: correct generic model type when multiple (c48c2a7)
● VForm: always update errors in slot (c0c28d1)
● VMenu: set aria-owns id on overlay element (916c9ef), closes #19054
● VOverlay: override scroll-behavior when restoring scroll position (2ddc9c5), closes #19109
● VWindow: increase pointer-event specificity (b560ead)

🔬 Code Refactoring

● fix CalendarProps types (adba173)

Other Commmits

● chore(release): publish v3.5.2 (0f5ba93)

● chore(VSelectionControl/VLabel): update click implementation (3095220)
● docs(OneSubCard): update styling (79ae722)
● docs(OneSubscription): add billing management link (a7e07b7)
● docs(PinnedItems): sort pinned items before save (6da78af)
● docs(why-vuetify): update page title (05c3a23)
● docs(roadmap): update 2024 roadmap (dfbe631)
● test(VDatePicker): add range test (dd32fc6)
● docs(components/all): remove duplicated Bottom Sheet Component (#19082) (594b61c)
● docs(text-decoration): fix example format issue (#19075) (b9fa960)
● docs: update various page's emphasize status (6af93f8)
● docs(Banner): update display logic (2d70c07)
● docs(sass-variables): make example more clear (416a9a5)
● docs(VAppBar): add icon and title to usage example (e6ec41c), closes #18922 #18930
● docs(VDatePicker): remove range from props (3fad1e3)
● docs(roadmap): update roadmap (132dce2)
● docs(scrolling): add version alert (b64e53d)

Vite
v5.1.0-beta.6

#vite

5.1.0-beta.6 (2024-02-01)

● feat: experimental Vite Runtime API (#12165) (8b3ab07), closes #12165

● fix: add ref() and unref() to chokidar.d.ts for typescript build to work (#15706) (6b45037), closes #15706

● perf: simplify explicit import mark in import analysis (#15724) (2805b2d), closes #15724

NuxtJS
v3.10.1

#nuxt3.10.1 is a regularly-scheduled 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 vue and unjs ecosystems.

👉 Changelog

compare changes

🔥 Performance

● nuxt: Clear route meta build cache when pages change (#25514)

🩹 Fixes

● nuxt: Fix syntax error when serializing route meta (#25515)
● nuxt: Only request animation frame on client (#25569)
● schema: Correctly set value for app.viewTransition (#25581)
● nuxt: Correct return type of refresh functions (#25568)
● nuxt: Broadcast cookie change in correct format (#25598)
● nuxt: Generate typed route declarations when building (#25593)
● nuxt: Remove key from useId type signature (#25614)
● nuxt: Remove $ from generated id in useId (#25615)
● nuxt: Don't set default rel for same-site external links (#25600)

● nuxt: Warn if inheritAttrs: false when using useId (#25616)
● nuxt: Fetch non-server rendered islands when hydrating (#25613)
● nuxt: Don't check page/layout usage when redirecting (#25628)

💅 Refactors

● nuxt: Improve NuxtLink types (#25599)

📖 Documentation

● Correct typo (#25523)
● Add and link to a section on Nuxt context (#23546)
● Explain how to set defaults in nuxt config (#25610)

🏡 Chore

● Use pathe in internal tests (e33cec958)
● nuxt: Rename nuxt -> nuxtApp internally for consistency (c5d5932f5)

🤖 CI

● Fix playwright cache (#25527)
● Retry flaky test when running in Windows with Webpack (#25536)
● Retry flaky test when running in Windows with Webpack (#25543)
● Retry flaky test when using Webpack (#25550)
● Simplify label PR workflow (#25579)

❤️ Contributors

● Daniel Roe (@danielroe)
● Julien Huang (@huang-julien)
● Harlan Wilton (@harlan-zw)
● Bobbie Goede (@BobbieGoede)
● xjccc (@xjccc)
● Ryan Clements (@RyanClementsHax)
● Enkot (@enkot)
● Damian Głowala (@DamianGlowala)
● Ted de Koning (@tdekoning)
● Troy Ciesco (@troyciesco)
● Michael Brevard (@GalacticHypernova)
● Arslan Ali (@warlock1996)

Vite
v5.1.0-beta.7

#vite

5.1.0-beta.7 (2024-02-07)

● fix: disable fs.cachedChecks for custom watch ignore patterns (#15828) (9070be3), closes #15828

● fix: judge next dirent cache type (#15787) (5fbeba3), closes #15787

● fix: scan entries when the root is in node_modules (#15746) (c3e83bb), closes #15746

● fix(config): improved warning when root path includes bad characters (#15761) (1c0dc3d), closes #15761

● docs: fix typos in CHANGELOG (#15825) (3ee4e7b), closes #15825

● perf: use transform cache by resolved id (#15785) (78d838a), closes #15785

● chore: release notes (#15777) (775bb50), closes #15777

Vuetify
v3.5.3

#vuetify

🔧 Bug Fixes

● VAvatar: provide component defaults to default slot (a765a6b)
● VCheckbox/VSwitch: incorrect default flex inherited from VInput (de501c3)
● VChip: prevent content div from taking activator target (e9a5a4a)
● VColorPicker: correct value gradient (d1251f5), closes #19187
● VListItemAction: adjust spacing when using the start/end props (1f63ca8)
● VOverlay: add missing opacity property (a27026f), closes #19182

🔄 Reverts

● Revert "fix(VOverlay): don't render if disabled" (0b79317), closes #19144

Other Commmits

● chore(release): publish v3.5.3 (5db19eb)
● docs(upgrade-guide): add v-navigation-drawer section (b5ba4a5), closes #19162
● docs(one): fix re-sub after billing failure (d8c2943)
● docs(AvatarOption): add new images (46f1b0e)
● chore(PerkOptions): update displayed pricing (b0543e7)
● chore(README): update sponsors (0f6c173)
● chore(package): update @vuetify/one (29a8e11)

Vue 3
v3.4.16

#vue #vue3

3.4.16 (2024-02-08)
Bug Fixes
● compiler-core: handle same-name shorthand edge case for in-DOM templates (cb87b62), closes #10280

● compiler-core: support v-bind shorthand syntax for dynamic slot name (#10218) (91f058a), closes #10213

● deps: update compiler (#10269) (336bb65)

● hydration: fix SFC style v-bind hydration mismatch warnings (#10250) (f0b5f7e), closes #10215

● reactivity: avoid infinite recursion from side effects in computed getter (#10232) (0bced13), closes #10214

● reactivity: handle MaybeDirty recurse (#10187) (6c7e0bd), closes #10185

● reactivity: skip non-extensible objects when using markRaw (#10289) (2312184), closes #10288

● runtime-core: avoid inlining isShallow (#10238) (53eee72)

● runtime-core: support for nested calls to runWithContext (#10261) (75e02b5), closes #10260

● runtime-dom: ensure v-show respects display value set via v-bind (#10161) (9b19f09), closes #10151

● runtime-dom: fix option selected update failed (#10200) (f31d782), closes #10194 #10267

Reverts
● perf(templateRef): avoid double render when using template ref on v-for (eb1b911), closes #9908 #10210 #10234

Vite
v5.1.0

#vite

5.1.0 (2024-02-08)

● chore: revert #15746 (#15839) (ed875f8), closes #15746 #15839

● fix: pass customLogger to loadConfigFromFile (fix #15824) (#15831) (55a3427), closes #15824 #15831

● fix(deps): update all non-major dependencies (#15803) (e0a6ef2), closes #15803

● refactor: remove vite build --force (#15837) (f1a4242), closes #15837

Vite
[email protected]

#vite

Please refer to CHANGELOG.md for details.

Quasar
@quasar/app-vite-v2.0.0-beta.1

#quasar

Important! There is an "Upgrade guide" page under the "Quasar CLI with Vite" menu section in the docs. Please read it top to bottom before proceeding with the upgrade.

Notable breaking changes

● Minimum Node.js version is now 18 (mainly due to Vite 5)
● We have shifted towards an ESM style for the whole Quasar project folder, so many default project files now require ESM code (although using .cjs as an extension for these files is supported, but you will most likely need to rename the extension should you not wish to change anything). One example is the /quasar.config.js file which now it's assumed to be ESM too (so change from .js to .cjs should you still want a CommonJs file).
● The "test" cmd was removed due to latest updates for @quasar/testing-* packages. See here
● The "clean" cmd has been re-designed. Type "quasar clean -h" in your upgraded Quasar project folder for more info.

● Typescript detection is based on the quasar.config file being in TS form (quasar.config.ts) and tsconfig.json file presence.
● feat+refactor(app-vite): ability to run multiple modes + dev/build simultaneously (huge effort!)
● SSR and Electron modes now build in ESM format.
● We will detail more breaking changes for each of the Quasar modes in the docs. There is an "Upgrade guide" page under the "Quasar CLI with Vite" menu section.

Highlights on what's new

Some of the work below has already been backported to the old @quasar/app-vite v1, but posting here for reader's awareness.

● feat(app-vite): upgrade to Vite 5
● feat(app-vite): ability to run multiple quasar dev/build commands simultaneously (example: can run "quasar dev -m capacitor" and "quasar dev -m ssr" and "quasar dev -m capacitor -T ios" simultaneously)
● feat(app-vite): Better TS typings overall
● refactor(app-vite): port CLI to ESM format (major effort! especially to support Vite 5 and SSR)
● feat(app-vite): support for quasar.config file in multiple formats (.js, .mjs, .ts, .cjs)
● feat(app-vite): Improve quasarConfOptions, generate types for it, improve docs (fix: #14069) (#15945)
● feat(app-vite): reload app if one of the imports from quasar.config file changes
● feat(app-vite): TS detection should keep account of quasar.config file format too (quasar.config.ts)
● feat(app-vite): support for SSR development with HTTPS
● feat(app-vite): env dotfiles support #15303
● feat(app-vite): New quasar.config file props: build > envFolder (string) and envFiles (string[])
● feat(app-vite): reopen browser (if configured so) when changing app url through quasar.config file
● feat&perf(app-vite): faster & more accurate algorithm for determining node package manager to use
● feat(app-vite): upgrade deps
● feat(app-vite): remove workaround for bug in Electron 6-8 in cli templates (#15845)
● feat(app-vite): remove bundleWebRuntime config for Capacitor v5+
● feat(app-vite): use workbox v7 by default
● feat(app-vite): quasar.config > pwa > injectPwaMetaTags can now also be a function: (({ pwaManifest, publicPath }) => string);
● feat(app-vite): quasar.config > build > htmlMinifyOptions
● feat(app-vite): lookup open port for vue devtools when being used; ability to run multiple cli instances with vue devtools
● perf(app-vite): SSR render-template in specific esm or cjs form, according to host project; interpolation by variable
● perf(app-vite): only verify quasar.conf server address for "dev" cmd
● feat(app-vite): pick new electron inspect port for each instance
● feat(app-vite): Electron - can now load multiple preload scripts
● refactor(app-vite): AE support - better and more efficient algorithms
● feat(app-vite): AE support for ESM format
● feat(app-vite): AE support for TS format (through a build step)
● feat(app-vite): AE API new methods -> hasTypescript() / hasLint() / getStorePackageName() / getNodePackagerName()
● feat(app-vite): AE -> Prompts API (and ability for prompts default exported fn to be async)
● refactor(app-vite): the "clean" cmd now works different, since the CLI can be run in multiple instances on the same project folder (multiple modes on dev or build)
● feat(app-vite): Support for Bun as package manager #16335
● feat(app-vite): for default /src-ssr template -> prod ssr -> on error, print err stack if built with debugging enabled

Env dotfiles support

Expanding a bit on the env dotfiles support. These files will be detected and used (the order matters):

.env                                # loaded in all cases
.env.local                          # loaded in all cases, ignored by git
.env.[dev|prod]                     # loaded for dev or prod only
.env.local.[dev|prod]               # loaded for dev or prod only, ignored by git
.env.[quasarMode]                   # loaded for specific Quasar CLI mode only
.env.local.[quasarMode]             # loaded for specific Quasar CLI mode only, ignored by git
.env.[dev|prod].[quasarMode]        # loaded for specific Quasar CLI mode and dev|prod only