codecov[bot]
commented
2 years ago Codecov Report
Merging #493 (d987c4e) into master (a14aece) will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #493 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 8 8
Lines 342 342
Branches 51 51
=========================================
Hits 342 342 | Flag | Coverage Δ | |
|---|---|---|
| unittests | 100.00% <ø> (ø) |
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update a14aece...d987c4e. Read the comment docs.
This PR contains the following updates:
0.13.0->0.13.2Release Notes
evanw/esbuild
### [`v0.13.2`](https://togithub.com/evanw/esbuild/blob/master/CHANGELOG.md#0132) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.13.1...v0.13.2) - Fix `export {}` statements with `--tree-shaking=true` ([#1628](https://togithub.com/evanw/esbuild/issues/1628)) The new `--tree-shaking=true` option allows you to force-enable tree shaking in cases where it wasn't previously possible. One such case is when bundling is disabled and there is no output format configured, in which case esbuild just preserves the format of whatever format the input code is in. Enabling tree shaking in this context caused a bug where `export {}` statements were stripped. This release fixes the bug so `export {}` statements should now be preserved when you pass `--tree-shaking=true`. This bug only affected this new functionality and didn't affect existing scenarios. ### [`v0.13.1`](https://togithub.com/evanw/esbuild/blob/master/CHANGELOG.md#0131) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.13.0...v0.13.1) - Fix the `esbuild` package in yarn 2+ The [yarn package manager](https://yarnpkg.com/) version 2 and above has a mode called [PnP](https://next.yarnpkg.com/features/pnp/) that installs packages inside zip files instead of using individual files on disk, and then hijacks node's `fs` module to pretend that paths to files inside the zip file are actually individual files on disk so that code that wasn't written specifically for yarn still works. Unfortunately that hijacking is incomplete and it still causes certain things to break such as using these zip file paths to create a JavaScript worker thread or to create a child process. This was an issue for the new `optionalDependencies` package installation strategy that was just released in version 0.13.0 since the binary executable is now inside of an installed package instead of being downloaded using an install script. When it's installed with yarn 2+ in PnP mode the binary executable is inside a zip file and can't be run. To work around this, esbuild detects yarn's PnP mode and copies the binary executable to a real file outside of the zip file. Unfortunately the code to do this didn't create the parent directory before writing to the file path. That caused esbuild's API to crash when it was run for the first time. This didn't come up during testing because the parent directory already existed when the tests were run. This release changes the location of the binary executable from a shared cache directory to inside the esbuild package itself, which should fix this crash. This problem only affected esbuild's JS API when it was run through yarn 2+ with PnP mode active.Configuration
📅 Schedule: 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.