Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump the npm-development-dependencies group with 2 updates #392

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 18, 2024

Bumps the npm-development-dependencies group with 2 updates: @yao-pkg/pkg and esbuild.

Updates @yao-pkg/pkg from 5.11.4 to 5.11.5

Release notes

Sourced from @​yao-pkg/pkg's releases.

Release 5.11.5

5.11.5 (2024-03-13)

Bug Fixes

  • add dictionary for thread-stream (Used by pino) (#36) (b01d1ad)
  • dictionary for sqlite3 (#40) (a3b18f8)
  • pass --runtime napi to prebuild-install when binary.napi_versions is set (#38) (d47ee03)

Chores

  • add update dep workflow (12d1872)
  • fix workflow permissions (c279732)
Changelog

Sourced from @​yao-pkg/pkg's changelog.

5.11.5 (2024-03-13)

Bug Fixes

  • add dictionary for thread-stream (Used by pino) (#36) (b01d1ad)
  • dictionary for sqlite3 (#40) (a3b18f8)
  • pass --runtime napi to prebuild-install when binary.napi_versions is set (#38) (d47ee03)

Chores

  • add update dep workflow (12d1872)
  • fix workflow permissions (c279732)
Commits
  • 42fd35e Release 5.11.5
  • b01d1ad fix: add dictionary for thread-stream (Used by pino) (#36)
  • d47ee03 fix: pass --runtime napi to prebuild-install when binary.napi_versions ...
  • a3b18f8 fix: dictionary for sqlite3 (#40)
  • c279732 chore: fix workflow permissions
  • 12d1872 chore: add update dep workflow
  • See full diff in compare view

Updates esbuild from 0.20.1 to 0.20.2

Release notes

Sourced from esbuild's releases.

v0.20.2

  • Support TypeScript experimental decorators on abstract class fields (#3684)

    With this release, you can now use TypeScript experimental decorators on abstract class fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:

    // Original code
    const log = (x: any, y: string) => console.log(y)
    abstract class Foo { @log abstract foo: string }
    new class extends Foo { foo = '' }
    // Old output (with --loader=ts --tsconfig-raw={"compilerOptions":{"experimentalDecorators":true}})
    const log = (x, y) => console.log(y);
    class Foo {
    }
    new class extends Foo {
    foo = "";
    }();
    // New output (with --loader=ts --tsconfig-raw={"compilerOptions":{"experimentalDecorators":true}})
    const log = (x, y) => console.log(y);
    class Foo {
    }
    __decorateClass([
    log
    ], Foo.prototype, "foo", 2);
    new class extends Foo {
    foo = "";
    }();

  • JSON loader now preserves __proto__ properties (#3700)

    Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the __proto__ key. A literal __proto__ property in a JavaScript object literal sets the prototype of the object instead of adding a property named __proto__, while a literal __proto__ property in a JSON object literal just adds a property named __proto__. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:

    // Original code
    import data from 'data:application/json,{"__proto__":{"fail":true}}'
    if (Object.getPrototypeOf(data)?.fail) throw 'fail'
    // Old output (with --bundle)
    (() => {
    // <data:application/json,{"proto":{"fail":true}}>
    var json_proto_fail_true_default = { proto: { fail: true } };
    // entry.js
    if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
    throw "fail";
    })();

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.20.2

  • Support TypeScript experimental decorators on abstract class fields (#3684)

    With this release, you can now use TypeScript experimental decorators on abstract class fields. This was silently compiled incorrectly in esbuild 0.19.7 and below, and was an error from esbuild 0.19.8 to esbuild 0.20.1. Code such as the following should now work correctly:

    // Original code
    const log = (x: any, y: string) => console.log(y)
    abstract class Foo { @log abstract foo: string }
    new class extends Foo { foo = '' }
    // Old output (with --loader=ts --tsconfig-raw={&quot;compilerOptions&quot;:{&quot;experimentalDecorators&quot;:true}})
    const log = (x, y) => console.log(y);
    class Foo {
    }
    new class extends Foo {
    foo = "";
    }();
    // New output (with --loader=ts --tsconfig-raw={&quot;compilerOptions&quot;:{&quot;experimentalDecorators&quot;:true}})
    const log = (x, y) => console.log(y);
    class Foo {
    }
    __decorateClass([
    log
    ], Foo.prototype, "foo", 2);
    new class extends Foo {
    foo = "";
    }();

  • JSON loader now preserves __proto__ properties (#3700)

    Copying JSON source code into a JavaScript file will change its meaning if a JSON object contains the __proto__ key. A literal __proto__ property in a JavaScript object literal sets the prototype of the object instead of adding a property named __proto__, while a literal __proto__ property in a JSON object literal just adds a property named __proto__. With this release, esbuild will now work around this problem by converting JSON to JavaScript with a computed property key in this case:

    // Original code
    import data from 'data:application/json,{"__proto__":{"fail":true}}'
    if (Object.getPrototypeOf(data)?.fail) throw 'fail'
    // Old output (with --bundle)
    (() => {
    // <data:application/json,{"proto":{"fail":true}}>
    var json_proto_fail_true_default = { proto: { fail: true } };
    // entry.js
    if (Object.getPrototypeOf(json_proto_fail_true_default)?.fail)
    throw "fail";
    })();

... (truncated)

Commits

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 npm-development-dependencies group with 2 updates: [@yao-pkg/pkg](https://github.com/yao-pkg/pkg) and [esbuild](https://github.com/evanw/esbuild).


Updates `@yao-pkg/pkg` from 5.11.4 to 5.11.5
- [Release notes](https://github.com/yao-pkg/pkg/releases)
- [Changelog](https://github.com/yao-pkg/pkg/blob/main/CHANGELOG.md)
- [Commits](yao-pkg/pkg@v5.11.4...v5.11.5)

Updates `esbuild` from 0.20.1 to 0.20.2
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.20.1...v0.20.2)

---
updated-dependencies:
- dependency-name: "@yao-pkg/pkg"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-development-dependencies
- dependency-name: esbuild
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-development-dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Mar 18, 2024
@hectorm hectorm merged commit cccde17 into master Mar 20, 2024
15 checks passed
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/npm-development-dependencies-4e4b101edc branch March 20, 2024 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant