search

unjs / unplugin

Unified plugin system for Vite, Rollup, Webpack, esbuild, Rolldown, and more
https://unplugin.unjs.io
MIT License
2.9k stars 104 forks source link

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

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
@antfu/eslint-config ^0.39.4 -> ^0.39.5 age adoption passing confidence
@antfu/ni ^0.21.3 -> ^0.21.4 age adoption passing confidence
@rspack/cli (source) ^0.2.0 -> ^0.2.1 age adoption passing confidence
@rspack/core (source) ^0.2.0 -> ^0.2.1 age adoption passing confidence
bumpp ^9.1.0 -> ^9.1.1 age adoption passing confidence
esbuild ^0.17.19 -> ^0.18.0 age adoption passing confidence
pnpm (source) 8.6.0 -> 8.6.1 age adoption passing confidence
rollup (source) ^3.23.0 -> ^3.24.1 age adoption passing confidence
vitest ^0.31.4 -> ^0.32.0 age adoption passing confidence
webpack ^5.85.0 -> ^5.86.0 age adoption passing confidence

Release Notes

antfu/eslint-config ### [`v0.39.5`](https://togithub.com/antfu/eslint-config/releases/tag/v0.39.5) [Compare Source](https://togithub.com/antfu/eslint-config/compare/v0.39.4...v0.39.5) #####    🚀 Features - **basic**: Ban deprecated syntax  -  by [@​zanminkian](https://togithub.com/zanminkian) in [https://github.com/antfu/eslint-config/issues/194](https://togithub.com/antfu/eslint-config/issues/194) [(0947d)](https://togithub.com/antfu/eslint-config/commit/0947ddb) #####    🐞 Bug Fixes - Disable `@typescript-eslint/consistent-type-assertions`  -  by [@​antfu](https://togithub.com/antfu) [(abf5c)](https://togithub.com/antfu/eslint-config/commit/abf5c27) #####     [View changes on GitHub](https://togithub.com/antfu/eslint-config/compare/v0.39.4...v0.39.5)
antfu/ni ### [`v0.21.4`](https://togithub.com/antfu/ni/releases/tag/v0.21.4) [Compare Source](https://togithub.com/antfu/ni/compare/v0.21.3...v0.21.4) #####    🚀 Features - Silent programmatic usage  -  by [@​millsp](https://togithub.com/millsp) in [https://github.com/antfu/ni/issues/151](https://togithub.com/antfu/ni/issues/151) [(3f86b)](https://togithub.com/antfu/ni/commit/3f86bf4) #####     [View changes on GitHub](https://togithub.com/antfu/ni/compare/v0.21.3...v0.21.4)
web-infra-dev/rspack ### [`v0.2.1`](https://togithub.com/web-infra-dev/rspack/releases/tag/0.2.1) [Compare Source](https://togithub.com/web-infra-dev/rspack/compare/0.2.0...0.2.1) #### What's Changed ##### Exciting New Features 🎉 - feat: nested module rules by [@​ahabhgk](https://togithub.com/ahabhgk) in [https://github.com/web-infra-dev/rspack/pull/3380](https://togithub.com/web-infra-dev/rspack/pull/3380) - feat: support compiler.hooks.assetEmitted by [@​jerrykingxyz](https://togithub.com/jerrykingxyz) in [https://github.com/web-infra-dev/rspack/pull/3387](https://togithub.com/web-infra-dev/rspack/pull/3387) - feat: make options having a single source of truth by [@​hyf0](https://togithub.com/hyf0) in [https://github.com/web-infra-dev/rspack/pull/3378](https://togithub.com/web-infra-dev/rspack/pull/3378) - feat: resource within scheme by [@​ahabhgk](https://togithub.com/ahabhgk) in [https://github.com/web-infra-dev/rspack/pull/3367](https://togithub.com/web-infra-dev/rspack/pull/3367) - feat: support file uri by [@​ahabhgk](https://togithub.com/ahabhgk) in [https://github.com/web-infra-dev/rspack/pull/3397](https://togithub.com/web-infra-dev/rspack/pull/3397) - feat: add finishMake hook by [@​dmitry-stepanenko](https://togithub.com/dmitry-stepanenko) in [https://github.com/web-infra-dev/rspack/pull/3390](https://togithub.com/web-infra-dev/rspack/pull/3390) - feat: create-rspack add template-vue by [@​faga295](https://togithub.com/faga295) in [https://github.com/web-infra-dev/rspack/pull/2153](https://togithub.com/web-infra-dev/rspack/pull/2153) - feat: Add 'succeedModule' and 'stillValidModule' hooks by [@​annanShao](https://togithub.com/annanShao) in [https://github.com/web-infra-dev/rspack/pull/3318](https://togithub.com/web-infra-dev/rspack/pull/3318) - feat(config): friendly config error message by [@​hyf0](https://togithub.com/hyf0) in [https://github.com/web-infra-dev/rspack/pull/3413](https://togithub.com/web-infra-dev/rspack/pull/3413) - feat(config): zod schema for optimization by [@​hyf0](https://togithub.com/hyf0) in [https://github.com/web-infra-dev/rspack/pull/3416](https://togithub.com/web-infra-dev/rspack/pull/3416) - feat(splitChunks): support passing `false` to `splitChunks.{cacheGroup}.xxx` by [@​hyf0](https://togithub.com/hyf0) in [https://github.com/web-infra-dev/rspack/pull/3420](https://togithub.com/web-infra-dev/rspack/pull/3420) - feat: electron support by [@​ahabhgk](https://togithub.com/ahabhgk) in [https://github.com/web-infra-dev/rspack/pull/3414](https://togithub.com/web-infra-dev/rspack/pull/3414) ##### Bug Fixes 🐞 - fix: update lock for ecosystem-ci by [@​ahabhgk](https://togithub.com/ahabhgk) in [https://github.com/web-infra-dev/rspack/pull/3385](https://togithub.com/web-infra-dev/rspack/pull/3385) - fix: metric recover by [@​IWANABETHATGUY](https://togithub.com/IWANABETHATGUY) in [https://github.com/web-infra-dev/rspack/pull/3388](https://togithub.com/web-infra-dev/rspack/pull/3388) - fix(rust): use jemallocator for linux gnu, mimalloc for everything else by [@​Boshen](https://togithub.com/Boshen) in [https://github.com/web-infra-dev/rspack/pull/3350](https://togithub.com/web-infra-dev/rspack/pull/3350) - fix: fix aarch64-unknown-linux-gnu not building jemallocator by [@​Boshen](https://togithub.com/Boshen) in [https://github.com/web-infra-dev/rspack/pull/3405](https://togithub.com/web-infra-dev/rspack/pull/3405) - fix: remove css updatedModulesList at hmr by [@​underfin](https://togithub.com/underfin) in [https://github.com/web-infra-dev/rspack/pull/3399](https://togithub.com/web-infra-dev/rspack/pull/3399) - fix: shouldn't diff hot update chunk at hmr by [@​underfin](https://togithub.com/underfin) in [https://github.com/web-infra-dev/rspack/pull/3411](https://togithub.com/web-infra-dev/rspack/pull/3411) - fix: support config version when emitAsset by [@​jerrykingxyz](https://togithub.com/jerrykingxyz) in [https://github.com/web-infra-dev/rspack/pull/3415](https://togithub.com/web-infra-dev/rspack/pull/3415) - fix: sourcemap as an empty string by [@​h-a-n-a](https://togithub.com/h-a-n-a) in [https://github.com/web-infra-dev/rspack/pull/3426](https://togithub.com/web-infra-dev/rspack/pull/3426) - fix(types): export `OptimizationSplitChunksOptions` for compatibility and enable validating for optimization by [@​hyf0](https://togithub.com/hyf0) in [https://github.com/web-infra-dev/rspack/pull/3435](https://togithub.com/web-infra-dev/rspack/pull/3435) - fix(types): type error for `runtimeChunk` by [@​hyf0](https://togithub.com/hyf0) in [https://github.com/web-infra-dev/rspack/pull/3442](https://togithub.com/web-infra-dev/rspack/pull/3442) - fix(context_module_cache): fix cache directory bug by [@​suxin2017](https://togithub.com/suxin2017) in [https://github.com/web-infra-dev/rspack/pull/3271](https://togithub.com/web-infra-dev/rspack/pull/3271) ##### Other Changes - chore: 🤖 disable for now by [@​IWANABETHATGUY](https://togithub.com/IWANABETHATGUY) in [https://github.com/web-infra-dev/rspack/pull/3384](https://togithub.com/web-infra-dev/rspack/pull/3384) - chore: 🤖 tweak word case by [@​IWANABETHATGUY](https://togithub.com/IWANABETHATGUY) in [https://github.com/web-infra-dev/rspack/pull/3389](https://togithub.com/web-infra-dev/rspack/pull/3389) - chore: update vue example by [@​h-a-n-a](https://togithub.com/h-a-n-a) in [https://github.com/web-infra-dev/rspack/pull/3386](https://togithub.com/web-infra-dev/rspack/pull/3386) - chore: delete npm folder by [@​hardfist](https://togithub.com/hardfist) in [https://github.com/web-infra-dev/rspack/pull/3394](https://togithub.com/web-infra-dev/rspack/pull/3394) - chore: add back vue build by [@​h-a-n-a](https://togithub.com/h-a-n-a) in [https://github.com/web-infra-dev/rspack/pull/3393](https://togithub.com/web-infra-dev/rspack/pull/3393) - chore: remove commit step when publishing by [@​hardfist](https://togithub.com/hardfist) in [https://github.com/web-infra-dev/rspack/pull/3395](https://togithub.com/web-infra-dev/rspack/pull/3395) - chore: add back npm packages for local publishing by [@​h-a-n-a](https://togithub.com/h-a-n-a) in [https://github.com/web-infra-dev/rspack/pull/3396](https://togithub.com/web-infra-dev/rspack/pull/3396) - chore: add vue2-ts example by [@​hardfist](https://togithub.com/hardfist) in [https://github.com/web-infra-dev/rspack/pull/3398](https://togithub.com/web-infra-dev/rspack/pull/3398) - chore: support short build commands by [@​h-a-n-a](https://togithub.com/h-a-n-a) in [https://github.com/web-infra-dev/rspack/pull/3400](https://togithub.com/web-infra-dev/rspack/pull/3400) - chore(packages): upload less files to npm by [@​Boshen](https://togithub.com/Boshen) in [https://github.com/web-infra-dev/rspack/pull/3362](https://togithub.com/web-infra-dev/rspack/pull/3362) - chore: fix release mr by [@​hardfist](https://togithub.com/hardfist) in [https://github.com/web-infra-dev/rspack/pull/3427](https://togithub.com/web-infra-dev/rspack/pull/3427) - chore: add release nigthly after full release by [@​hardfist](https://togithub.com/hardfist) in [https://github.com/web-infra-dev/rspack/pull/3429](https://togithub.com/web-infra-dev/rspack/pull/3429) - chore(webpack-test): --forceExit for open handles by [@​Boshen](https://togithub.com/Boshen) in [https://github.com/web-infra-dev/rspack/pull/3432](https://togithub.com/web-infra-dev/rspack/pull/3432) - chore: fix binding by [@​hardfist](https://togithub.com/hardfist) in [https://github.com/web-infra-dev/rspack/pull/3443](https://togithub.com/web-infra-dev/rspack/pull/3443) - test: webpack cache deps test to file deps test by [@​jerrykingxyz](https://togithub.com/jerrykingxyz) in [https://github.com/web-infra-dev/rspack/pull/3445](https://togithub.com/web-infra-dev/rspack/pull/3445) #### New Contributors - [@​dmitry-stepanenko](https://togithub.com/dmitry-stepanenko) made their first contribution in [https://github.com/web-infra-dev/rspack/pull/3390](https://togithub.com/web-infra-dev/rspack/pull/3390) - [@​annanShao](https://togithub.com/annanShao) made their first contribution in [https://github.com/web-infra-dev/rspack/pull/3318](https://togithub.com/web-infra-dev/rspack/pull/3318) **Full Changelog**: https://github.com/web-infra-dev/rspack/compare/0.2.0...0.2.1
antfu/bumpp ### [`v9.1.1`](https://togithub.com/antfu/bumpp/releases/tag/v9.1.1) [Compare Source](https://togithub.com/antfu/bumpp/compare/v9.1.0...v9.1.1) *No significant changes* #####     [View changes on GitHub](https://togithub.com/antfu/bumpp/compare/v9.1.0...v9.1.1)
evanw/esbuild ### [`v0.18.0`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​0180) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.19...v0.18.0) **This release deliberately contains backwards-incompatible changes.** To avoid automatically picking up releases like this, you should either be pinning the exact version of `esbuild` in your `package.json` file (recommended) or be using a version range syntax that only accepts patch upgrades such as `^0.17.0` or `~0.17.0`. See npm's documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information. The breaking changes in this release mainly focus on fixing some long-standing issues with esbuild's handling of `tsconfig.json` files. Here are all the changes in this release, in detail: - Add a way to try esbuild online ([#​797](https://togithub.com/evanw/esbuild/issues/797)) There is now a way to try esbuild live on esbuild's website without installing it: https://esbuild.github.io/try/. In addition to being able to more easily evaluate esbuild, this should also make it more efficient to generate esbuild bug reports. For example, you can use it to compare the behavior of different versions of esbuild on the same input. The state of the page is stored in the URL for easy sharing. Many thanks to [@​hyrious](https://togithub.com/hyrious) for creating https://hyrious.me/esbuild-repl/, which was the main inspiration for this addition to esbuild's website. Two forms of build options are supported: either CLI-style ([example](https://esbuild.github.io/try/#dAAwLjE3LjE5AC0tbG9hZGVyPXRzeCAtLW1pbmlmeSAtLXNvdXJjZW1hcABsZXQgZWw6IEpTWC5FbGVtZW50ID0gPGRpdiAvPg)) or JS-style ([example](https://esbuild.github.io/try/#dAAwLjE3LjE5AHsKICBsb2FkZXI6ICd0c3gnLAogIG1pbmlmeTogdHJ1ZSwKICBzb3VyY2VtYXA6IHRydWUsCn0AbGV0IGVsOiBKU1guRWxlbWVudCA9IDxkaXYgLz4)). Both are converted into a JS object that's passed to esbuild's WebAssembly API. The CLI-style argument parser is a custom one that simulates shell quoting rules, and the JS-style argument parser is also custom and parses a superset of JSON (basically JSON5 + regular expressions). So argument parsing is an approximate simulation of what happens for real but hopefully it should be close enough. - Changes to esbuild's `tsconfig.json` support ([#​3019](https://togithub.com/evanw/esbuild/issues/3019)): This release makes the following changes to esbuild's `tsconfig.json` support: - Using experimental decorators now requires `"experimentalDecorators": true` ([#​104](https://togithub.com/evanw/esbuild/issues/104)) Previously esbuild would always compile decorators in TypeScript code using TypeScript's experimental decorator transform. Now that standard JavaScript decorators are close to being finalized, esbuild will now require you to use `"experimentalDecorators": true` to do this. This new requirement makes it possible for esbuild to introduce a transform for standard JavaScript decorators in TypeScript code in the future. Such a transform has not been implemented yet, however. - TypeScript's `target` no longer affects esbuild's `target` ([#​2628](https://togithub.com/evanw/esbuild/issues/2628)) Some people requested that esbuild support TypeScript's `target` setting, so support for it was added (in [version 0.12.4](https://togithub.com/evanw/esbuild/releases/v0.12.4)). However, esbuild supports reading from multiple `tsconfig.json` files within a single build, which opens up the possibility that different files in the build have different language targets configured. There isn't really any reason to do this and it can lead to unexpected results. So with this release, the `target` setting in `tsconfig.json` will no longer affect esbuild's own `target` setting. You will have to use esbuild's own target setting instead (which is a single, global value). - TypeScript's `jsx` setting no longer causes esbuild to preserve JSX syntax ([#​2634](https://togithub.com/evanw/esbuild/issues/2634)) TypeScript has a setting called [`jsx`](https://www.typescriptlang.org/tsconfig#jsx) that controls how to transform JSX into JS. The tool-agnostic transform is called `react`, and the React-specific transform is called `react-jsx` (or `react-jsxdev`). There is also a setting called `preserve` which indicates JSX should be passed through untransformed. Previously people would run esbuild with `"jsx": "preserve"` in their `tsconfig.json` files and then be surprised when esbuild preserved their JSX. So with this release, esbuild will now ignore `"jsx": "preserve"` in `tsconfig.json` files. If you want to preserve JSX syntax with esbuild, you now have to use `--jsx=preserve`. Note: Some people have suggested that esbuild's equivalent `jsx` setting override the one in `tsconfig.json`. However, some projects need to legitimately have different files within the same build use different transforms (i.e. `react` vs. `react-jsx`) and having esbuild's global `jsx` setting override `tsconfig.json` would prevent this from working. This release ignores `"jsx": "preserve"` but still allows other `jsx` values in `tsconfig.json` files to override esbuild's global `jsx` setting to keep the ability for multiple files within the same build to use different transforms. - `useDefineForClassFields` behavior has changed ([#​2584](https://togithub.com/evanw/esbuild/issues/2584), [#​2993](https://togithub.com/evanw/esbuild/issues/2993)) Class fields in TypeScript look like this (`x` is a class field): ```js class Foo { x = 123 } ``` TypeScript has legacy behavior that uses assignment semantics instead of define semantics for class fields when [`useDefineForClassFields`](https://www.typescriptlang.org/tsconfig#useDefineForClassFields) is enabled (in which case class fields in TypeScript behave differently than they do in JavaScript, which is arguably "wrong"). This legacy behavior exists because TypeScript added class fields to TypeScript before they were added to JavaScript. The TypeScript team decided to go with assignment semantics and shipped their implementation. Much later on TC39 decided to go with define semantics for class fields in JavaScript instead. This behaves differently if the base class has a setter with the same name: ```js class Base { set x(_) { console.log('x:', _) } } // useDefineForClassFields: false class AssignSemantics extends Base { constructor() { super() this.x = 123 } } // useDefineForClassFields: true class DefineSemantics extends Base { constructor() { super() Object.defineProperty(this, 'x', { value: 123 }) } } console.log( new AssignSemantics().x, // Calls the setter new DefineSemantics().x // Doesn't call the setter ) ``` When you run `tsc`, the value of `useDefineForClassFields` defaults to `false` when it's not specified and the `target` in `tsconfig.json` is present but earlier than `ES2022`. This sort of makes sense because the class field language feature was added in ES2022, so before ES2022 class fields didn't exist (and thus TypeScript's legacy behavior is active). However, TypeScript's `target` setting currently defaults to `ES3` which unfortunately means that the `useDefineForClassFields` setting currently defaults to false (i.e. to "wrong"). In other words if you run `tsc` with all default settings, class fields will behave incorrectly. Previously esbuild tried to do what `tsc` did. That meant esbuild's version of `useDefineForClassFields` was `false` by default, and was also `false` if esbuild's `--target=` was present but earlier than `es2022`. However, TypeScript's legacy class field behavior is becoming increasingly irrelevant and people who expect class fields in TypeScript to work like they do in JavaScript are confused when they use esbuild with default settings. It's also confusing that the behavior of class fields would change if you changed the language target (even though that's exactly how TypeScript works). So with this release, esbuild will now only use the information in `tsconfig.json` to determine whether `useDefineForClassFields` is true or not. Specifically `useDefineForClassFields` will be respected if present, otherwise it will be `false` if `target` is present in `tsconfig.json` and is `ES2021` or earlier, otherwise it will be `true`. Targets passed to esbuild's `--target=` setting will no longer affect `useDefineForClassFields`. Note that this means different directories in your build can have different values for this setting since esbuild allows different directories to have different `tsconfig.json` files within the same build. This should let you migrate your code one directory at a time without esbuild's `--target=` setting affecting the semantics of your code. - Add support for `verbatimModuleSyntax` from TypeScript 5.0 TypeScript 5.0 added a new option called [`verbatimModuleSyntax`](https://www.typescriptlang.org/tsconfig#verbatimModuleSyntax) that deprecates and replaces two older options, `preserveValueImports` and `importsNotUsedAsValues`. Setting `verbatimModuleSyntax` to true in `tsconfig.json` tells esbuild to not drop unused import statements. Specifically esbuild now treats `"verbatimModuleSyntax": true` as if you had specified both `"preserveValueImports": true` and `"importsNotUsedAsValues": "preserve"`. - Add multiple inheritance for `tsconfig.json` from TypeScript 5.0 TypeScript 5.0 now allows [multiple inheritance for `tsconfig.json` files](https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#supporting-multiple-configuration-files-in-extends). You can now pass an array of filenames via the `extends` parameter and your `tsconfig.json` will start off containing properties from all of those configuration files, in order. This release of esbuild adds support for this new TypeScript feature. - Remove support for `moduleSuffixes` ([#​2395](https://togithub.com/evanw/esbuild/issues/2395)) The community has requested that esbuild remove support for TypeScript's `moduleSuffixes` feature, so it has been removed in this release. Instead you can use esbuild's `--resolve-extensions=` feature to select which module suffix you want to build with. - Apply `--tsconfig=` overrides to `stdin` and virtual files ([#​385](https://togithub.com/evanw/esbuild/issues/385), [#​2543](https://togithub.com/evanw/esbuild/issues/2543)) When you override esbuild's automatic `tsconfig.json` file detection with `--tsconfig=` to pass a specific `tsconfig.json` file, esbuild previously didn't apply these settings to source code passed via the `stdin` API option or to TypeScript files from plugins that weren't in the `file` namespace. This release changes esbuild's behavior so that settings from `tsconfig.json` also apply to these source code files as well. - Support `--tsconfig-raw=` in build API calls ([#​943](https://togithub.com/evanw/esbuild/issues/943), [#​2440](https://togithub.com/evanw/esbuild/issues/2440)) Previously if you wanted to override esbuild's automatic `tsconfig.json` file detection, you had to create a new `tsconfig.json` file and pass the file name to esbuild via the `--tsconfig=` flag. With this release, you can now optionally use `--tsconfig-raw=` instead to pass the contents of `tsconfig.json` to esbuild directly instead of passing the file name. For example, you can now use `--tsconfig-raw={"compilerOptions":{"experimentalDecorators":true}}` to enable TypeScript experimental decorators directly using a command-line flag (assuming you escape the quotes correctly using your current shell's quoting rules). The `--tsconfig-raw=` flag previously only worked with transform API calls but with this release, it now works with build API calls too. - Ignore all `tsconfig.json` files in `node_modules` ([#​276](https://togithub.com/evanw/esbuild/issues/276), [#​2386](https://togithub.com/evanw/esbuild/issues/2386)) This changes esbuild's behavior that applies `tsconfig.json` to all files in the subtree of the directory containing `tsconfig.json`. In version 0.12.7, esbuild started ignoring `tsconfig.json` files inside `node_modules` folders. The rationale is that people typically do this by mistake and that doing this intentionally is a rare use case that doesn't need to be supported. However, this change only applied to certain syntax-specific settings (e.g. `jsxFactory`) but did not apply to path resolution settings (e.g. `paths`). With this release, esbuild will now ignore all `tsconfig.json` files in `node_modules` instead of only ignoring certain settings. - Ignore `tsconfig.json` when resolving paths within `node_modules` ([#​2481](https://togithub.com/evanw/esbuild/issues/2481)) Previously fields in `tsconfig.json` related to path resolution (e.g. `paths`) were respected for all files in the subtree containing that `tsconfig.json` file, even within a nested `node_modules` subdirectory. This meant that a project's `paths` settings could potentially affect any bundled packages. With this release, esbuild will no longer use `tsconfig.json` settings during path resolution inside nested `node_modules` subdirectories. - Prefer `.js` over `.ts` within `node_modules` ([#​3019](https://togithub.com/evanw/esbuild/issues/3019)) The default list of implicit extensions that esbuild will try appending to import paths contains `.ts` before `.js`. This makes it possible to bundle TypeScript projects that reference other files in the project using extension-less imports (e.g. `./some-file` to load `./some-file.ts` instead of `./some-file.js`). However, this behavior is undesirable within `node_modules` directories. Some package authors publish both their original TypeScript code and their compiled JavaScript code side-by-side. In these cases, esbuild should arguably be using the compiled JavaScript files instead of the original TypeScript files because the TypeScript compilation settings for files within the package should be determined by the package author, not the user of esbuild. So with this release, esbuild will now prefer implicit `.js` extensions over `.ts` when searching for import paths within `node_modules`. These changes are intended to improve esbuild's compatibility with `tsc` and reduce the number of unfortunate behaviors regarding `tsconfig.json` and esbuild. - Add a workaround for bugs in Safari 16.2 and earlier ([#​3072](https://togithub.com/evanw/esbuild/issues/3072)) Safari's JavaScript parser had a bug (which has now been fixed) where at least something about unary/binary operators nested inside default arguments nested inside either a function or class expression was incorrectly considered a syntax error if that expression was the target of a property assignment. Here are some examples that trigger this Safari bug: ❱ x(function (y = -1) {}.z = 2) SyntaxError: Left hand side of operator '=' must be a reference. ❱ x(class { f(y = -1) {} }.z = 2) SyntaxError: Left hand side of operator '=' must be a reference. It's not clear what the exact conditions are that trigger this bug. However, a workaround for this bug appears to be to post-process your JavaScript to wrap any in function and class declarations that are the direct target of a property access expression in parentheses. That's the workaround that UglifyJS applies for this issue: [mishoo/UglifyJS#​2056](https://togithub.com/mishoo/UglifyJS/pull/2056). So that's what esbuild now does starting with this release: ```js // Original code x(function (y = -1) {}.z = 2, class { f(y = -1) {} }.z = 2) // Old output (with --minify --target=safari16.2) x(function(c=-1){}.z=2,class{f(c=-1){}}.z=2); // New output (with --minify --target=safari16.2) x((function(c=-1){}).z=2,(class{f(c=-1){}}).z=2); ``` This fix is not enabled by default. It's only enabled when `--target=` contains Safari 16.2 or earlier, such as with `--target=safari16.2`. You can also explicitly enable or disable this specific transform (called `function-or-class-property-access`) with `--supported:function-or-class-property-access=false`. - Fix esbuild's TypeScript type declarations to forbid unknown properties ([#​3089](https://togithub.com/evanw/esbuild/issues/3089)) Version 0.17.0 of esbuild introduced a specific form of function overloads in the TypeScript type definitions for esbuild's API calls that looks like this: ```ts interface TransformOptions { legalComments?: 'none' | 'inline' | 'eof' | 'external' } interface TransformResult { legalComments: string | (ProvidedOptions['legalComments'] extends 'external' ? never : undefined) } declare function transformSync(input: string, options?: ProvidedOptions): TransformResult declare function transformSync(input: string, options?: TransformOptions): TransformResult ``` This more accurately reflects how esbuild's JavaScript API behaves. The result object returned by `transformSync` only has the `legalComments` property if you pass `legalComments: 'external'`: ```ts // These have type "string | undefined" transformSync('').legalComments transformSync('', { legalComments: 'eof' }).legalComments // This has type "string" transformSync('', { legalComments: 'external' }).legalComments ``` However, this form of function overloads unfortunately allows typos (e.g. `egalComments`) to pass the type checker without generating an error as TypeScript allows all objects with unknown properties to extend `TransformOptions`. These typos result in esbuild's API throwing an error at run-time. To prevent typos during type checking, esbuild's TypeScript type definitions will now use a different form that looks like this: ```ts type SameShape = In & { [Key in Exclude]: never } interface TransformOptions { legalComments?: 'none' | 'inline' | 'eof' | 'external' } interface TransformResult { legalComments: string | (ProvidedOptions['legalComments'] extends 'external' ? never : undefined) } declare function transformSync(input: string, options?: SameShape): TransformResult ``` This change should hopefully not affect correct code. It should hopefully introduce type errors only for incorrect code. - Fix CSS nesting transform for pseudo-elements ([#​3119](https://togithub.com/evanw/esbuild/issues/3119)) This release fixes esbuild's CSS nesting transform for pseudo-elements (e.g. `::before` and `::after`). The CSS nesting specification says that [the nesting selector does not work with pseudo-elements](https://www.w3.org/TR/css-nesting-1/#ref-for-matches-pseudo%E2%91%A0). This can be seen in the example below: esbuild does not carry the parent pseudo-element `::before` through the nesting selector `&`. However, that doesn't apply to pseudo-elements that are within the same selector. Previously esbuild had a bug where it considered pseudo-elements in both locations as invalid. This release changes esbuild to only consider those from the parent selector invalid, which should align with the specification: ```css /* Original code */ a, b::before { &.c, &::after { content: 'd'; } } /* Old output (with --target=chrome90) */ a:is(.c, ::after) { content: "d"; } /* New output (with --target=chrome90) */ a.c, a::after { content: "d"; } ``` - Forbid `&` before a type selector in nested CSS The people behind the work-in-progress CSS nesting specification have very recently [decided to forbid nested CSS that looks like `&div`](https://togithub.com/w3c/csswg-drafts/issues/8662#issuecomment-1514977935). You will have to use either `div&` or `&:is(div)` instead. This release of esbuild has been updated to take this new change into consideration. Doing this now generates a warning. The suggested fix is slightly different depending on where in the overall selector it happened: ▲ [WARNING] Cannot use type selector "input" directly after nesting selector "&" [css-syntax-error] example.css:2:3: 2 │ &input { │ ~~~~~ ╵ :is(input) CSS nesting syntax does not allow the "&" selector to come before a type selector. You can wrap this selector in ":is()" as a workaround. This restriction exists to avoid problems with SASS nesting, where the same syntax means something very different that has no equivalent in real CSS (appending a suffix to the parent selector). ▲ [WARNING] Cannot use type selector "input" directly after nesting selector "&" [css-syntax-error] example.css:6:8: 6 │ .form &input { │ ~~~~~~ ╵ input& CSS nesting syntax does not allow the "&" selector to come before a type selector. You can move the "&" to the end of this selector as a workaround. This restriction exists to avoid problems with SASS nesting, where the same syntax means something very different that has no equivalent in real CSS (appending a suffix to the parent selector).
pnpm/pnpm ### [`v8.6.1`](https://togithub.com/pnpm/pnpm/releases/tag/v8.6.1) [Compare Source](https://togithub.com/pnpm/pnpm/compare/v8.6.0...v8.6.1) #### Patch Changes - When `dedupe-peer-dependents` is enabled (default), use the path (not id) to determine compatibility. When multiple dependency groups can be deduplicated, the latter ones are sorted according to number of peers to allow them to benefit from deduplication. Resolves: [#​6605](https://togithub.com/pnpm/pnpm/issues/6605) - Some minor performance improvements by removing await from loops [#​6617](https://togithub.com/pnpm/pnpm/pull/6617). #### Our Gold Sponsors
#### Our Silver Sponsors
rollup/rollup ### [`v3.24.1`](https://togithub.com/rollup/rollup/blob/HEAD/CHANGELOG.md#​3241) [Compare Source](https://togithub.com/rollup/rollup/compare/v3.24.0...v3.24.1) *2023-06-10* ##### Bug Fixes - Fix an issue where bundles with `@rollup/plugin-commonjs` were missing internal dependencies when code-splitting ([#​5029](https://togithub.com/rollup/rollup/issues/5029)) - Do not use `process.exit(0)` in watch mode to avoid issues in embedded scenarios ([#​5027](https://togithub.com/rollup/rollup/issues/5027)) ##### Pull Requests - [#​5027](https://togithub.com/rollup/rollup/pull/5027): fix turborepo with rollup --watch ([@​plumber-dhaval](https://togithub.com/plumber-dhaval)) - [#​5028](https://togithub.com/rollup/rollup/pull/5028): chore(deps): lock file maintenance minor/patch updates ([@​renovate](https://togithub.com/renovate)\[bot]) - [#​5029](https://togithub.com/rollup/rollup/pull/5029): fix: get right sideEffectModules ([@​TrickyPi](https://togithub.com/TrickyPi)) ### [`v3.24.0`](https://togithub.com/rollup/rollup/blob/HEAD/CHANGELOG.md#​3240) [Compare Source](https://togithub.com/rollup/rollup/compare/v3.23.1...v3.24.0) *2023-06-07* ##### Features - Add new annotation `/* #__NO_SIDE_EFFECTS__ */` to mark function declarations as side effect free ([#​5024](https://togithub.com/rollup/rollup/issues/5024)) ##### Pull Requests - [#​5024](https://togithub.com/rollup/rollup/pull/5024): feat: support `#__NO_SIDE_EFFECTS__` annotation for function declaration ([@​antfu](https://togithub.com/antfu)) ### [`v3.23.1`](https://togithub.com/rollup/rollup/blob/HEAD/CHANGELOG.md#​3231) [Compare Source](https://togithub.com/rollup/rollup/compare/v3.23.0...v3.23.1) *2023-06-04* ##### Bug Fixes - Ensure the last segment of sourcemapBaseUrl is never omitted ([#​5022](https://togithub.com/rollup/rollup/issues/5022)) ##### Pull Requests - [#​5006](https://togithub.com/rollup/rollup/pull/5006): Better workflow caching ([@​lukastaegert](https://togithub.com/lukastaegert)) - [#​5012](https://togithub.com/rollup/rollup/pull/5012): chore(deps): lock file maintenance minor/patch updates ([@​renovate](https://togithub.com/renovate)\[bot]) - [#​5022](https://togithub.com/rollup/rollup/pull/5022): fix: add a trailing slash automatically for sourcemapBaseUrl ([@​TrickyPi](https://togithub.com/TrickyPi)) - [#​5023](https://togithub.com/rollup/rollup/pull/5023): chore(deps): lock file maintenance minor/patch updates ([@​renovate](https://togithub.com/renovate)\[bot])
vitest-dev/vitest ### [`v0.32.0`](https://togithub.com/vitest-dev/vitest/releases/tag/v0.32.0) [Compare Source](https://togithub.com/vitest-dev/vitest/compare/v0.31.4...v0.32.0) #####    🚨 Breaking Changes - Throw an error, if the module cannot be resolved  -  by [@​sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3307](https://togithub.com/vitest-dev/vitest/issues/3307) [(1ad63)](https://togithub.com/vitest-dev/vitest/commit/1ad63b0c) - Vitest used to fall back to the original import when it could not resolve it to the file path or the virtual module. This leads to hard-to-find module graph mismatches if you had incorrect alias or relied on relative imports to be resolved to the project root (which is usual behavior in TypeScript) because the code accidentally "worked". With this release, Vitest will now throw an error if it cannot resolve the module - there are possible edge cases that are not covered yet, so if you have any problems with this, please open a separate issue with reproduction. - Improve globs  -  by [@​nickmccurdy](https://togithub.com/nickmccurdy) in [https://github.com/vitest-dev/vitest/issues/3392](https://togithub.com/vitest-dev/vitest/issues/3392) [(19ecc)](https://togithub.com/vitest-dev/vitest/commit/19ecc6c7) - Vitest now has glob patterns similar to Jest for better compatibility. It's possible that some files will be considered test files when previously they were not. For example, Vitest now considers `test.js` to be a test file. Also any file in `__tests__` is now considered to be a test, not just files with `test` or `spec` suffix. - Add `@vitest/coverage-v8` package  -  by [@​AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3339](https://togithub.com/vitest-dev/vitest/issues/3339) [(82112)](https://togithub.com/vitest-dev/vitest/commit/821126f1) - Vitest now uses v8 code coverage directly for better performance. `@vitest/coverage-c8` is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user has `c8` as their coverage provider. Please, install the new `@vitest/coverage-v8` package if you previously used `@vitest/coverage-c8`. - **mocker**: Don't restore mock to the original if the module is automocked  -  by [@​sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3518](https://togithub.com/vitest-dev/vitest/issues/3518) [(c1004)](https://togithub.com/vitest-dev/vitest/commit/c1004e14) - `spy.mockRestore` on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does. #####    🚀 Features - Support ssr optimizer  -  by [@​sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3490](https://togithub.com/vitest-dev/vitest/issues/3490) [(89842)](https://togithub.com/vitest-dev/vitest/commit/898422b0) - Image type add apng  -  by [@​btea](https://togithub.com/btea) in [https://github.com/vitest-dev/vitest/issues/3498](https://togithub.com/vitest-dev/vitest/issues/3498) [(a53c2)](https://togithub.com/vitest-dev/vitest/commit/a53c2151) - **expect**: Support `expect.soft`  -  by [@​Dunqing](https://togithub.com/Dunqing) in [https://github.com/vitest-dev/vitest/issues/3507](https://togithub.com/vitest-dev/vitest/issues/3507) [(7c687)](https://togithub.com/vitest-dev/vitest/commit/7c687ada) - **runner**: Support using function/class as `describe`/`test` name  -  by [@​fenghan34](https://togithub.com/fenghan34) in [https://github.com/vitest-dev/vitest/issues/3497](https://togithub.com/vitest-dev/vitest/issues/3497) [(15253)](https://togithub.com/vitest-dev/vitest/commit/15253890) #####    🐞 Bug Fixes - The cli option is passed to coverage.exclude  -  by [@​btea](https://togithub.com/btea) in [https://github.com/vitest-dev/vitest/issues/3506](https://togithub.com/vitest-dev/vitest/issues/3506) [(c37cd)](https://togithub.com/vitest-dev/vitest/commit/c37cdebe) - **optimizer**: Always respect optimizeDeps even if include/exclude is overridden  -  by [@​sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3488](https://togithub.com/vitest-dev/vitest/issues/3488) [(eb285)](https://togithub.com/vitest-dev/vitest/commit/eb285ea0) - **runner**: Ensure Vitest is deduped  -  by [@​sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3489](https://togithub.com/vitest-dev/vitest/issues/3489) [(2deb7)](https://togithub.com/vitest-dev/vitest/commit/2deb70ab) - **ui**: Don't cache coverage assets  -  by [@​userquin](https://togithub.com/userquin) in [https://github.com/vitest-dev/vitest/issues/3508](https://togithub.com/vitest-dev/vitest/issues/3508) [(952b5)](https://togithub.com/vitest-dev/vitest/commit/952b5be6) - **vite-node**: Circular import stuck  -  by [@​Dunqing](https://togithub.com/Dunqing) in [https://github.com/vitest-dev/vitest/issues/3480](https://togithub.com/vitest-dev/vitest/issues/3480) [(50f07)](https://togithub.com/vitest-dev/vitest/commit/50f0700d) - **watch**: Junit reporter fails to re-generate report  -  by [@​AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3496](https://togithub.com/vitest-dev/vitest/issues/3496) [(5b73c)](https://togithub.com/vitest-dev/vitest/commit/5b73cbf8) #####     [View changes on GitHub](https://togithub.com/vitest-dev/vitest/compare/v0.31.4...v0.32.0)
webpack/webpack ### [`v5.86.0`](https://togithub.com/webpack/webpack/releases/tag/v5.86.0) [Compare Source](https://togithub.com/webpack/webpack/compare/v5.85.1...v5.86.0) #### New Features - Improved cache size performance via better handling of serialization for errors and bigints by [@​alexander-akait](https://togithub.com/alexander-akait) in [https://github.com/webpack/webpack/pull/17282](https://togithub.com/webpack/webpack/pull/17282) - Introduce an export default handler function option for `ProgressPlugin` by [@​alexander-akait](https://togithub.com/alexander-akait) in [https://github.com/webpack/webpack/pull/17312](https://togithub.com/webpack/webpack/pull/17312) - Support passing `RegExp` to `splitChunks.chunks` by [@​hyf0](https://togithub.com/hyf0) in [https://github.com/webpack/webpack/pull/17332](https://togithub.com/webpack/webpack/pull/17332) #### Bug Fixes - Fix layer capabilities for `ContextModule` types by [@​huozhi](https://togithub.com/huozhi) in [https://github.com/webpack/webpack/pull/17310](https://togithub.com/webpack/webpack/pull/17310) - Fix compatibility of `__non_webpack_require__` with ES modules by [@​alexander-akait](https://togithub.com/alexander-akait) in [https://github.com/webpack/webpack/pull/17308](https://togithub.com/webpack/webpack/pull/17308) - Improve type coverage `Chunk`, `ChunkGroup`, and other plugins by [@​alexander-akait](https://togithub.com/alexander-akait) in [https://github.com/webpack/webpack/pull/1731](https://togithub.com/webpack/webpack/pull/1731) - Do not add `js` extension for eval source maps when extension is not resolvable by [@​alexander-akait](https://togithub.com/alexander-akait) in [https://github.com/webpack/webpack/pull/17331](https://togithub.com/webpack/webpack/pull/17331) #### Developer Experience - Improve type coverage for Json Module type and lazy load json-assertions package by [@​alexander-akait](https://togithub.com/alexander-akait) in [https://github.com/webpack/webpack/pull/17301](https://togithub.com/webpack/webpack/pull/17301) #### Dependencies & Maintenance - Bump memfs from 3.5.1 to 3.5.2 by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/webpack/webpack/pull/17315](https://togithub.com/webpack/webpack/pull/17315) - Bump webpack-cli from 5.1.1 to 5.1.3 by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/webpack/webpack/pull/17314](https://togithub.com/webpack/webpack/pull/17314) - Bump eslint from 8.41.0 to 8.42.0 by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/webpack/webpack/pull/17313](https://togithub.com/webpack/webpack/pull/17313) #### New Contributors - [@​huozhi](https://togithub.com/huozhi) made their first contribution in [https://github.com/webpack/webpack/pull/17310](https://togithub.com/webpack/webpack/pull/17310) - [@​hyf0](https://togithub.com/hyf0) made their first contribution in [https://github.com/webpack/webpack/pull/17332](https://togithub.com/webpack/webpack/pull/17332) **Full Changelog**: https://github.com/webpack/webpack/compare/v5.85.1...v5.86.0 ### [`v5.85.1`](https://togithub.com/webpack/webpack/releases/tag/v5.85.1) [Compare Source](https://togithub.com/webpack/webpack/compare/v5.85.0...v5.85.1) #### Bug Fixes - Fix bug in handling barrel imports ([#​17305](https://togithub.com/webpack/webpack/issues/17305)) by [@​bworline](https://togithub.com/bworline) in [https://github.com/webpack/webpack/pull/17307](https://togithub.com/webpack/webpack/pull/17307) - ***NOTE**: An internal API `BasicEvaluatedExpression.getMemberRangeStarts` has been changed to `BasicEvaluatedExpression.getMemberRanges`, please see type definition changes and the pull request for more information.* #### Dependencies & Maintenance - Bump [@​types/jest](https://togithub.com/types/jest) from 29.5.1 to 29.5.2 by [@​dependabot](https://togithub.com/dependabot) in [https://github.com/webpack/webpack/pull/17297](https://togithub.com/webpack/webpack/pull/17297) **Full Changelog**: https://github.com/webpack/webpack/compare/v5.85.0...v5.85.1

Configuration

📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).

🚦 Automerge: Enabled.

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