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

build: update all non-major dependencies #21949

Merged
merged 2 commits into from
Oct 14, 2021
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 14, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
build_bazel_rules_nodejs http_archive patch 4.4.0 -> 4.4.1
esbuild optionalDependencies patch 0.13.5 -> 0.13.6
esbuild devDependencies patch 0.13.5 -> 0.13.6
esbuild-wasm dependencies patch 0.13.5 -> 0.13.6
esbuild-wasm devDependencies patch 0.13.5 -> 0.13.6
eslint (source) devDependencies patch 8.0.0 -> 8.0.1
jasmine (source) devDependencies minor ~3.9.0 -> ~3.10.0
jasmine-core (source) dependencies minor ~3.9.0 -> ~3.10.0
jasmine-core (source) devDependencies minor ~3.9.0 -> ~3.10.0
postcss-loader dependencies minor 6.1.1 -> 6.2.0
postcss-loader devDependencies minor 6.1.1 -> 6.2.0
sass dependencies minor 1.42.1 -> 1.43.2
sass devDependencies minor 1.42.1 -> 1.43.2
webpack devDependencies patch 5.58.1 -> 5.58.2
webpack dependencies patch 5.58.1 -> 5.58.2
webpack resolutions patch 5.58.1 -> 5.58.2

Release Notes

bazelbuild/rules_nodejs

v4.4.1

Compare Source

Bug Fixes
  • terser semver compatibility range (c7439a0)
evanw/esbuild

v0.13.6

Compare Source

  • Emit decorators for declare class fields (#​1675)

    In version 3.7, TypeScript introduced the declare keyword for class fields that avoids generating any code for that field:

    // TypeScript input
    class Foo {
      a: number
      declare b: number
    }
    
    // JavaScript output
    class Foo {
      a;
    }

    However, it turns out that TypeScript still emits decorators for these omitted fields. With this release, esbuild will now do this too:

    // TypeScript input
    class Foo {
      @​decorator a: number;
      @​decorator declare b: number;
    }
    
    // Old JavaScript output
    class Foo {
      a;
    }
    __decorateClass([
      decorator
    ], Foo.prototype, "a", 2);
    
    // New JavaScript output
    class Foo {
      a;
    }
    __decorateClass([
      decorator
    ], Foo.prototype, "a", 2);
    __decorateClass([
      decorator
    ], Foo.prototype, "b", 2);
  • Experimental support for esbuild on NetBSD (#​1624)

    With this release, esbuild now has a published binary executable for NetBSD in the esbuild-netbsd-64 npm package, and esbuild's installer has been modified to attempt to use it when on NetBSD. Hopefully this makes installing esbuild via npm work on NetBSD. This change was contributed by @​gdt.

    ⚠️ Note: NetBSD is not one of Node's supported platforms, so installing esbuild may or may not work on NetBSD depending on how Node has been patched. This is not a problem with esbuild. ⚠️

  • Disable the "esbuild was bundled" warning if ESBUILD_BINARY_PATH is provided (#​1678)

    The ESBUILD_BINARY_PATH environment variable allows you to substitute an alternate binary executable for esbuild's JavaScript API. This is useful in certain cases such as when debugging esbuild. The JavaScript API has some code that throws an error if it detects that it was bundled before being run, since bundling prevents esbuild from being able to find the path to its binary executable. However, that error is unnecessary if ESBUILD_BINARY_PATH is present because an alternate path has been provided. This release disables the warning when ESBUILD_BINARY_PATH is present so that esbuild can be used when bundled as long as you also manually specify ESBUILD_BINARY_PATH.

    This change was contributed by @​heypiotr.

  • Remove unused catch bindings when minifying (#​1660)

    With this release, esbuild will now remove unused catch bindings when minifying:

    // Original code
    try {
      throw 0;
    } catch (e) {
    }
    
    // Old output (with --minify)
    try{throw 0}catch(t){}
    
    // New output (with --minify)
    try{throw 0}catch{}

    This takes advantage of the new optional catch binding syntax feature that was introduced in ES2019. This minification rule is only enabled when optional catch bindings are supported by the target environment. Specifically, it's not enabled when using --target=es2018 or older. Make sure to set esbuild's target setting correctly when minifying if the code will be running in an older JavaScript environment.

    This change was contributed by @​sapphi-red.

eslint/eslint

v8.0.1

Compare Source

jasmine/jasmine-npm

v3.10.0

Compare Source

Please see the release notes.

jasmine/jasmine

v3.10.0

Compare Source

Please see the release notes.

webpack-contrib/postcss-loader

v6.2.0

Compare Source

Features
6.1.1 (2021-07-01)
Bug Fixes
  • do not swallow exception from postcss (2eec42b)
sass/dart-sass

v1.43.2

Compare Source

  • Improve the error message when the default namespace of a @use rule is not
    a valid identifier.
webpack/webpack

v5.58.2

Compare Source

Bugfixes

  • fix serialization context passed
  • fix a bug which caused module duplication when using persistent caching, unsafe cache and memory cache with GC
  • fix validation of snapshots of non-existing directories

Performance


Configuration

📅 Schedule: "after 10pm every weekday,before 4am every weekday,every weekend" in timezone America/Tijuana.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box.

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

@renovate renovate bot added action: merge The PR is ready for merge by the caretaker target: minor This PR is targeted for the next minor release labels Oct 14, 2021
@google-cla google-cla bot added the cla: yes label Oct 14, 2021
@alan-agius4 alan-agius4 added target: rc This PR is targeted for the next release-candidate and removed target: minor This PR is targeted for the next minor release labels Oct 14, 2021
This forces a single Webpack version to be available, as otherwise types will be incompatible.
@google-cla
Copy link

google-cla bot commented Oct 14, 2021

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added cla: no and removed cla: yes labels Oct 14, 2021
@alan-agius4
Copy link
Collaborator

@googlebot I consent.

@google-cla google-cla bot added cla: yes and removed cla: no labels Oct 14, 2021
@clydin clydin merged commit 37b4704 into master Oct 14, 2021
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Nov 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants