build: update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@babel/core (source)	7.16.5 -> 7.16.7
@babel/generator (source)	7.16.5 -> 7.16.7
@babel/helper-annotate-as-pure (source)	7.16.0 -> 7.16.7
@babel/plugin-proposal-async-generator-functions (source)	7.16.5 -> 7.16.7
@babel/plugin-transform-async-to-generator (source)	7.16.5 -> 7.16.7
@babel/plugin-transform-runtime (source)	7.16.5 -> 7.16.7
@babel/preset-env (source)	7.16.5 -> 7.16.7
@babel/runtime (source)	7.16.5 -> 7.16.7
@babel/template (source)	7.16.0 -> 7.16.7
@bazel/jasmine	4.4.6 -> 4.6.0
@bazel/typescript	4.4.6 -> 4.6.0
@types/babel__core	7.1.17 -> 7.1.18
@typescript-eslint/eslint-plugin	5.7.0 -> 5.9.1
@typescript-eslint/parser	5.7.0 -> 5.9.1
build_bazel_rules_nodejs	4.4.6 -> 4.6.0
core-js	3.20.0 -> 3.20.2
esbuild	0.14.5 -> 0.14.11
esbuild-wasm	0.14.5 -> 0.14.11
eslint (source)	8.4.1 -> 8.6.0
eslint-plugin-import	2.25.3 -> 2.25.4
mini-css-extract-plugin	2.4.5 -> 2.4.6
puppeteer	13.0.0 -> 13.0.1
resolve	1.20.0 -> 1.21.0
rxjs (source)	~7.4.0 -> ~7.5.0
sass	1.45.0 -> 1.47.0
source-map-loader	3.0.0 -> 3.0.1
stylus	0.55.0 -> 0.56.0
verdaccio (source)	5.3.2 -> 5.4.0
webpack-dev-server	4.6.0 -> 4.7.2

---

Release Notes

babel/babel

v7.16.7

Compare Source

👓 Spec Compliance

• babel-parser
  • #​14049 fix: check preceding line break before exclamation (@​JLHwung)

🐛 Bug Fix

• babel-plugin-transform-runtime, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
  • #​14081 Import the correct ./typeof.js helper in @babel/runtime (@​exb)
• babel-helpers
  • #​14072 Fix derived classes in Chrome <= 36 (@​nicolo-ribaudo)
• babel-helper-function-name, babel-plugin-transform-function-name
  • #​14047 Fix unicode handling in generated function names (@​The-x-Theorist)

💅 Polish

• babel-core
  • #​14067 Allow $schema property in json config files (@​The-x-Theorist)

bazelbuild/rules_nodejs

v4.6.0

Compare Source

Bug Fixes

• builtin: js_library: propagate all default_runfiles (#​3183) (d9f3500), closes #​3182
• typescript: ts_project transpiler produces js_library (#​3187) (f593e06)
• bump jasmine-reporters to 2.5.0 (#​3180) (5ac6852)

Features

• typescript: allow alternative transpilers (#​3134) (dc0dc8f), closes #​3133

4.5.1 (2021-12-16)

v4.5.0

Compare Source

Bug Fixes

• allow cypress to run on m1 macs (#​3088) (c1778f4)
• builtin: support mjs/cjs files as javascript files in js_library (2b4e903)
• esbuild: do not ignore annotations when the minify shorthand attribute is disabled (#​3106) (af70835)
• esbuild: format attribute not working with multiple entry points (#​3103) (8d7b542)
• don't symlink execroot node_modules when under bazel run (f72e956)
• unset INIT_CWD and npm_config_registry before calling yarn in yarn_install (653600d)

Features

• esbuild: make Starlark build settings usable as defines (#​3122) (e47f339)
• add bzlmod extension (#​3146) (ed23145)

4.4.6 (2021-11-23)

Bug Fixes

• add arm64 as a platform to //packages/concatjs:docs_scrub_platform (#​3089) (bc2803a)
• normalize module path passed to runfiles helper for robustness (#​3094) (3c44f51)
• remove trailing forward slash when resolving workspace root link in runfiles MANIFEST (#​3093) (6af7317)
• update tsconfigs to include darwin_arm64-fastbuild in rootDirs (#​3087) (104420b)
• builtin: don't use local:1 spawn (#​3084) (f886b82)

4.4.5 (2021-11-11)

Bug Fixes

• builtin: handle external repository file paths in js_library strip_prefix check (c6ba226)
• builtin: provide a DeclarationInfo from js_library is any input files are directories (TreeArtifacts) (0b247c3)
• typescript: don't set resolveJsonModule in generated tsconfig if tsconfig is dict and resolve_json_module is unset (e026387)

Features

• esbuild: add option to disable metafile generation (#​3066) (2960f54)

4.4.4 (2021-11-08)

Bug Fixes

• builtin: fixed missing dist targets (#​3068) (c30a26c)
• esbuild: allow passing additional args to the npm install for esbuild (#​3063) (31d5094)

4.4.3 (2021-11-04)

Bug Fixes

• #​3054 regression in linker behavior in 4.4.2 (#​3059) (ccf54bc)
• correct bzl_library target graph (#​3049) (5ac721a)
• don't link runfiles node_modules to execroot node_modules if there is an external workspace node_modules (#​3060) (a76d000)
• typescript: give better error when noEmit is set (#​3047) (eedc065)

4.4.2 (2021-10-28)

Bug Fixes

• builtin: retrieve yarn shasums from Github releases, rather than npm registry (b233b07)
• create: relocate help argument evaluation (f67c584)
• esbuild: allow whitespace within args (#​2998) (3446425), closes #​2997
• examples: run jest updateSnapshot in the workspace (#​3041) (6ee1e52)
• typescript: don't declare outputs that collide with inputs (#​3046) (bd8b7f3)
• simplify portion of linker and fix case where runfiles node_modules symlinks are missing under bazel run (f6db6c9)

4.4.1 (2021-10-13)

Bug Fixes

• terser semver compatibility range (c7439a0)

typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v5.9.1

Compare Source

Note: Version bump only for package @​typescript-eslint/eslint-plugin

v5.9.0

Compare Source

Features

• experimental-utils: move isTypeReadonly from eslint-plugin to experimental-utils (#​3658) (a9eb0b9)

5.8.1 (2021-12-27)

Bug Fixes

• eslint-plugin: [consistent-indexed-object-style] do not report for circular references (#​4347) (6edebcd)
• eslint-plugin: [consistent-type-definitions] correct fixer with declare keyword (#​4334) (0cd911a)
• eslint-plugin: [padding-line-between-statements] make function overloading is also processed (#​4345) (d31ec26)

v5.8.1

Compare Source

Bug Fixes

• eslint-plugin: [consistent-indexed-object-style] do not report for circular references (#​4347) (6edebcd)
• eslint-plugin: [consistent-type-definitions] correct fixer with declare keyword (#​4334) (0cd911a)
• eslint-plugin: [padding-line-between-statements] make function overloading is also processed (#​4345) (d31ec26)

v5.8.0

Compare Source

Bug Fixes

• eslint-plugin: [no-implied-eval] improve performance (#​4313) (e344596)
• eslint-plugin: [padding-line-between-statements] type StatementTypes can't differenciate from variable (#​4270) (bfc4324)
• eslint-plugin: [strict-boolean-expression] false positive for truthy boolean (#​4275) (72c2e41)
• eslint-plugin: array-type mark AST_NODE_TYPES.TSBigIntKeyword as simple (#​4274) (74e544e)
• eslint-plugin: handle method overloading in semi (#​4318) (3b87b49)
• experimental-utils: support immutable members (#​3844) (3d33a77)

Features

• eslint-plugin: [no-throw-literal] add options to to disallow any/unknown (#​4207) (ff0adf9)
• eslint-plugin: [restrict-plus-operand] add allowAny option (#​4260) (2788545)

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v5.9.1

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.9.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

5.8.1 (2021-12-27)

Note: Version bump only for package @​typescript-eslint/parser

v5.8.1

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

v5.8.0

Compare Source

Note: Version bump only for package @​typescript-eslint/parser

zloirock/core-js

v3.20.2

Compare Source

• Added a fix of a V8 ~ Chrome 36- Object.{ defineProperty, defineProperties } bug, Babel issue
• Added fixes of some different %TypedArray%.prototype.set bugs, affects modern engines (like Chrome < 95 or Safari < 14.1)

v3.20.1

Compare Source

• Fixed the order of calling reactions of already fulfilled / rejected promises in Promise.prototype.then, #​1026
• Fixed possible memory leak in specific promise chains
• Fixed some missed dependencies of entries
• Added Deno 1.18 compat data mapping

evanw/esbuild

v0.14.11

Compare Source

• Fix a bug with enum inlining (#​1903)

  The new TypeScript enum inlining behavior had a bug where it worked correctly if you used export enum Foo but not if you used enum Foo and then later export { Foo }. This release fixes the bug so enum inlining now works correctly in this case.

• Warn about module.exports.foo = ... in ESM (#​1907)

  The module variable is treated as a global variable reference instead of as a CommonJS module reference in ESM code, which can cause problems for people that try to use both CommonJS and ESM exports in the same file. There has been a warning about this since version 0.14.9. However, the warning only covered cases like exports.foo = bar and module.exports = bar but not module.exports.foo = bar. This last case is now handled;

  ▲ [WARNING] The CommonJS "module" variable is treated as a global variable in an ECMAScript module and may not work as expected
  
      example.ts:2:0:
        2 │ module.exports.b = 1
          ╵ ~~~~~~
  
    This file is considered to be an ECMAScript module because of the "export" keyword here:
  
      example.ts:1:0:
        1 │ export let a = 1
          ╵ ~~~~~~
  

• Enable esbuild's CLI with Deno (#​1913)

  This release allows you to use Deno as an esbuild installer, without also needing to use esbuild's JavaScript API. You can now use esbuild's CLI with Deno:

  deno run --allow-all "https://deno.land/x/[email protected]/mod.js" --version
  

v0.14.10

Compare Source

• Enable tree shaking of classes with lowered static fields (#​175)

  If the configured target environment doesn't support static class fields, they are converted into a call to esbuild's __publicField function instead. However, esbuild's tree-shaking pass treated this call as a side effect, which meant that all classes with static fields were ineligible for tree shaking. This release fixes the problem by explicitly ignoring calls to the __publicField function during tree shaking side-effect determination. Tree shaking is now enabled for these classes:

  // Original code
  class Foo { static foo = 'foo' }
  class Bar { static bar = 'bar' }
  new Bar()
  
  // Old output (with --tree-shaking=true --target=es6)
  class Foo {
  }
  __publicField(Foo, "foo", "foo");
  class Bar {
  }
  __publicField(Bar, "bar", "bar");
  new Bar();
  
  // New output (with --tree-shaking=true --target=es6)
  class Bar {
  }
  __publicField(Bar, "bar", "bar");
  new Bar();

• Treat --define:foo=undefined as an undefined literal instead of an identifier (#​1407)

  References to the global variable undefined are automatically replaced with the literal value for undefined, which appears as void 0 when printed. This allows for additional optimizations such as collapsing undefined ?? bar into just bar. However, this substitution was not done for values specified via --define:. As a result, esbuild could potentially miss out on certain optimizations in these cases. With this release, it's now possible to use --define: to substitute something with an undefined literal:

  // Original code
  let win = typeof window !== 'undefined' ? window : {}
  
  // Old output (with --define:window=undefined --minify)
  let win=typeof undefined!="undefined"?undefined:{};
  
  // New output (with --define:window=undefined --minify)
  let win={};

• Add the --drop:debugger flag (#​1809)

  Passing this flag causes all debugger; statements to be removed from the output. This is similar to the drop_debugger: true flag available in the popular UglifyJS and Terser JavaScript minifiers.

• Add the --drop:console flag (#​28)

  Passing this flag causes all console.xyz() API calls to be removed from the output. This is similar to the drop_console: true flag available in the popular UglifyJS and Terser JavaScript minifiers.

  WARNING: Using this flag can introduce bugs into your code! This flag removes the entire call expression including all call arguments. If any of those arguments had important side effects, using this flag will change the behavior of your code. Be very careful when using this flag. If you want to remove console API calls without removing arguments with side effects (which does not introduce bugs), you should mark the relevant API calls as pure instead like this: --pure:console.log --minify.

• Inline calls to certain no-op functions when minifying (#​290, #​907)

  This release makes esbuild inline two types of no-op functions: empty functions and identity functions. These most commonly arise when most of the function body is eliminated as dead code. In the examples below, this happens because we use --define:window.DEBUG=false to cause dead code elimination inside the function body of the resulting if (false) statement. This inlining is a small code size and performance win but, more importantly, it allows for people to use these features to add useful abstractions that improve the development experience without needing to worry about the run-time performance impact.

  An identity function is a function that just returns its argument. Here's an example of inlining an identity function:

  // Original code
  function logCalls(fn) {
    if (window.DEBUG) return function(...args) {
      console.log('calling', fn.name, 'with', args)
      return fn.apply(this, args)
    }
    return fn
  }
  export const foo = logCalls(function foo() {})
  
  // Old output (with --minify --define:window.DEBUG=false --tree-shaking=true)
  function o(n){return n}export const foo=o(function(){});
  
  // New output (with --minify --define:window.DEBUG=false --tree-shaking=true)
  export const foo=function(){};

  An empty function is a function with an empty body. Here's an example of inlining an empty function:

  // Original code
  function assertNotNull(val: Object | null): asserts val is Object {
    if (window.DEBUG && val === null) throw new Error('null assertion failed');
  }
  export const val = getFoo();
  assertNotNull(val);
  console.log(val.bar);
  
  // Old output (with --minify --define:window.DEBUG=false --tree-shaking=true)
  function l(o){}export const val=getFoo();l(val);console.log(val.bar);
  
  // New output (with --minify --define:window.DEBUG=false --tree-shaking=true)
  export const val=getFoo();console.log(val.bar);

  To get this behavior you'll need to use the function keyword to define your function since that causes the definition to be hoisted, which eliminates concerns around initialization order. These features also work across modules, so functions are still inlined even if the definition of the function is in a separate module from the call to the function. To get cross-module function inlining to work, you'll need to have bundling enabled and use the import and export keywords to access the function so that esbuild can see which functions are called. And all of this has been added without an observable impact to compile times.

  I previously wasn't able to add this to esbuild easily because of esbuild's low-pass compilation approach. The compiler only does three full passes over the data for speed. The passes are roughly for parsing, binding, and printing. It's only possible to inline something after binding but it needs to be inlined before printing. Also the way module linking was done made it difficult to roll back uses of symbols that were inlined, so the symbol definitions were not tree shaken even when they became unused due to inlining.

  The linking issue was somewhat resolved when I fixed #​128 in the previous release. To implement cross-module inlining of TypeScript enums, I came up with a hack to defer certain symbol uses until the linking phase, which happens after binding but before printing. Another hack is that inlining of TypeScript enums is done directly in the printer to avoid needing another pass.

  The possibility of these two hacks has unblocked these simple function inlining use cases that are now handled. This isn't a fully general approach because optimal inlining is recursive. Inlining something may open up further inlining opportunities, which either requires multiple iterations or a worklist algorithm, both of which don't work when doing late-stage inlining in the printer. But the function inlining that esbuild now implements is still useful even though it's one level deep, and so I believe it's still worth adding.

v0.14.9

Compare Source

• Implement cross-module tree shaking of TypeScript enum values (#​128)

  If your bundle uses TypeScript enums across multiple files, esbuild is able to inline the enum values as long as you export and import the enum using the ES module export and import keywords. However, this previously still left the definition of the enum in the bundle even when it wasn't used anymore. This was because esbuild's tree shaking (i.e. dead code elimination) is based on information recorded during parsing, and at that point we don't know which imported symbols are inlined enum values and which aren't.

  With this release, esbuild will now remove enum definitions that become unused due to cross-module enum value inlining. Property accesses off of imported symbols are now tracked separately during parsing and then resolved during linking once all inlined enum values are known. This behavior change means esbuild's support for cross-module inlining of TypeScript enums is now finally complete. Here's an example:

  // entry.ts
  import { Foo } from './enum'
  console.log(Foo.Bar)
  
  // enum.ts
  export enum Foo { Bar }

  Bundling the example code above now results in the enum definition being completely removed from the bundle:

  // Old output (with --bundle --minify --format=esm)
  var r=(o=>(o[o.Bar=0]="Bar",o))(r||{});console.log(0);
  
  // New output (with --bundle --minify --format=esm)
  console.log(0);

• Fix a regression with export {} from and CommonJS (#​1890)

  This release fixes a regression that was introduced by the change in 0.14.7 that avoids calling the __toESM wrapper for import statements that are converted to require calls and that don't use the default or __esModule export names. The previous change was correct for the import {} from syntax but not for the export {} from syntax, which meant that in certain cases with re-exported values, the value of the default import could be different than expected. This release fixes the regression.

• Warn about using module or exports in ESM code (#​1887)

  CommonJS export variables cannot be referenced in ESM code. If you do this, they are treated as global variables instead. This release includes a warning for people that try to use both CommonJS and ES module export styles in the same file. Here's an example:

  export enum Something {
    a,
    b,
  }
  module.exports = { a: 1, b: 2 }

  Running esbuild on that code now generates a warning that looks like this:

  ▲ [WARNING] The CommonJS "module" variable is treated as a global variable in an ECMAScript module and may not work as expected
  
      example.ts:5:0:
        5 │ module.exports = { a: 1, b: 2 }
          ╵ ~~~~~~
  
    This file is considered to be an ECMAScript module because of the "export" keyword here:
  
      example.ts:1:0:
        1 │ export enum Something {
          ╵ ~~~~~~
  

v0.14.8

Compare Source

• Add a resolve API for plugins (#​641, #​1652)

  Plugins now have access to a new API called resolve that runs esbuild's path resolution logic and returns the result to the caller. This lets you write plugins that can reuse esbuild's complex built-in path resolution logic to change the inputs and/or adjust the outputs. Here's an example:

  let examplePlugin = {
    name: 'example',
    setup(build) {
      build.onResolve({ filter: /^example$/ }, async () => {
        const result = await build.resolve('./foo', { resolveDir: '/bar' })
        if (result.errors.length > 0) return result
        return { ...result, external: true }
      })
    },
  }

  This plugin intercepts imports to the path example, tells esbuild to resolve the import ./foo in the directory /bar, and then forces whatever path esbuild returns to be considered external. Here are some additional details:

  • If you don't pass the optional resolveDir parameter, esbuild will still run onResolve plugin callbacks but will not attempt any path resolution itself. All of esbuild's path resolution logic depends on the resolveDir parameter including looking for packages in node_modules directories (since it needs to know where those node_modules directories might be).

  • If you want to resolve a file name in a specific directory, make sure the input path starts with ./. Otherwise the input path will be treated as a package path instead of a relative path. This behavior is identical to esbuild's normal path resolution logic.

  • If path resolution fails, the errors property on the returned object will be a non-empty array containing the error information. This function does not always throw an error when it fails. You need to check for errors after calling it.

  • The behavior of this function depends on the build configuration. That's why it's a property of the build object instead of being a top-level API call. This also means you can't call it until all plugin setup functions have finished since these give plugins the opportunity to adjust the build configuration before it's frozen at the start of the build. So the new resolve function is going to be most useful inside your onResolve and/or onLoad callbacks.

  • There is currently no attempt made to detect infinite path resolution loops. Calling resolve from within onResolve with the same parameters is almost certainly a bad idea.

• Avoid the CJS-to-ESM wrapper in some cases (#​1831)

  Import statements are converted into require() calls when the output format is set to CommonJS. To convert from CommonJS semantics to ES module semantics, esbuild wraps the return value in a call to esbuild's __toESM() helper function. However, the conversion is only needed if it's possible that the exports named default or __esModule could be accessed.

  This release avoids calling this helper function in cases where esbuild knows it's impossible for the default or __esModule exports to be accessed, which results in smaller and faster code. To get this behavior, you have to use the import {} from import syntax:

  // Original code
  import { readFile } from "fs";
  readFile();
  
  // Old output (with --format=cjs)
  var __toESM = (module, isNodeMode) => {
    ...
  };
  var import_fs = __toESM(require("fs"));
  (0, import_fs.readFile)();
  
  // New output (with --format=cjs)
  var import_fs = require("fs");
  (0, import_fs.readFile)();

• Strip overwritten function declarations when minifying (#​610)

  JavaScript allows functions to be re-declared, with each declaration overwriting the previous declaration. This type of code can sometimes be emitted by automatic code generators. With this release,

---

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, click this checkbox.

---

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

[angular-automatic-lock-bot]

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.}