v7.18.8

Compare Source

v7.18.8 (2022-07-08)

Thanks @​dbacarel for your first PR!

👓 Spec Compliance

• babel-parser, babel-types
  • #​14730 Misc fixes to @babel/types AST definitions (@​JLHwung)

🐛 Bug Fix

• babel-plugin-transform-parameters
  • #​14736 Inject IIFE when variables shadow binding in rest param (@​nicolo-ribaudo)
• babel-plugin-transform-classes
  • #​14709 Fix compilation of nested super(...) calls (@​dbacarel)
• babel-plugin-transform-for-of, babel-plugin-transform-spread, babel-traverse, babel-types
  • #​14393 Support some TSTypes in the inferrer (@​JLHwung)
• babel-helper-module-transforms, babel-plugin-transform-modules-commonjs
  • #​14708 Unshadow cjs exports when transforming mutations (@​nicolo-ribaudo)

📝 Documentation

• #​14486 Fix test debugging instructions for contributors (@​conartist6)

🏠 Internal

• babel-types
  • #​14737 fix: deep clone shared AST field definitions (@​JLHwung)
• Other
  • #​14720 fix: support compiling monorepo on single-core CPU machines (@​JLHwung)
• babel-helper-fixtures, babel-parser
  • #​12619 Add json schema of fixture runner options (@​JLHwung)

🔬 Output optimization

• babel-plugin-transform-typescript
  • #​14723 [optimizeConstEnums] Inline const enum if only exported as type (@​nicolo-ribaudo)

Committers: 7

• Babel Bot (@​babel-bot)
• Conrad Buck (@​conartist6)
• Daniele Bacarella (@​dbacarel)
• Huáng Jùnliàng (@​JLHwung)
• Nicolò Ribaudo (@​nicolo-ribaudo)
• @​liuxingbaoyu
• coderaiser (@​coderaiser)

v7.18.8

Compare Source

👓 Spec Compliance

• babel-parser, babel-types
  • #​14730 Misc fixes to @babel/types AST definitions (@​JLHwung)

🐛 Bug Fix

• babel-plugin-transform-parameters
  • #​14736 Inject IIFE when variables shadow binding in rest param (@​nicolo-ribaudo)
• babel-plugin-transform-classes
  • #​14709 Fix compilation of nested super(...) calls (@​dbacarel)
• babel-plugin-transform-for-of, babel-plugin-transform-spread, babel-traverse, babel-types
  • #​14393 Support some TSTypes in the inferrer (@​JLHwung)
• babel-helper-module-transforms, babel-plugin-transform-modules-commonjs
  • #​14708 Unshadow cjs exports when transforming mutations (@​nicolo-ribaudo)

📝 Documentation

• #​14486 Fix test debugging instructions for contributors (@​conartist6)

🏠 Internal

• babel-types
  • #​14737 fix: deep clone shared AST field definitions (@​JLHwung)
• Other
  • #​14720 fix: support compiling monorepo on single-core CPU machines (@​JLHwung)
• babel-helper-fixtures, babel-parser
  • #​12619 Add json schema of fixture runner options (@​JLHwung)

🔬 Output optimization

• babel-plugin-transform-typescript
  • #​14723 [optimizeConstEnums] Inline const enum if only exported as type (@​nicolo-ribaudo)

v5.30.5

Compare Source

Bug Fixes

• eslint-plugin: [consistent-indexed-object-style] fix record mode fixer for generics with a default value (#​5280) (57f032c)

v5.30.5

Compare Source

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

v3.23.4

Compare Source

• Added a workaround of the Bun ~ 0.1.1 bug that define some globals with incorrect property descriptors and that causes a crash of core-js
• Added a fix of the FF103+ structuredClone bugs (1774866 (fixed in FF104) and 1777321 (still not fixed)) that now can clone errors, but .stack of the clone is an empty string
• Fixed { Map, WeakMap }.prototype.emplace logic, #​1102
• Fixed order of errors throwing on iterator helpers

v1.23.2

Compare Source

Highlights

This patch includes the following bug fixes:

https://github.com/microsoft/playwright/issues/15273 - [BUG] LaunchOptions config has no effect after update to v1.23.0https://github.com/microsoft/playwright/issues/153511 - [REGRESSION]: Component testing project does not compile anymorhttps://github.com/microsoft/playwright/issues/1543131 - [BUG] Regression: page.on('console') is ignored in 1.23

Browser Versions

• Chromium 104.0.5112.20
• Mozilla Firefox 100.0.2
• WebKit 15.4

This version was also tested against the following stable channels:

• Google Chrome 103
• Microsoft Edge 103

v3.49.0

Compare Source

• Improve performance of string escaping during SSR (#​5701)
• Add ComponentType and ComponentProps convenience types (#​6770)
• Add support for CSS @layer (#​7504)
• Export CompileOptions from svelte/compiler (#​7658)
• Fix DOM-less components not being properly destroyed (#​7488)
• Fix class: directive updates with <svelte:element> (#​7521, #​7571)
• Harden attribute escaping during SSR (#​7530)

v3.1.5

Compare Source

Added

• Support configuring a default font-weight for each font size utility (#​8763)
• Add support for alpha values in safe list (#​8774)

Fixed

• Improve types to support fallback values in the CSS-in-JS syntax used in plugin APIs (#​8762)
• Support including tailwindcss and autoprefixer in postcss.config.js in standalone CLI (#​8769)
• Fix using special-characters as prefixes (#​8772)
• Don’t prefix classes used within arbitrary variants (#​8773)
• Add more explicit types for the default theme (#​8780)

v0.8.5

Compare Source

v2.9.14

Compare Source

Please refer to CHANGELOG.md for details.

v0.18.0

Compare Source

   🚨 Breaking Changes

• TestSequencerConstructor typo  -  by @​AriPerkkio in https://github.com/vitest-dev/vitest/issues/1618
• reporter: Move ctx.log to ctx.logger.log, improve log flicking  -  by @​userquin and @​antfu in https://github.com/vitest-dev/vitest/issues/1166

   🐞 Bug Fixes

• Show error message when cache failed to parse  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/1614
• Move cache state to ctx.cache  -  by @​antfu (695a7)
• reporter: Clear previous state on rerun  -  by @​antfu (f7148)

    View changes on GitHub

v0.17.1

Compare Source

   🚀 Features

• Check related against forceRerunTriggers  -  by @​elliotwestlake and @​sheremet-va in https://github.com/vitest-dev/vitest/issues/1595
• Make sequencer public, add option to run tests in random order  -  by @​sheremet-va and @​antfu in https://github.com/vitest-dev/vitest/issues/1582

   🐞 Bug Fixes

• Use jsdom MessageEvent  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/1594
• Crash with odd cpu counts  -  by @​yamazaki-sensei in https://github.com/vitest-dev/vitest/issues/1597
• vite-node: Self circular reference  -  by @​antfu in https://github.com/vitest-dev/vitest/issues/1609

    View changes on GitHub

v4.1.1

Compare Source

Please refer to CHANGELOG.md for details.

v4.1.0

Compare Source

Vue Router 4.1

We are excited to announce the release of Vue Router 4.1 with a few new interesting features, better support for Node ESM and no breaking changes.

Omitting the component/components option in routes

It's now possible to completely omit the component option when defining routes with children. While nested routes are about defining layouts, they are also directly connected to a path and users often found themselves defining a pass through component that would just render a <RouterView> component to reuse the path structure. You can now simplify this to:

- import { RouterView } from 'vue-router'
- import { h } from 'vue'
-
 const routes = [
   {
     path: '/admin',
-     component: () => h(RouterView),
     children: [
       { path: 'users', component: AdminUserList },
       { path: 'users/:id', component: AdminUserDetails },
     ],
   },
 ]

In other words, you can now nest paths without having to define a component.

Passing History State in navigations

Passing History State through router.push() has been implemented and used by the router since its version 4.0 but hasn't been exposed as a public API until now. This enables passing a state property when calling router.push() or router.replace(). This is useful to pass global state to be associated with the history entry that cannot be shared by copying the URL. One common example of this are Modals:

// go to /users/24 but show a modal instead
router.push({ name: 'UserDetail', params: { id: 24 } state: { backgroundView: ... } })

To see a full example, check the modal e2e test, it has been updated to use the state property.

It's worth noting this shouldn't be used to pass fetched data or complex objects such as classes because of type and size limitations. Check the History State documentation for more information about the state property.

Given the nature of the <RouterView>'s route prop, there is also a new function loadRouteLocation() that can be used on a resolved route location to load a route with lazy loading:

import { loadRouteLocation } from 'vue-router'

const loadedRoute = await loadRouteLocation(router.resolve('/users/24'))

Typed Routes

In v4.1 we were initially planning to introduce types to automatically detect the params from a path property, creating autocomplete and type safety in router.push() and <RouterLink>'s to prop. It was implemented but also turned out to be extremely slow after ~50 routes due to the nature of the types relying on nesting and complex unions. Instead, we are introducing a build plugin to generate the types of the routes for you based your file structure. This is similar to Nuxt and Vite Plugin Pages but with full type support (similar to nuxt-typed-router) while allowing you to keep using the exact same API, just with Autocompletion and typing hints 😄. The plugin currently supports Vite, Webpack (with some caveats), and rollup and it's currently experimental to gather feedback from the community and build a flexible solution. We hope to release a stable version in the following months.

Check out the plugin GitHub repository for installation instructions and documentation.

Here are some other examples of how much this plugin can improves your developer experience:

CJS/MJS support for Node

We now expose a few extra entry points for Node but kept the old ones as well to prevent any disruption to the existing users. You can find more information about this in the corresponding pull request.

Please refer to CHANGELOG.md for details.

v0.38.4

Compare Source

• feat: add vueCompilerOptions.strictTemplates (#​1418)
• fix: don't auto close ``` (#​1428)
• fix: change unknown slot type from unknown to any (#​1541)
• fix: SFC templates outline incorrect (#​1531)
• fix: slot shorthand highlighting incorrect if have not = (#​1423)
• fix: vue file import path auto-complete not working on windows (#​1304)
• fix: avoid duplicate result in html (#​1552) (#​1530)
• fix: code action document edit version incorrect (#​1490)

Breaking changes

• experimentalSuppressUnknownJsxPropertyErrors, experimentalSuppressInvalidJsxElementTypeErrors is replaced by strictTemplates.

  {
  	"vueCompilerOptions": {
  -		"experimentalSuppressUnknownJsxPropertyErrors": false,
  -		"experimentalSuppressInvalidJsxElementTypeErrors": false,
  +		"strictTemplates": true
  	},
  }

Our Sponsors

v0.38.3

Compare Source

• feat: support html, css intellisense for petite-vue (#​1471)
• fix: avoid unknown jsx property error for vue 2.7 (#​1533)
• fix: fixed GlobalComponents interface not working edge case (#​1489)
• fix: stricter slots type extracting (#​1522)
• fix: nuxt app preview not working