sleistner / vscode-fileutils

Visual Studio Code Extension
https://marketplace.visualstudio.com/items?itemName=sleistner.vscode-fileutils
MIT License
190 stars 26 forks source link

chore(deps): update dependency esbuild to v0.17.7 #518

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
esbuild 0.17.6 -> 0.17.7 age adoption passing confidence

Release Notes

evanw/esbuild ### [`v0.17.7`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#​0177) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.17.6...v0.17.7) - Change esbuild's parsing of TypeScript instantiation expressions to match TypeScript 4.8+ ([#​2907](https://togithub.com/evanw/esbuild/issues/2907)) This release updates esbuild's implementation of instantiation expression erasure to match [microsoft/TypeScript#​49353](https://togithub.com/microsoft/TypeScript/pull/49353). The new rules are as follows (copied from TypeScript's PR description): > When a potential type argument list is followed by > > - a line break, > - an `(` token, > - a template literal string, or > - any token except `<` or `>` that isn't the start of an expression, > > we consider that construct to be a type argument list. Otherwise we consider the construct to be a `<` relational expression followed by a `>` relational expression. - Ignore `sideEffects: false` for imported CSS files ([#​1370](https://togithub.com/evanw/esbuild/issues/1370), [#​1458](https://togithub.com/evanw/esbuild/pull/1458), [#​2905](https://togithub.com/evanw/esbuild/issues/2905)) This release ignores the `sideEffects` annotation in `package.json` for CSS files that are imported into JS files using esbuild's `css` loader. This means that these CSS files are no longer be tree-shaken. Importing CSS into JS causes esbuild to automatically create a CSS entry point next to the JS entry point containing the bundled CSS. Previously packages that specified some form of `"sideEffects": false` could potentially cause esbuild to consider one or more of the JS files on the import path to the CSS file to be side-effect free, which would result in esbuild removing that CSS file from the bundle. This was problematic because the removal of that CSS is outwardly observable, since all CSS is global, so it was incorrect for previous versions of esbuild to tree-shake CSS files imported into JS files. - Add constant folding for certain additional equality cases ([#​2394](https://togithub.com/evanw/esbuild/issues/2394), [#​2895](https://togithub.com/evanw/esbuild/issues/2895)) This release adds constant folding for expressions similar to the following: ```js // Original input console.log( null === 'foo', null === undefined, null == undefined, false === 0, false == 0, 1 === true, 1 == true, ) // Old output console.log( null === "foo", null === void 0, null == void 0, false === 0, false == 0, 1 === true, 1 == true ); // New output console.log( false, false, true, false, true, false, true ); ```

Configuration

πŸ“… Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

β™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

πŸ”• Ignore: Close this PR and you won't be reminded about this update again.



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

sleistner commented 1 year ago

:tada: This PR is included in version 3.10.1 :tada:

The release is available on:

Your semantic-release bot :package::rocket: