74b2db2
3.0.388f1429
update eslint. lint, fix unit tests.415d660
Snyk js braces 6838727 (#40)190510f
fix tests, skip 1 test in test/braces.expand716eb9f
readme bumpa5851e5
Merge pull request #37
from coderaiser/fix/vulnerability2092bd1
feature: braces: add maxSymbols (https://github.com/micromatch/braces/issues/...9f5b4cf
fix: vulnerability (https://security.snyk.io/vuln/SNYK-JS-BRACES-6838727)98414f9
remove funding file665ab5d
update keepEscaping doc (#27)Sourced from undici's releases.
v6.19.2
What's Changed
- fix #3337 by
@KhafraDevin nodejs/undici#3338- build: use
huskyashusky installis deprecated by@jazellyin nodejs/undici#3340- fix: interceptors.d.ts has no default export by
@Uzlopakin nodejs/undici#3332Full Changelog: https://github.com/nodejs/undici/compare/v6.19.1...v6.19.2
v6.19.1
What's Changed
- don't append empty origin by
@KhafraDevin nodejs/undici#3335Full Changelog: https://github.com/nodejs/undici/compare/v6.19.0...v6.19.1
v6.19.0
What's Changed
- build(deps): bump ossf/scorecard-action from 2.3.1 to 2.3.3 by
@dependabotin nodejs/undici#3305- build(deps): bump codecov/codecov-action from 4.3.1 to 4.4.1 by
@dependabotin nodejs/undici#3303- build(deps): bump step-security/harden-runner from 2.7.1 to 2.8.0 by
@dependabotin nodejs/undici#3304- build(deps): bump github/codeql-action from 3.25.3 to 3.25.7 by
@dependabotin nodejs/undici#3306- build(deps): bump node from
9e8f45ftodd7e693in /build by@dependabotin nodejs/undici#3309- build(deps): bump node from
dd7e693toe6d4495in /build by@dependabotin nodejs/undici#3313- remove websocket experimental warning by
@KhafraDevin nodejs/undici#3311- perf: optimization of request instantiation by
@tsctxin nodejs/undici#3107- perf: convert object to params by
@DarkGLin nodejs/undici#3302- build(deps-dev): bump borp from 0.14.0 to 0.15.0 by
@dependabotin nodejs/undici#3320- build(deps-dev): bump c8 from 9.1.0 to 10.0.0 by
@dependabotin nodejs/undici#3321- fix: add missing error classes to types by
@maxbeattyin nodejs/undici#3316- export interceptor to type def file by
@jakecastelliin nodejs/undici#3318- build(deps): bump node from
e6d4495to075a5ccin /build by@dependabotin nodejs/undici#3326- doc: clearify the behaviour of
bodyTimeoutin the request by@jakecastelliin nodejs/undici#3324- feature: support pre-shared sessions by
@tastypacketsin nodejs/undici#3325New Contributors
@maxbeattymade their first contribution in nodejs/undici#3316@jakecastellimade their first contribution in nodejs/undici#3318Full Changelog: https://github.com/nodejs/undici/compare/v6.18.2...v6.19.0
532b7b2
Bumped v6.19.2 (#3342)a7441d8
fix: interceptors.d.ts has no default export (#3332)5dadb95
build: use husky as husky install is
deprecated (#3340)035524e
fix #3337
(#3338)f6b9b44
Bumped v6.19.1 (#3336)1573f69
don't append empty origin (#3335)981fb3d
Bumped v6.19.039869b2
feature: support pre-shared sessions (#3325)7f54a24
doc: clearify the behaviour of bodyTimeout in the request
(#3324)9785b15
build(deps): bump node from e6d4495 to 075a5cc
in /build (#3326)Sourced from c8's releases.
v10.1.2
10.1.2 (2024-06-13)
Bug Fixes
- deps: make monocart-coverage-reports an optional with meta defined (3b91fda)
v10.1.1
10.1.1 (2024-06-11)
Bug Fixes
v10.1.0
10.1.0 (2024-06-11)
Features
v10.0.0
10.0.0 (2024-06-10)
⚠ BREAKING CHANGES
- deps: Node 18 is now the minimum supported Node.js version
Bug Fixes
Sourced from c8's changelog.
10.1.2 (2024-06-13)
Bug Fixes
- deps: make monocart-coverage-reports an optional with meta defined (3b91fda)
10.1.1 (2024-06-11)
Bug Fixes
10.1.0 (2024-06-11)
Features
10.0.0 (2024-06-10)
⚠ BREAKING CHANGES
- deps: Node 18 is now the minimum supported Node.js version
Bug Fixes
ff146b4
chore(main): release 10.1.2 (#538)3b91fda
fix(deps): make monocart-coverage-reports an optional with meta
definede3560e1
chore(main): release 10.1.1 (#536)13979a7
fix: stop installing monocart-coverage-reports (#535)15ac690
chore(main): release 10.1.0 (#533)96e869f
build(deps-dev): bump braces from 3.0.2 to 3.0.3 (#534)2e5e297
feat: add experimental monocart reports (#521)dc38051
chore(main): release 10.0.0 (#532)e33cf30
fix(deps)!: update test-exclude with new glob / minimatch (#531)1eeeaeb
doc(CONTRIBUTING): remove dead link, update broken link (#526)Sourced from esbuild's releases.
v0.22.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
esbuildin yourpackage.jsonfile (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.21.0or~0.21.0. See npm's documentation about semver for more information.
Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)
This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for
--platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use--packages=externalto work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.With this release, esbuild will now omit packages from the bundle by default when the platform is
node(i.e. the previous behavior of--packages=externalis now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do--packages=bundleto allow packages to be included in the bundle (i.e. the previous default behavior). Note that--packages=bundledoesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using--external:even when--packages=bundleis present.The
--packages=setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of/or.or..are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a#character) and TypeScript path remappings viapathsand/orbaseUrlintsconfig.json(which are applied first).Drop support for older platforms (#3802)
This release drops support for the following operating systems:
- Windows 7
- Windows 8
- Windows Server 2008
- Windows Server 2012
This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.
Note that this only affects the binary esbuild executables that are published to the
esbuildnpm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:git clone https://github.com/evanw/esbuild.git cd esbuild go build ./cmd/esbuild ./esbuild.exe --versionIn addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the
esbuild-wasmpackage and versions of node before node 17.4 (specifically thecrypto.getRandomValuesfunction).Update
await usingbehavior to match TypeScriptTypeScript 5.5 subtly changes the way
await usingbehaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.Allow
es2024as a target environmentThe ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression
/vflag. With--target=es2024, regular expressions that use the/vflag will now be passed through untransformed instead of being transformed into a call tonew RegExp.Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)
With this release, you should now be able to install the
esbuildnpm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.This was contributed by
@ikmckenz.Publish binaries for WASI (WebAssembly System Interface) preview 1 (#3300, #3779)
The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a
.wasmfile without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).
... (truncated)
Sourced from esbuild's changelog.
0.22.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
esbuildin yourpackage.jsonfile (recommended) or be using a version range syntax that only accepts patch upgrades such as^0.21.0or~0.21.0. See npm's documentation about semver for more information.
Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)
This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for
--platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use--packages=externalto work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.With this release, esbuild will now omit packages from the bundle by default when the platform is
node(i.e. the previous behavior of--packages=externalis now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do--packages=bundleto allow packages to be included in the bundle (i.e. the previous default behavior). Note that--packages=bundledoesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using--external:even when--packages=bundleis present.The
--packages=setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of/or.or..are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a#character) and TypeScript path remappings viapathsand/orbaseUrlintsconfig.json(which are applied first).Drop support for older platforms (#3802)
This release drops support for the following operating systems:
- Windows 7
- Windows 8
- Windows Server 2008
- Windows Server 2012
This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.
Note that this only affects the binary esbuild executables that are published to the
esbuildnpm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.21). That might look something like this:git clone https://github.com/evanw/esbuild.git cd esbuild go build ./cmd/esbuild ./esbuild.exe --versionIn addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the
esbuild-wasmpackage and versions of node before node 17.4 (specifically thecrypto.getRandomValuesfunction).Update
await usingbehavior to match TypeScriptTypeScript 5.5 subtly changes the way
await usingbehaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.Allow
es2024as a target environmentThe ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression
/vflag. With--target=es2024, regular expressions that use the/vflag will now be passed through untransformed instead of being transformed into a call tonew RegExp.Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)
With this release, you should now be able to install the
esbuildnpm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.This was contributed by
@ikmckenz.Publish binaries for WASI (WebAssembly System Interface) preview 1 (#3300, #3779)
... (truncated)
80c6e6e
publish 0.22.0 to npm196dcad
fix #1874:
node defaults to --packages=external3f57db8
release notes for #353991663db
Provide API to create a custom esbuild CLI with plugins (#3539)e01c0e0
also mention #3665
in release notes65711b3
release notes for #367463eb814
Add OpenBSD arm64 (#3674)b722000
fix #3300,
fix #3779:
add @esbuild/wasi-preview16679ec8
fix: verbose analyse output improperly trimmed (#3785)94f09ea
fix #3790:
warn about incorrect onResolve pluginSourced from execa's releases.
v9.3.0
Features
- The
verboseoption can now be a function to customize logging. (#1130)v9.2.0
This release includes a new set of methods to exchange messages between the current process and a Node.js subprocess, also known as "IPC". This allows passing and returning almost any message type to/from a Node.js subprocess. Also, debugging IPC is now much easier.
Moreover, a new
gracefulCanceloption has also been added to terminate a subprocess gracefully.For a deeper dive-in, please check and share the release post!
Thanks
@iirojfor your contribution,@SimonSiefkeand@adymorzfor reporting the bugs fixed in this release, and@karlhorkyfor improving the documentation!Deprecations
- Passing
'ipc'to thestdiooption has been deprecated. It will be removed in the next major release. Instead, theipc: trueoption should be used. (#1056)- await execa('npm', ['run', 'build'], {stdio: ['pipe', 'pipe', 'pipe', 'ipc']}); + await execa('npm', ['run', 'build'], {ipc: true});
- The
execaCommand()method has been deprecated. It will be removed in the next major release. If most cases, the template string syntax should be used instead.- import {execaCommand} from 'execa'; + import {execa} from 'execa';
- await execaCommand('npm run build');
- await execa
npm run build;const taskName = 'build';
- await execaCommand(
npm run ${taskName});
- await execa
npm run ${taskName};const commandArguments = ['run', 'task with space']; await execa
npm ${commandArguments};If the file and/or multiple arguments are supplied as a single string, parseCommandString(command) can split that string into an array. More info. (#1054)
- import {execaCommand} from 'execa'; + import {execa, parseCommandString} from 'execa';const commandString = 'npm run task';
- await execaCommand(commandString);
- const commandArray = parseCommandString(commandString); // ['npm', 'run', 'task']
- await execa
${commandArray}; </tr></table>
... (truncated)
57658b0
9.3.08daf348
Allow verbose option to be a function for custom logging
(#1130)78edcb9
Fix c8 memory crash (#1129)18d320f
Refactor test helpers for the verbose option (#1128)37e0024
Add more tests for the verbose option (#1127)f9f1199
Refactor verbose logic (#1126)cbe805c
9.2.08ae6975
Send fewer requests with link checking (#1122)e15e516
Fix typo in IPC documentation (#1121)4044152
Automatically check Markdown links (#1120)Sourced from yaml's releases.
v2.4.5
v2.4.4
With special thanks to
@RedCMDfor finding and reporting all of the following:
- Allow comment after top-level block scalar with explicit indent indicator (#547)
- Allow tab as indent for line comments before nodes (#548)
- Do not allow tab before block collection (#549)
- In flow collections, allow
[]{}immediately after:with plain key (#550)- Require indentation for
?explicit-key contents (#551)- Require indentation from block scalar header & flow collections in mapping values (#553)
v2.4.3
1b8fde6
2.4.5f3c7d03
test: Obey yaml-test-suite skip instructions4e66d72
fix: Improve tab handling (tests DK95 & Y79Y, #553)d06f386
2.4.439053e8
chore: Satisfy strict TS8baee44
test: Use source files for yaml-test-suite tests280a861
fix: Allow comment after top-level block scalar with explicit indent
indicato...767bc47
fix: Require indentation from block scalar header & flow collections
in mappi...5096f83
fix: Require indentation for ? explicit-key contents (fixes #551)22f2c6f
fix: In flow collections, allow []{} immediately after : with plain key
(fixe...