Vite
v5.0.12

#vite

5.0.12 (2024-01-19)

● fix: await configResolved hooks of worker plugins (#15597) (#15605) (ef89f80), closes #15597 #15605

● fix: fs deny for case insensitive systems (#15653) (91641c4), closes #15653

Vite
v4.5.2

#vite

Please refer to CHANGELOG.md for details.

Vite
v3.2.8

#vite

Please refer to CHANGELOG.md for details.

Vite
v2.9.17

#vite

Please refer to CHANGELOG.md for details.

Vite
v5.1.0-beta.2

#vite

5.1.0-beta.2 (2024-01-19)

● fix: fs deny for case insensitive systems (#15653) (89be67d), closes #15653

● perf: don't recalculate path.dirname(mod.file) (#15623) (e459be4), closes #15623

● perf: optimize getSortedPluginsByHook (#15624) (f08a037), closes #15624

● goTo: port to v3 (#19046) (4eeae8c), closes #5732 #13538
● locale: add khmer translations (#18695) (e1d0e03)
● style: add cursor class utilities (#17033) (a25aac9)
● theme: add surface-light color (#19047) (d20875a), closes #18091
● VAutocomplete/VCombobox: add new clearOnSelect prop (657d929), closes #6842
● VCardItem: bring in-line with VListItem functionality (356bfd1)
● VDataTable/Virtual: add support for sorting raw objects (#19048) (0bba2f5), closes #11226
● VDatePicker: add new multiple prop options (07781b3), closes #18701
● VFileInput: add string support for showSize prop (706565f)
● VImg: add rounded and color support (32ac0a1)
● VList: add expand / collapse icon support (8414baf)
● VSelects: add new listProps prop (1f7b403), closes #6458
● VSwitch: add thumb, track-true, and track-false slots (#18092) (7031faa)

🔧 Bug Fixes

● VChipGroup: use VSlideGroup as baseline component (#17911) (bcffca9), closes #17321
● VDataTable: add new headerProps prop (#19025) (d121f54), closes #18993
● VDataTableVirtual: add missing colgroup slot (#19052) (0dca210)

Vuetify
v3.5.1

#vuetify

🔧 Bug Fixes

● VChipGroup: correctly filter props (54054d8)

Other Commmits

● chore(release): publish v3.5.1 (7afd453)

Vite
v5.1.0-beta.3

#vite

5.1.0-beta.3 (2024-01-22)

● perf: middleware to short-circuit on 304 (#15586) (35ae4f8), closes #15586

● perf: use thread for preprocessors (#13584) (acd795f), closes #13584

● fix: default sideEffect option is delivered to rollup (#15665) (f6cf3d1), closes #15665

● fix(ssr): mark builtin modules as side effect free (#15658) (526cf23), closes #15658

● fix(ssr): support externalized builtins for webworker (#15656) (639bbd6), closes #15656

● refactor: append tags logic in applyHtmlTransforms (#15647) (09b1517), closes #15647

● refactor(hmr): provide a separate logger interface (#15631) (110e2e1), closes #15631

Quasar
quasar-v2.14.3

#quasar

Fixes

● Vue 3.4 --> fix(ui): Hydration issues with Vue 3.4 (QField/QInput/..., QBtnDropdown, QExpansionItem, QFab) #16792
● Vue 3.4 --> fix(Dark): [Vue 3.4] Hydration issue with Dark Quasar plugin on SSR #16818
● fix(QAjaxBar): fix infinite fetch loop in watchEffect #16767 (#16780)
● fix(ui): expose updateScrollTarget method for QInfiniteScroll (#16182)
● fix(QTab): softError.message is undefined when opening tab with control-key #16791
● fix(QField/QInput/...): lazy validation breaks when clearable button is clicked #16723

Donations

Quasar Framework is an open-source MIT-licensed project made possible due to the generous contributions by sponsors and backers. If you are interested in supporting this project, please consider the following:

● Becoming a sponsor on Github
● One-off donation via PayPal

Vite
[email protected]

#vite

5.3.0 (2024-01-25)

● docs: fix commit id collision (#15105) (0654d1b), closes #15105

● docs: fix dead link (#15700) (aa7916a), closes #15700

● feat(legacy): build file name optimization (#15115) (39f435d), closes #15115

● feat(legacy): support any separator before hash in fileNames (#15170) (ecab41a), closes #15170

● feat(plugin-legacy): add modernTargets option (#15506) (cf56507), closes #15506

● fix(deps): update all non-major dependencies (#15233) (ad3adda), closes #15233

● fix(deps): update all non-major dependencies (#15304) (bb07f60), closes #15304

● fix(deps): update all non-major dependencies (#15375) (ab56227), closes #15375

● chore(deps): update all non-major dependencies (#15145) (7ff2c0a), closes #15145

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)