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 #21525

Merged
merged 1 commit into from
Aug 9, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 7, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
core-js 3.16.0 -> 3.16.1 age adoption passing confidence
esbuild 0.12.18 -> 0.12.19 age adoption passing confidence
eslint-plugin-import 2.23.4 -> 2.24.0 age adoption passing confidence
webpack 5.48.0 -> 5.49.0 age adoption passing confidence

Release Notes

zloirock/core-js

v3.16.1

Compare Source

  • Fixed microtask implementation on iOS Pebble, #​967
  • Fixed some entry points
  • Improved old Safari compat data
evanw/esbuild

v0.12.19

Compare Source

  • Add support for CSS source maps (#​519)

    With this release, esbuild will now generate source maps for CSS output files when --sourcemap is enabled. This supports all of the same options as JS source maps including --sourcemap=inline and --sourcemap=external. In addition, CSS input files with embedded /*# sourceMappingURL=... */ comments will cause the CSS output file source map to map all the way back to the original inputs. CSS source maps are used by the browser's style inspector to link back to the original source code instead of linking to the bundled source code.

  • Fix computed class fields in TypeScript edge case (#​1507)

    If TypeScript code contains computed class fields, the target environment supports class fields so syntax lowering is not necessary, and TypeScript's useDefineForClassFields setting is set to true, then esbuild had a bug where the computed property names were computed after the class definition and were undefined. Note that TypeScript's useDefineForClassFields setting defaults to true if tsconfig.json contains "target": "ESNext".

    // Original code
    class Foo {
      [foo] = 1;
      @​bar [baz] = 2;
    }
    
    // Old output
    var _a, _b;
    var Foo = class {
      [_a] = 1;
      [_b] = 2;
    };
    _a = foo, _b = baz;
    __decorateClass([
      bar
    ], Foo.prototype, _b, 2);
    
    // New output
    var _a;
    var Foo = class {
      [foo] = 1;
      [_a = baz] = 2;
    };
    __decorateClass([
      bar
    ], Foo.prototype, _a, 2);

    The problem in this case is that normally TypeScript moves class field initializers into the special constructor method (automatically generating one if one doesn't already exist) so the side effects for class field property names must happen after the class body. But if class fields are supported by the target environment then the side effects must happen inline instead.

import-js/eslint-plugin-import

v2.24.0

Compare Source

Added
Fixed
  • [no-duplicates]: ensure autofix avoids excessive newlines ([#​2028], thanks [@​ertrzyiks])
  • [extensions]: avoid crashing on partially typed import/export statements ([#​2118], thanks [@​ljharb])
  • [no-extraneous-dependencies]: add ESM intermediate package.json support] ([#​2121], thanks [@​paztis])
  • Use context.getPhysicalFilename() when available (ESLint 7.28+) ([#​2160], thanks [@​pmcelhaney])
  • [extensions]/importType: fix isScoped treating @​/abc as scoped module ([#​2146], thanks [@​rperello])
Changed
webpack/webpack

v5.49.0

Compare Source

Features

  • add experiments.buildHttp to build http(s):// imports instead of keeping them external
    • keeps a webpack.lock file with integrity and webpack.lock.data with cached content that should be committed
    • Automatically upgrades lockfile during development when remote resources change
      (might be disabled with experiments.buildHttp.upgrade: false)
    • Lockfile is frozen during production builds and usually no network requests are made
      (exception: Cache-Control: no-cache).
    • The webpack.lock.data persisting can be disabled with experiments.buildHttp.cacheLocation: false.
      That will will introduce a availability risk.
      (webpack cache will be used to cache network responses)

Bugfixes

  • fix HMR infinite loop (again)
  • fix rare non-determinism with splitChunks.maxSize introduces in the last release
  • optional modules no longer cause the module to fail when bail is set
  • fix typo in records format: chunkHashs -> chunkHashes

Performance

  • limit the number of parallel generated chunks for memory reasons

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: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 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 Aug 7, 2021
@google-cla google-cla bot added the cla: yes label Aug 7, 2021
@renovate renovate bot changed the title build: update dependency webpack to v5.49.0 build: update all non-major dependencies Aug 7, 2021
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 33116ae to d604480 Compare August 8, 2021 18:07
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d604480 to 19124d5 Compare August 8, 2021 23:07
@alan-agius4 alan-agius4 merged commit 7098d65 into master Aug 9, 2021
@renovate renovate bot deleted the renovate/all-minor-patch branch August 9, 2021 09:31
@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 Sep 9, 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: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants