search

kineticio / runnable

Build internal workflows with ease
https://getrunnable.com/
51 stars 4 forks source link

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

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@chakra-ui/icons ^2.0.18 -> ^2.0.19 age adoption passing confidence
@chakra-ui/react (source) ^2.5.5 -> ^2.6.0 age adoption passing confidence
@chakra-ui/styled-system ^2.8.0 -> ^2.9.0 age adoption passing confidence
@chakra-ui/system ^2.5.5 -> ^2.5.6 age adoption passing confidence
@emotion/cache (source) ^11.10.7 -> ^11.10.8 age adoption passing confidence
@emotion/react (source) ^11.10.6 -> ^11.10.8 age adoption passing confidence
@emotion/styled (source) ^11.10.6 -> ^11.10.8 age adoption passing confidence
@types/jest (source) 29.5.0 -> 29.5.1 age adoption passing confidence
@types/node (source) ^18.15.11 -> ^18.16.2 age adoption passing confidence
@types/react (source) ^18.0.35 -> ^18.2.0 age adoption passing confidence
@types/react-dom (source) ^18.0.11 -> ^18.2.1 age adoption passing confidence
@typescript-eslint/eslint-plugin ^5.58.0 -> ^5.59.1 age adoption passing confidence
@typescript-eslint/parser ^5.58.0 -> ^5.59.1 age adoption passing confidence
esbuild 0.17.16 -> 0.17.18 age adoption passing confidence
eslint (source) ^8.38.0 -> ^8.39.0 age adoption passing confidence
eslint (source) 8.38.0 -> 8.39.0 age adoption passing confidence
framer-motion ^10.11.6 -> ^10.12.4 age adoption passing confidence
js-cookie ^3.0.1 -> ^3.0.5 age adoption passing confidence
lint-staged ^13.2.1 -> ^13.2.2 age adoption passing confidence
pnpm (source) 8.2.0 -> 8.3.1 age adoption passing confidence
prettier (source) ^2.8.7 -> ^2.8.8 age adoption passing confidence
rollup (source) ^3.20.2 -> ^3.21.0 age adoption passing confidence
stylis ^4.1.3 -> ^4.1.4 age adoption passing confidence
turbo (source) ^1.9.1 -> ^1.9.3 age adoption passing confidence
vitepress (source) ^1.0.0-alpha.65 -> ^1.0.0-alpha.74 age adoption passing confidence

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

Release Notes

chakra-ui/chakra-ui (@​chakra-ui/icons) ### [`v2.0.19`](https://togithub.com/chakra-ui/chakra-ui/blob/HEAD/packages/components/icons/CHANGELOG.md#​2019) [Compare Source](https://togithub.com/chakra-ui/chakra-ui/compare/@chakra-ui/icons@2.0.18...@chakra-ui/icons@2.0.19) ##### Patch Changes - [`e7bd872d0`](https://togithub.com/chakra-ui/chakra-ui/commit/e7bd872d007b1ab2c08e71493450557727791c5b) Thanks [@​segunadebayo](https://togithub.com/segunadebayo)! - Fix issue where `SpinnerIcon` id causes accessibility violation - Updated dependencies \[]: - [@​chakra-ui/icon](https://togithub.com/chakra-ui/icon)[@​3](https://togithub.com/3).0.16
chakra-ui/chakra-ui (@​chakra-ui/react) ### [`v2.6.0`](https://togithub.com/chakra-ui/chakra-ui/blob/HEAD/packages/components/react/CHANGELOG.md#​260) [Compare Source](https://togithub.com/chakra-ui/chakra-ui/compare/@chakra-ui/react@2.5.5...@chakra-ui/react@2.6.0) ##### Minor Changes - [#​7502](https://togithub.com/chakra-ui/chakra-ui/pull/7502) [`49a29a238`](https://togithub.com/chakra-ui/chakra-ui/commit/49a29a238439242e0959d74ebf48c84411581288) Thanks [@​estheragbaje](https://togithub.com/estheragbaje)! - Introduce new `Stepper` component to model sequencial steps in a process. ```jsx live=false {steps.map((step, index) => ( } incomplete={} active={} /> {step.title} {step.description} ))} ``` ##### Patch Changes - Updated dependencies \[[`68482afaa`](https://togithub.com/chakra-ui/chakra-ui/commit/68482afaa6c0dd753a1071fbe3c4207896e7e311), [`7b67fd58c`](https://togithub.com/chakra-ui/chakra-ui/commit/7b67fd58c74765831d1fda016aafae15a49617a5), [`379f347a8`](https://togithub.com/chakra-ui/chakra-ui/commit/379f347a891f131c39a436b5738221105300ad76), [`c2f0d1bb2`](https://togithub.com/chakra-ui/chakra-ui/commit/c2f0d1bb2a07fe6af5e53a1f216d80c9a7d6df72), [`24f952da2`](https://togithub.com/chakra-ui/chakra-ui/commit/24f952da27ef43febbe20714a08eb94ce87133eb), [`6077dffc6`](https://togithub.com/chakra-ui/chakra-ui/commit/6077dffc6303391fba3e12d7a193584fe88bbb14), [`5ff30252f`](https://togithub.com/chakra-ui/chakra-ui/commit/5ff30252f565f2e171375011a349fde53e6e4ec9), [`27dcf2f56`](https://togithub.com/chakra-ui/chakra-ui/commit/27dcf2f5647c3323d1e6bee35db6cf1514c1b29d), [`7c62a361a`](https://togithub.com/chakra-ui/chakra-ui/commit/7c62a361ad7cc52141e7604d34fe57347e25effa), [`49a29a238`](https://togithub.com/chakra-ui/chakra-ui/commit/49a29a238439242e0959d74ebf48c84411581288), [`417293f8c`](https://togithub.com/chakra-ui/chakra-ui/commit/417293f8cf65cf953851ce6b99f50d1f611075a2), [`82ec66459`](https://togithub.com/chakra-ui/chakra-ui/commit/82ec66459283ef24a422955952efa1f8d267af2c), [`49a29a238`](https://togithub.com/chakra-ui/chakra-ui/commit/49a29a238439242e0959d74ebf48c84411581288), [`49a29a238`](https://togithub.com/chakra-ui/chakra-ui/commit/49a29a238439242e0959d74ebf48c84411581288), [`169d71679`](https://togithub.com/chakra-ui/chakra-ui/commit/169d71679ed22d2245240b4018a906d220d502f8), [`d6b6941c8`](https://togithub.com/chakra-ui/chakra-ui/commit/d6b6941c8e64f451313539d15f23fb0fb05ff129)]: - [@​chakra-ui/checkbox](https://togithub.com/chakra-ui/checkbox)[@​2](https://togithub.com/2).2.15 - [@​chakra-ui/menu](https://togithub.com/chakra-ui/menu)[@​2](https://togithub.com/2).1.13 - [@​chakra-ui/theme](https://togithub.com/chakra-ui/theme)[@​3](https://togithub.com/3).1.0 - [@​chakra-ui/styled-system](https://togithub.com/chakra-ui/styled-system)[@​2](https://togithub.com/2).9.0 - [@​chakra-ui/layout](https://togithub.com/chakra-ui/layout)[@​2](https://togithub.com/2).1.19 - [@​chakra-ui/toast](https://togithub.com/chakra-ui/toast)[@​6](https://togithub.com/6).1.2 - [@​chakra-ui/avatar](https://togithub.com/chakra-ui/avatar)[@​2](https://togithub.com/2).2.9 - [@​chakra-ui/image](https://togithub.com/chakra-ui/image)[@​2](https://togithub.com/2).0.16 - [@​chakra-ui/stepper](https://togithub.com/chakra-ui/stepper)[@​2](https://togithub.com/2).1.0 - [@​chakra-ui/hooks](https://togithub.com/chakra-ui/hooks)[@​2](https://togithub.com/2).2.0 - [@​chakra-ui/editable](https://togithub.com/chakra-ui/editable)[@​3](https://togithub.com/3).0.0 - [@​chakra-ui/switch](https://togithub.com/chakra-ui/switch)[@​2](https://togithub.com/2).0.27 - [@​chakra-ui/card](https://togithub.com/chakra-ui/card)[@​2](https://togithub.com/2).1.6 - [@​chakra-ui/button](https://togithub.com/chakra-ui/button)[@​2](https://togithub.com/2).0.18 - [@​chakra-ui/media-query](https://togithub.com/chakra-ui/media-query)[@​3](https://togithub.com/3).2.12 - [@​chakra-ui/skeleton](https://togithub.com/chakra-ui/skeleton)[@​2](https://togithub.com/2).0.24 - [@​chakra-ui/slider](https://togithub.com/chakra-ui/slider)[@​2](https://togithub.com/2).0.23 - [@​chakra-ui/system](https://togithub.com/chakra-ui/system)[@​2](https://togithub.com/2).5.6 - [@​chakra-ui/theme-utils](https://togithub.com/chakra-ui/theme-utils)[@​2](https://togithub.com/2).0.16 - [@​chakra-ui/accordion](https://togithub.com/chakra-ui/accordion)[@​2](https://togithub.com/2).1.11 - [@​chakra-ui/alert](https://togithub.com/chakra-ui/alert)[@​2](https://togithub.com/2).1.0 - [@​chakra-ui/input](https://togithub.com/chakra-ui/input)[@​2](https://togithub.com/2).0.22 - [@​chakra-ui/number-input](https://togithub.com/chakra-ui/number-input)[@​2](https://togithub.com/2).0.19 - [@​chakra-ui/popover](https://togithub.com/chakra-ui/popover)[@​2](https://togithub.com/2).1.10 - [@​chakra-ui/radio](https://togithub.com/chakra-ui/radio)[@​2](https://togithub.com/2).0.22 - [@​chakra-ui/select](https://togithub.com/chakra-ui/select)[@​2](https://togithub.com/2).0.19 - [@​chakra-ui/tag](https://togithub.com/chakra-ui/tag)[@​3](https://togithub.com/3).0.0 - [@​chakra-ui/textarea](https://togithub.com/chakra-ui/textarea)[@​2](https://togithub.com/2).0.19 - [@​chakra-ui/tooltip](https://togithub.com/chakra-ui/tooltip)[@​2](https://togithub.com/2).2.7 - [@​chakra-ui/modal](https://togithub.com/chakra-ui/modal)[@​2](https://togithub.com/2).2.11 - [@​chakra-ui/popper](https://togithub.com/chakra-ui/popper)[@​3](https://togithub.com/3).0.13 - [@​chakra-ui/transition](https://togithub.com/chakra-ui/transition)[@​2](https://togithub.com/2).0.16 - [@​chakra-ui/breadcrumb](https://togithub.com/chakra-ui/breadcrumb)[@​2](https://togithub.com/2).1.5 - [@​chakra-ui/control-box](https://togithub.com/chakra-ui/control-box)[@​2](https://togithub.com/2).0.13 - [@​chakra-ui/table](https://togithub.com/chakra-ui/table)[@​2](https://togithub.com/2).0.17 - [@​chakra-ui/close-button](https://togithub.com/chakra-ui/close-button)[@​2](https://togithub.com/2).0.17 - [@​chakra-ui/form-control](https://togithub.com/chakra-ui/form-control)[@​2](https://togithub.com/2).0.18 - [@​chakra-ui/icon](https://togithub.com/chakra-ui/icon)[@​3](https://togithub.com/3).0.16 - [@​chakra-ui/pin-input](https://togithub.com/chakra-ui/pin-input)[@​2](https://togithub.com/2).0.20 - [@​chakra-ui/progress](https://togithub.com/chakra-ui/progress)[@​2](https://togithub.com/2).1.6 - [@​chakra-ui/provider](https://togithub.com/chakra-ui/provider)[@​2](https://togithub.com/2).2.3 - [@​chakra-ui/spinner](https://togithub.com/chakra-ui/spinner)[@​2](https://togithub.com/2).0.13 - [@​chakra-ui/stat](https://togithub.com/chakra-ui/stat)[@​2](https://togithub.com/2).0.18 - [@​chakra-ui/tabs](https://togithub.com/chakra-ui/tabs)[@​2](https://togithub.com/2).1.9 - [@​chakra-ui/visually-hidden](https://togithub.com/chakra-ui/visually-hidden)[@​2](https://togithub.com/2).0.15
chakra-ui/chakra-ui (@​chakra-ui/styled-system) ### [`v2.9.0`](https://togithub.com/chakra-ui/chakra-ui/releases/tag/%40chakra-ui/styled-system%402.9.0) [Compare Source](https://togithub.com/chakra-ui/chakra-ui/compare/@chakra-ui/styled-system@2.8.0...@chakra-ui/styled-system@2.9.0) ##### Minor Changes - [`379f347a8`](https://togithub.com/chakra-ui/chakra-ui/commit/379f347a891f131c39a436b5738221105300ad76) Thanks [@​segunadebayo](https://togithub.com/segunadebayo)! - Add support for `aspectRatio` style prop to enable the usage of the native aspect ratio property - [#​7494](https://togithub.com/chakra-ui/chakra-ui/pull/7494) [`27dcf2f56`](https://togithub.com/chakra-ui/chakra-ui/commit/27dcf2f5647c3323d1e6bee35db6cf1514c1b29d) Thanks [@​kuroppe1819](https://togithub.com/kuroppe1819)! - Add support for nested semantic tokens in theme. It is now possible to declare semantic tokens by nesting objects. BEFORE: ```js const theme = { semanticTokens: { colors: { "background.pressed.base": { default: "blue.800", _dark: "blue.300" }, "background.pressed.subtle": { default: "blue.300", _dark: "blue.700" }, }, }, } ``` AFTER: ```js const theme = { semanticTokens: { colors: { background: { pressed: { base: { default: "blue.800", _dark: "blue.300" }, subtle: { default: "blue.300", _dark: "blue.700" }, }, }, }, }, } ``` This allows for cleaner grouping and organization of tokens. - [#​7502](https://togithub.com/chakra-ui/chakra-ui/pull/7502) [`49a29a238`](https://togithub.com/chakra-ui/chakra-ui/commit/49a29a238439242e0959d74ebf48c84411581288) Thanks [@​estheragbaje](https://togithub.com/estheragbaje)! - Add `_horizontal` and `_vertical` pseudo props to style orientation data attributes
emotion-js/emotion ### [`v11.10.8`](https://togithub.com/emotion-js/emotion/releases/tag/%40emotion/styled%4011.10.8) [Compare Source](https://togithub.com/emotion-js/emotion/compare/@emotion/cache@11.10.7...@emotion/cache@11.10.8) ##### Patch Changes - [#​3025](https://togithub.com/emotion-js/emotion/pull/3025) [`6bd13425`](https://togithub.com/emotion-js/emotion/commit/6bd13425a2b413150c81e63fad1105d7968b5e6f) Thanks [@​Andarist](https://togithub.com/Andarist)! - Fixed a parsing issue with `&` within nested functions in declaration values by updating the underlying parser ([stylis](https://togithub.com/thysultan/stylis)). - Updated dependencies \[[`6bd13425`](https://togithub.com/emotion-js/emotion/commit/6bd13425a2b413150c81e63fad1105d7968b5e6f)]: - [@​emotion/babel-plugin](https://togithub.com/emotion/babel-plugin)[@​11](https://togithub.com/11).10.8
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin) ### [`v5.59.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#​5591-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5590v5591-2023-04-24) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.0...v5.59.1) ##### Bug Fixes - **eslint-plugin:** \[prefer-regexp-exec] skip malformed regexes ([#​6935](https://togithub.com/typescript-eslint/typescript-eslint/issues/6935)) ([05ed60e](https://togithub.com/typescript-eslint/typescript-eslint/commit/05ed60e25f1de9d1bb83d56c81a349130960bec8)) - **eslint-plugin:** \[unified-signatures] no parameters function ([#​6940](https://togithub.com/typescript-eslint/typescript-eslint/issues/6940)) ([2970861](https://togithub.com/typescript-eslint/typescript-eslint/commit/297086154acc568a0ae8eb41c8977b7a7ba4e0ed)) ### [`v5.59.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/eslint-plugin/CHANGELOG.md#​5590-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5580v5590-2023-04-17) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.58.0...v5.59.0) ##### Bug Fixes - **eslint-plugin:** \[no-unnecessary-condition] allow nullish coalescing for naked type parameter ([#​6910](https://togithub.com/typescript-eslint/typescript-eslint/issues/6910)) ([3e5f858](https://togithub.com/typescript-eslint/typescript-eslint/commit/3e5f8583f1e4fe045c2fe2143d6f280b7381f96b)) ##### Features - **eslint-plugin:** \[ban-types] add NonNullable suggestion and allow custom suggestions ([#​6876](https://togithub.com/typescript-eslint/typescript-eslint/issues/6876)) ([ff65235](https://togithub.com/typescript-eslint/typescript-eslint/commit/ff65235246bb6214fb64f0e0317373ca99f8bcbe))
typescript-eslint/typescript-eslint (@​typescript-eslint/parser) ### [`v5.59.1`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#​5591-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5590v5591-2023-04-24) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.59.0...v5.59.1) **Note:** Version bump only for package [@​typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) ### [`v5.59.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#​5590-httpsgithubcomtypescript-eslinttypescript-eslintcomparev5580v5590-2023-04-17) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.58.0...v5.59.0) **Note:** Version bump only for package [@​typescript-eslint/parser](https://togithub.com/typescript-eslint/parser)
evanw/esbuild ### [`v0.17.18`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​01718) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.17...v0.17.18) - Fix non-default JSON import error with `export {} from` ([#​3070](https://togithub.com/evanw/esbuild/issues/3070)) This release fixes a bug where esbuild incorrectly identified statements of the form `export { default as x } from "y" assert { type: "json" }` as a non-default import. The bug did not affect code of the form `import { default as x } from ...` (only code that used the `export` keyword). - Fix a crash with an invalid subpath import ([#​3067](https://togithub.com/evanw/esbuild/issues/3067)) Previously esbuild could crash when attempting to generate a friendly error message for an invalid [subpath import](https://nodejs.org/api/packages.html#subpath-imports) (i.e. an import starting with `#`). This happened because esbuild originally only supported the `exports` field and the code for that error message was not updated when esbuild later added support for the `imports` field. This crash has been fixed. ### [`v0.17.17`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​01717) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.16...v0.17.17) - Fix CSS nesting transform for top-level `&` ([#​3052](https://togithub.com/evanw/esbuild/issues/3052)) Previously esbuild could crash with a stack overflow when lowering CSS nesting rules with a top-level `&`, such as in the code below. This happened because esbuild's CSS nesting transform didn't handle top-level `&`, causing esbuild to inline the top-level selector into itself. This release handles top-level `&` by replacing it with [the `:scope` pseudo-class](https://drafts.csswg.org/selectors-4/#the-scope-pseudo): ```css /* Original code */ &, a { .b { color: red; } } /* New output (with --target=chrome90) */ :is(:scope, a) .b { color: red; } ``` - Support `exports` in `package.json` for `extends` in `tsconfig.json` ([#​3058](https://togithub.com/evanw/esbuild/issues/3058)) TypeScript 5.0 added the ability to use `extends` in `tsconfig.json` to reference a path in a package whose `package.json` file contains an `exports` map that points to the correct location. This doesn't automatically work in esbuild because `tsconfig.json` affects esbuild's path resolution, so esbuild's normal path resolution logic doesn't apply. This release adds support for doing this by adding some additional code that attempts to resolve the `extends` path using the `exports` field. The behavior should be similar enough to esbuild's main path resolution logic to work as expected. Note that esbuild always treats this `extends` import as a `require()` import since that's what TypeScript appears to do. Specifically the `require` condition will be active and the `import` condition will be inactive. - Fix watch mode with `NODE_PATH` ([#​3062](https://togithub.com/evanw/esbuild/issues/3062)) Node has a rarely-used feature where you can extend the set of directories that node searches for packages using the `NODE_PATH` environment variable. While esbuild supports this too, previously a bug prevented esbuild's watch mode from picking up changes to imported files that were contained directly in a `NODE_PATH` directory. You're supposed to use `NODE_PATH` for packages, but some people abuse this feature by putting files in that directory instead (e.g. `node_modules/some-file.js` instead of `node_modules/some-pkg/some-file.js`). The watch mode bug happens when you do this because esbuild first tries to read `some-file.js` as a directory and then as a file. Watch mode was incorrectly waiting for `some-file.js` to become a valid directory. This release fixes this edge case bug by changing watch mode to watch `some-file.js` as a file when this happens. ### [`v0.17.16`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​01716) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.15...v0.17.16) - Fix CSS nesting transform for triple-nested rules that start with a combinator ([#​3046](https://togithub.com/evanw/esbuild/issues/3046)) This release fixes a bug with esbuild where triple-nested CSS rules that start with a combinator were not transformed correctly for older browsers. Here's an example of such a case before and after this bug fix: ```css /* Original input */ .a { color: red; > .b { color: green; > .c { color: blue; } } } /* Old output (with --target=chrome90) */ .a { color: red; } .a > .b { color: green; } .a .b > .c { color: blue; } /* New output (with --target=chrome90) */ .a { color: red; } .a > .b { color: green; } .a > .b > .c { color: blue; } ``` - Support `--inject` with a file loaded using the `copy` loader ([#​3041](https://togithub.com/evanw/esbuild/issues/3041)) This release now allows you to use `--inject` with a file that is loaded using the `copy` loader. The `copy` loader copies the imported file to the output directory verbatim and rewrites the path in the `import` statement to point to the copied output file. When used with `--inject`, this means the injected file will be copied to the output directory as-is and a bare `import` statement for that file will be inserted in any non-copy output files that esbuild generates. Note that since esbuild doesn't parse the contents of copied files, esbuild will not expose any of the export names as usable imports when you do this (in the way that esbuild's `--inject` feature is typically used). However, any side-effects that the injected file has will still occur. ### [`v0.17.15`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​01715) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.14...v0.17.15) - Allow keywords as type parameter names in mapped types ([#​3033](https://togithub.com/evanw/esbuild/issues/3033)) TypeScript allows type keywords to be used as parameter names in mapped types. Previously esbuild incorrectly treated this as an error. Code that does this is now supported: ```ts type Foo = 'a' | 'b' | 'c' type A = { [keyof in Foo]: number } type B = { [infer in Foo]: number } type C = { [readonly in Foo]: number } ``` - Add annotations for re-exported modules in node ([#​2486](https://togithub.com/evanw/esbuild/issues/2486), [#​3029](https://togithub.com/evanw/esbuild/issues/3029)) Node lets you import named imports from a CommonJS module using ESM import syntax. However, the allowed names aren't derived from the properties of the CommonJS module. Instead they are derived from an arbitrary syntax-only analysis of the CommonJS module's JavaScript AST. To accommodate node doing this, esbuild's ESM-to-CommonJS conversion adds a special non-executable "annotation" for node that describes the exports that node should expose in this scenario. It takes the form `0 && (module.exports = { ... })` and comes at the end of the file (`0 && expr` means `expr` is never evaluated). Previously esbuild didn't do this for modules re-exported using the `export * from` syntax. Annotations for these re-exports will now be added starting with this release: ```js // Original input export { foo } from './foo' export * from './bar' // Old output (with --format=cjs --platform=node) ... 0 && (module.exports = { foo }); // New output (with --format=cjs --platform=node) ... 0 && (module.exports = { foo, ...require("./bar") }); ``` Note that you need to specify both `--format=cjs` and `--platform=node` to get these node-specific annotations. - Avoid printing an unnecessary space in between a number and a `.` ([#​3026](https://togithub.com/evanw/esbuild/pull/3026)) JavaScript typically requires a space in between a number token and a `.` token to avoid the `.` being interpreted as a decimal point instead of a member expression. However, this space is not required if the number token itself contains a decimal point, an exponent, or uses a base other than 10. This release of esbuild now avoids printing the unnecessary space in these cases: ```js // Original input foo(1000 .x, 0 .x, 0.1 .x, 0.0001 .x, 0xFFFF_0000_FFFF_0000 .x) // Old output (with --minify) foo(1e3 .x,0 .x,.1 .x,1e-4 .x,0xffff0000ffff0000 .x); // New output (with --minify) foo(1e3.x,0 .x,.1.x,1e-4.x,0xffff0000ffff0000.x); ``` - Fix server-sent events with live reload when writing to the file system root ([#​3027](https://togithub.com/evanw/esbuild/issues/3027)) This release fixes a bug where esbuild previously failed to emit server-sent events for live reload when `outdir` was the file system root, such as `/`. This happened because `/` is the only path on Unix that cannot have a trailing slash trimmed from it, which was fixed by improved path handling. ### [`v0.17.14`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​01714) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.13...v0.17.14) - Allow the TypeScript 5.0 `const` modifier in object type declarations ([#​3021](https://togithub.com/evanw/esbuild/issues/3021)) The new TypeScript 5.0 `const` modifier was added to esbuild in version 0.17.5, and works with classes, functions, and arrow expressions. However, support for it wasn't added to object type declarations (e.g. interfaces) due to an oversight. This release adds support for these cases, so the following TypeScript 5.0 code can now be built with esbuild: ```ts interface Foo { (): T } type Bar = { new (): T } ``` - Implement preliminary lowering for CSS nesting ([#​1945](https://togithub.com/evanw/esbuild/issues/1945)) Chrome has [implemented the new CSS nesting specification](https://developer.chrome.com/articles/css-nesting/) in version 112, which is currently in beta but will become stable very soon. So CSS nesting is now a part of the web platform! This release of esbuild can now transform nested CSS syntax into non-nested CSS syntax for older browsers. The transformation relies on the `:is()` pseudo-class in many cases, so the transformation is only guaranteed to work when targeting browsers that support `:is()` (e.g. Chrome 88+). You'll need to set esbuild's [`target`](https://esbuild.github.io/api/#target) to the browsers you intend to support to tell esbuild to do this transformation. You will get a warning if you use CSS nesting syntax with a `target` which includes older browsers that don't support `:is()`. The lowering transformation looks like this: ```css /* Original input */ a.btn { color: #​333; &:hover { color: #​444 } &:active { color: #​555 } } /* New output (with --target=chrome88) */ a.btn { color: #​333; } a.btn:hover { color: #​444; } a.btn:active { color: #​555; } ``` More complex cases may generate the `:is()` pseudo-class: ```css /* Original input */ div, p { .warning, .error { padding: 20px; } } /* New output (with --target=chrome88) */ :is(div, p) :is(.warning, .error) { padding: 20px; } ``` In addition, esbuild now has a special warning message for nested style rules that start with an identifier. This isn't allowed in CSS because the syntax would be ambiguous with the existing declaration syntax. The new warning message looks like this: ▲ [WARNING] A nested style rule cannot start with "p" because it looks like the start of a declaration [css-syntax-error] :1:7: 1 │ main { p { margin: auto } } │ ^ ╵ :is(p) To start a nested style rule with an identifier, you need to wrap the identifier in ":is(...)" to prevent the rule from being parsed as a declaration. Keep in mind that the transformation in this release is a preliminary implementation. CSS has many features that interact in complex ways, and there may be some edge cases that don't work correctly yet. - Minification now removes unnecessary `&` CSS nesting selectors This release introduces the following CSS minification optimizations: ```css /* Original input */ a { font-weight: bold; & { color: blue; } & :hover { text-decoration: underline; } } /* Old output (with --minify) */ a{font-weight:700;&{color:#​00f}& :hover{text-decoration:underline}} /* New output (with --minify) */ a{font-weight:700;:hover{text-decoration:underline}color:#​00f} ``` - Minification now removes duplicates from CSS selector lists This release introduces the following CSS minification optimization: ```css /* Original input */ div, div { color: red } /* Old output (with --minify) */ div,div{color:red} /* New output (with --minify) */ div{color:red} ``` ### [`v0.17.13`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​01713) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.12...v0.17.13) - Work around an issue with `NODE_PATH` and Go's WebAssembly internals ([#​3001](https://togithub.com/evanw/esbuild/issues/3001)) Go's WebAssembly implementation returns `EINVAL` instead of `ENOTDIR` when using the `readdir` syscall on a file. This messes up esbuild's implementation of node's module resolution algorithm since encountering `ENOTDIR` causes esbuild to continue its search (since it's a normal condition) while other encountering other errors causes esbuild to fail with an I/O error (since it's an unexpected condition). You can encounter this issue in practice if you use node's legacy `NODE_PATH` feature to tell esbuild to resolve node modules in a custom directory that was not installed by npm. This release works around this problem by converting `EINVAL` into `ENOTDIR` for the `readdir` syscall. - Fix a minification bug with CSS `@layer` rules that have parsing errors ([#​3016](https://togithub.com/evanw/esbuild/issues/3016)) CSS at-rules [require either a `{}` block or a semicolon at the end](https://www.w3.org/TR/css-syntax-3/#consume-at-rule). Omitting both of these causes esbuild to treat the rule as an unknown at-rule. Previous releases of esbuild had a bug that incorrectly removed unknown at-rules without any children during minification if the at-rule token matched an at-rule that esbuild can handle. Specifically [cssnano](https://cssnano.co/) can generate `@layer` rules with parsing errors, and empty `@layer` rules cannot be removed because they have side effects (`@layer` didn't exist when esbuild's CSS support was added, so esbuild wasn't written to handle this). This release changes esbuild to no longer discard `@layer` rules with parsing errors when minifying (the rule `@layer c` has a parsing error): ```css /* Original input */ @​layer a { @​layer b { @​layer c } } /* Old output (with --minify) */ @​layer a.b; /* New output (with --minify) */ @​layer a.b.c; ``` - Unterminated strings in CSS are no longer an error The CSS specification provides [rules for handling parsing errors](https://www.w3.org/TR/CSS22/syndata.html#parsing-errors). One of those rules is that user agents must close strings upon reaching the end of a line (i.e., before an unescaped line feed, carriage return or form feed character), but then drop the construct (declaration or rule) in which the string was found. For example: ```css p { color: green; font-family: 'Courier New Times color: red; color: green; } ``` ...would be treated the same as: ```css p { color: green; color: green; } ``` ...because the second declaration (from `font-family` to the semicolon after `color: red`) is invalid and is dropped. Previously using this CSS with esbuild failed to build due to a syntax error, even though the code can be interpreted by a browser. With this release, the code now produces a warning instead of an error, and esbuild prints the invalid CSS such that it stays invalid in the output: ```css /* esbuild's new non-minified output: */ p { color: green; font-family: 'Courier New Times color: red; color: green; } ``` ```css /* esbuild's new minified output: */ p{font-family:'Courier New Times color: red;color:green} ``` ### [`v0.17.12`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​01712) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.11...v0.17.12) - Fix a crash when parsing inline TypeScript decorators ([#​2991](https://togithub.com/evanw/esbuild/issues/2991)) Previously esbuild's TypeScript parser crashed when parsing TypeScript decorators if the definition of the decorator was inlined into the decorator itself: ```ts @​(function sealed(constructor: Function) { Object.seal(constructor); Object.seal(constructor.prototype); }) class Foo {} ``` This crash was not noticed earlier because this edge case did not have test coverage. The crash is fixed in this release. ### [`v0.17.11`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​01711) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.10...v0.17.11) - Fix the `alias` feature to always prefer the longest match ([#​2963](https://togithub.com/evanw/esbuild/issues/2963)) It's possible to configure conflicting aliases such as `--alias:a=b` and `--alias:a/c=d`, which is ambiguous for the import path `a/c/x` (since it could map to either `b/c/x` or `d/x`). Previously esbuild would pick the first matching `alias`, which would non-deterministically pick between one of the possible matches. This release fixes esbuild to always deterministically pick the longest possible match. - Minify calls to some global primitive constructors ([#​2962](https://togithub.com/evanw/esbuild/issues/2962)) With this release, esbuild's minifier now replaces calls to `Boolean`/`Number`/`String`/`BigInt` with equivalent shorter code when relevant: ```js // Original code console.log( Boolean(a ? (b | c) !== 0 : (c & d) !== 0), Number(e ? '1' : '2'), String(e ? '1' : '2'), BigInt(e ? 1n : 2n), ) // Old output (with --minify) console.log(Boolean(a?(b|c)!==0:(c&d)!==0),Number(e?"1":"2"),String(e?"1":"2"),BigInt(e?1n:2n)); // New output (with --minify) console.log(!!(a?b|c:c&d),+(e?"1":"2"),e?"1":"2",e?1n:2n); ``` - Adjust some feature compatibility tables for node ([#​2940](https://togithub.com/evanw/esbuild/issues/2940)) This release makes the following adjustments to esbuild's internal feature compatibility tables for node, which tell esbuild which versions of node are known to support all aspects of that feature: - `class-private-brand-checks`: node v16.9+ => node v16.4+ (a decrease) - `hashbang`: node v12.0+ => node v12.5+ (an increase) - `optional-chain`: node v16.9+ => node v16.1+ (a decrease) - `template-literal`: node v4+ => node v10+ (an increase) Each of these adjustments was identified by comparing against data from the `node-compat-table` package and was manually verified using old node executables downloaded from https://nodejs.org/download/release/. ### [`v0.17.10`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​01710) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.9...v0.17.10) - Update esbuild's handling of CSS nesting to match the latest specification changes ([#​1945](https://togithub.com/evanw/esbuild/issues/1945)) The syntax for the upcoming CSS nesting feature has [recently changed](https://webkit.org/blog/13813/try-css-nesting-today-in-safari-technology-preview/). The `@nest` prefix that was previously required in some cases is now gone, and nested rules no longer have to start with `&` (as long as they don't start with an identifier or function token). This release updates esbuild's pass-through handling of CSS nesting syntax to match the latest specification changes. So you can now use esbuild to bundle CSS containing nested rules and try them out in a browser that supports CSS nesting (which includes nightly builds of both Chrome and Safari). However, I'm not implementing lowering of nested CSS to non-nested CSS for older browsers yet. While the syntax has been decided, the semantics are still in flux. In particular, there is still some debate about changing the fundamental way that CSS nesting works. For example, you might think that the following CSS is equivalent to a `.outer .inner button { ... }` rule: ```css .inner button { .outer & { color: red; } } ``` But instead it's actually equivalent to a `.outer :is(.inner button) { ... }` rule which unintuitively also matches the following DOM structure: ```html
``` The `:is()` behavior is preferred by browser implementers because it's more memory-efficient, but the straightforward translation into a `.outer .inner button { ... }` rule is preferred by developers used to the existing CSS preprocessing ecosystem (e.g. SASS). It seems premature to commit esbuild to specific semantics for this syntax at this time given the ongoing debate. - Fix cross-file CSS rule deduplication involving `url()` tokens ([#​2936](https://togithub.com/evanw/esbuild/issues/2936)) Previously cross-file CSS rule deduplication didn't handle `url()` tokens correctly. These tokens contain references to import paths which may be internal (i.e. in the bundle) or external (i.e. not in the bundle). When comparing two `url()` tokens for equality, the underlying import paths should be compared instead of their references. This release of esbuild fixes `url()` token comparisons. One side effect is that `@font-face` rules should now be deduplicated correctly across files: ```css /* Original code */ @​import "data:text/css, \ @​import 'http://example.com/style.css'; \ @​font-face { src: url(http://example.com/font.ttf) }"; @​import "data:text/css, \ @​font-face { src: url(http://example.com/font.ttf) }"; /* Old output (with --bundle --minify) */ @​import"http://example.com/style.css";@​font-face{src:url(http://example.com/font.ttf)}@​font-face{src:url(http://example.com/font.ttf)} /* New output (with --bundle --minify) */ @​import"http://example.com/style.css";@​font-face{src:url(http://example.com/font.ttf)} ``` ### [`v0.17.9`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​0179) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.8...v0.17.9) - Parse rest bindings in TypeScript types ([#​2937](https://togithub.com/evanw/esbuild/issues/2937)) Previously esbuild was unable to parse the following valid TypeScript code: ```ts let tuple: (...[e1, e2, ...es]: any) => any ``` This release includes support for parsing code like this. - Fix TypeScript code translation for certain computed `declare` class fields ([#​2914](https://togithub.com/evanw/esbuild/issues/2914)) In TypeScript, the key of a computed `declare` class field should only be preserved if there are no decorators for that field. Previously esbuild always preserved the key, but esbuild will now remove the key to match the output of the TypeScript compiler: ```t

Configuration

📅 Schedule: Branch creation - "before 3am 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.

This PR has been generated by Mend Renovate. View repository job log here.