build(deps-dev): bump the development-dependencies group with 4 updates #150

dependabot · 2024-07-01T10:17:40Z

Bumps the development-dependencies group with 4 updates: c8, esbuild, execa and yaml.

Updates c8 from 9.1.0 to 10.1.2

Release notes

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

stop installing monocart-coverage-reports (#535) (13979a7)

v10.1.0

10.1.0 (2024-06-11)

Features

add experimental monocart reports (#521) (2e5e297)

v10.0.0

10.0.0 (2024-06-10)

⚠ BREAKING CHANGES

deps: Node 18 is now the minimum supported Node.js version

Bug Fixes

deps: update test-exclude with new glob / minimatch (#531) (e33cf30)

Changelog

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

stop installing monocart-coverage-reports (#535) (13979a7)

10.1.0 (2024-06-11)

Features

add experimental monocart reports (#521) (2e5e297)

10.0.0 (2024-06-10)

⚠ BREAKING CHANGES

deps: Node 18 is now the minimum supported Node.js version

Bug Fixes

deps: update test-exclude with new glob / minimatch (#531) (e33cf30)

Commits

ff146b4 chore(main): release 10.1.2 (#538)
3b91fda fix(deps): make monocart-coverage-reports an optional with meta defined
e3560e1 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)
Additional commits viewable in compare view

Updates esbuild from 0.21.4 to 0.22.0

Release notes

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 esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~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=external to 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=external is 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=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn'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=bundle is 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 via paths and/or baseUrl in tsconfig.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 esbuild npm 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 --version
In 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-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).
Update await using behavior to match TypeScript

TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.

Allow es2024 as a target environment

The 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 /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.

Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)

With this release, you should now be able to install the esbuild npm 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 .wasm file 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)

Changelog

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 esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~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=external to 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=external is 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=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn'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=bundle is 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 via paths and/or baseUrl in tsconfig.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 esbuild npm 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 --version
In 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-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).
Update await using behavior to match TypeScript

TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.

Allow es2024 as a target environment

The 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 /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.

Publish binaries for OpenBSD on 64-bit ARM (#3665, #3674)

With this release, you should now be able to install the esbuild npm 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)

Commits

80c6e6e publish 0.22.0 to npm
196dcad fix #1874: node defaults to --packages=external
3f57db8 release notes for #3539
91663db Provide API to create a custom esbuild CLI with plugins (#3539)
e01c0e0 also mention #3665 in release notes
65711b3 release notes for #3674
63eb814 Add OpenBSD arm64 (#3674)
b722000 fix #3300, fix #3779: add @esbuild/wasi-preview1
6679ec8 fix: verbose analyse output improperly trimmed (#3785)
94f09ea fix #3790: warn about incorrect onResolve plugin
Additional commits viewable in compare view

Updates execa from 9.1.0 to 9.3.0

Release notes

Sourced from execa's releases.

v9.3.0

Features

The verbose option 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 gracefulCancel option has also been added to terminate a subprocess gracefully.

For a deeper dive-in, please check and share the release post!

Thanks @iiroj for your contribution, @SimonSiefke and @adymorz for reporting the bugs fixed in this release, and @karlhorky for improving the documentation!

Deprecations

Passing 'ipc' to the stdio option has been deprecated. It will be removed in the next major release. Instead, the ipc: true option 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 execanpm run build;

const taskName = 'build';

await execaCommand(npm run ${taskName});


await execanpm run ${taskName};

const commandArguments = ['run', 'task with space'];
await execanpm ${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)

Commits

57658b0 9.3.0
8daf348 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.0
8ae6975 Send fewer requests with link checking (#1122)
e15e516 Fix typo in IPC documentation (#1121)
4044152 Automatically check Markdown links (#1120)
Additional commits viewable in compare view

Updates yaml from 2.4.2 to 2.4.5

Release notes

Sourced from yaml's releases.

v2.4.5

Improve tab handling (#553, yaml-test-suite tests DK95 & Y79Y)

v2.4.4

With special thanks to @RedCMD for 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

Improve error when parsing a non-string value (#459)

Do not parse -.NaN or +.nan as NaN (#546)

Support # within %TAG prefixes with trailing #comments

Check for non-node complex keys when stringifying with simpleKeys (#541)

Commits

1b8fde6 2.4.5
f3c7d03 test: Obey yaml-test-suite skip instructions
4e66d72 fix: Improve tab handling (tests DK95 & Y79Y, #553)
d06f386 2.4.4
39053e8 chore: Satisfy strict TS
8baee44 test: Use source files for yaml-test-suite tests
280a861 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...
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the development-dependencies group with 4 updates: [c8](https://github.com/bcoe/c8), [esbuild](https://github.com/evanw/esbuild), [execa](https://github.com/sindresorhus/execa) and [yaml](https://github.com/eemeli/yaml). Updates `c8` from 9.1.0 to 10.1.2 - [Release notes](https://github.com/bcoe/c8/releases) - [Changelog](https://github.com/bcoe/c8/blob/main/CHANGELOG.md) - [Commits](bcoe/c8@v9.1.0...v10.1.2) Updates `esbuild` from 0.21.4 to 0.22.0 - [Release notes](https://github.com/evanw/esbuild/releases) - [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md) - [Commits](evanw/esbuild@v0.21.4...v0.22.0) Updates `execa` from 9.1.0 to 9.3.0 - [Release notes](https://github.com/sindresorhus/execa/releases) - [Commits](sindresorhus/execa@v9.1.0...v9.3.0) Updates `yaml` from 2.4.2 to 2.4.5 - [Release notes](https://github.com/eemeli/yaml/releases) - [Commits](eemeli/yaml@v2.4.2...v2.4.5) --- updated-dependencies: - dependency-name: c8 dependency-type: direct:development update-type: version-update:semver-major dependency-group: development-dependencies - dependency-name: esbuild dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development-dependencies - dependency-name: execa dependency-type: direct:development update-type: version-update:semver-minor dependency-group: development-dependencies - dependency-name: yaml dependency-type: direct:development update-type: version-update:semver-patch dependency-group: development-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>

…://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md\#0220

…cies-39087a2ce8

create-app-token-action-releaser · 2024-09-04T04:41:30Z

🎉 This PR is included in version 1.10.4 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

dependabot bot requested a review from gr2m as a code owner July 1, 2024 10:17

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jul 1, 2024

dependabot bot requested review from parkerbxyz and a team as code owners July 1, 2024 10:17

gr2m added 5 commits July 1, 2024 10:47

use js extension for dist files

4f0a116

build: explicitly bundle packages with --platform=node as per https…

2cfcf40

…://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md\#0220

Merge branch 'main' into dependabot/npm_and_yarn/development-dependen…

025806f

…cies-39087a2ce8

back to CJS 🤷

a0a8bd4

oops

54313ce

gr2m approved these changes Jul 1, 2024

View reviewed changes

gr2m merged commit 040c259 into main Jul 1, 2024
4 checks passed

gr2m deleted the dependabot/npm_and_yarn/development-dependencies-39087a2ce8 branch July 1, 2024 19:02

create-app-token-action-releaser bot added the released label Sep 4, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

build(deps-dev): bump the development-dependencies group with 4 updates #150

build(deps-dev): bump the development-dependencies group with 4 updates #150

dependabot bot commented on behalf of github Jul 1, 2024 •

edited

Loading

create-app-token-action-releaser bot commented Sep 4, 2024

build(deps-dev): bump the development-dependencies group with 4 updates #150

build(deps-dev): bump the development-dependencies group with 4 updates #150

Conversation

dependabot bot commented on behalf of github Jul 1, 2024 • edited Loading

v10.1.2

10.1.2 (2024-06-13)

Bug Fixes

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

Bug Fixes

10.1.2 (2024-06-13)

Bug Fixes

10.1.1 (2024-06-11)

Bug Fixes

10.1.0 (2024-06-11)

Features

10.0.0 (2024-06-10)

⚠ BREAKING CHANGES

Bug Fixes

v0.22.0

0.22.0

v9.3.0

Features

v9.2.0

Deprecations

v2.4.5

v2.4.4

v2.4.3

create-app-token-action-releaser bot commented Sep 4, 2024

dependabot bot commented on behalf of github Jul 1, 2024 •

edited

Loading