build: update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@bazel/buildifier	4.2.3 -> 4.2.4
@types/babel__core	7.1.16 -> 7.1.17
@typescript-eslint/eslint-plugin	5.5.0 -> 5.6.0
@typescript-eslint/parser	5.5.0 -> 5.6.0
core-js	3.19.2 -> 3.19.3
esbuild	0.14.1 -> 0.14.2
esbuild-wasm	0.14.1 -> 0.14.2
eslint (source)	8.3.0 -> 8.4.1
sass-loader	12.3.0 -> 12.4.0
webpack	5.64.4 -> 5.65.0

---

Release Notes

bazelbuild/buildtools

v4.2.4

Compare Source

• Minor bug fixes

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

v5.6.0

Compare Source

Features

• scope-manager: support TS4.5 import/export specifier kind (#​4234) (833f822)

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

v5.6.0

Compare Source

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

zloirock/core-js (core-js)

v3.19.3

Compare Source

• Fixed internal slots check in methods of some built-in types, #​1017
• Fixed URLSearchParams iterator .next that should be enumerable by the spec
• Refactored Subscription
• Added NodeJS 17.2 compat data mapping

zloirock/core-js (core-js)

evanw/esbuild (esbuild)

v0.14.2

Compare Source

• Add [ext] placeholder for path templates (#​1799)

  This release adds the [ext] placeholder to the --entry-names=, --chunk-names=, and --asset-names= configuration options. The [ext] placeholder takes the value of the file extension without the leading ., and can be used to place output files with different file extensions into different folders. For example, --asset-names=assets/[ext]/[name]-[hash] might generate an output path of assets/png/image-LSAMBFUD.png.

  This feature was contributed by @​LukeSheard.

• Disable star-to-clause transform for external imports (#​1801)

  When bundling is enabled, esbuild automatically transforms import * as x from 'y'; x.z() into import {z} as 'y'; z() to improve tree shaking. This avoids needing to create the import namespace object x if it's unnecessary, which can result in the removal of large amounts of unused code. However, this transform shouldn't be done for external imports because that incorrectly changes the semantics of the import. If the export z doesn't exist in the previous example, the value x.z is a property access that is undefined at run-time, but the value z is an import error that will prevent the code from running entirely. This release fixes the problem by avoiding doing this transform for external imports:

  // Original code
  import * as x from 'y';
  x.z();
  
  // Old output (with --bundle --format=esm --external:y)
  import { z } from "y";
  z();
  
  // New output (with --bundle --format=esm --external:y)
  import * as x from "y";
  x.z();

• Disable calc() transform for numbers with many fractional digits (#​1821)

  Version 0.13.12 introduced simplification of calc() expressions in CSS when minifying. For example, calc(100% / 4) turns into 25%. However, this is problematic for numbers with many fractional digits because either the number is printed with reduced precision, which is inaccurate, or the number is printed with full precision, which could be longer than the original expression. For example, turning calc(100% / 3) into 33.33333% is inaccurate and turning it into 33.333333333333336% likely isn't desired. In this release, minification of calc() is now disabled when any number in the result cannot be represented to full precision with at most five fractional digits.

• Fix an edge case with catch scope handling (#​1812)

  This release fixes a subtle edge case with catch scope and destructuring assignment. Identifiers in computed properties and/or default values inside the destructuring binding pattern should reference the outer scope, not the inner scope. The fix was to split the destructuring pattern into its own scope, separate from the catch body. Here's an example of code that was affected by this edge case:

  // Original code
  let foo = 1
  try {
    throw ['a', 'b']
  } catch ({ [foo]: y }) {
    let foo = 2
    assert(y === 'b')
  }
  
  // Old output (with --minify)
  let foo=1;try{throw["a","b"]}catch({[o]:t}){let o=2;assert(t==="b")}
  
  // New output (with --minify)
  let foo=1;try{throw["a","b"]}catch({[foo]:t}){let o=2;assert(t==="b")}

• Go 1.17.2 was upgraded to Go 1.17.4

  The previous release was built with Go 1.17.2, but this release is built with Go 1.17.4. This is just a routine upgrade. There are no changes significant to esbuild outside of some security-related fixes to Go's HTTP stack (but you shouldn't be running esbuild's dev server in production anyway).

  One notable change related to this is that esbuild's publishing script now ensures that git's state is free of uncommitted and/or untracked files before building. Previously this wasn't the case because publishing esbuild involved changing the version number, running the publishing script, and committing at the end, which meant that files were uncommitted during the build process. I also typically had some untracked test files in the same directory during publishing (which is harmless).

  This matters because there's an upcoming change in Go 1.18 where the Go compiler will include metadata about whether there are untracked files or not when doing a build: https://github.com/golang/go/issues/37475. Changing esbuild's publishing script should mean that when esbuild upgrades to Go 1.18, esbuild's binary executables will be marked as being built off of a specific commit without any modifications. This is important for reproducibility. Checking out a specific esbuild commit and building it should give a bitwise-identical binary executable to one that I published. But if this metadata indicated that there were untracked files during the published build, then the resulting executable would no longer be bitwise-identical.

evanw/esbuild (esbuild)

eslint/eslint

v8.4.1

Compare Source

Bug Fixes

• 234e3d9 fix: revert changes to reported locations in max-lines-per-function (#​15397) (Milos Djermanovic)

Documentation

• fa4d483 docs: fix typo in example for sort-keys rule (#​15393) (Nitin Kumar)

v8.4.0

Compare Source

Features

• 5771663 feat: add allowReserved parser option (#​15387) (Milos Djermanovic)
• 32ac37a feat: Flat config support in Linter (refs #​13481) (#​15185) (Nicholas C. Zakas)
• d041f34 feat: Treat Class/New Expressions as truthy in no-constant-condition (#​15326) (Jordan Eldredge)
• 8f44cf5 feat: report only lines that exceed the limit in max-lines-per-function (#​15140) (Sneh Khatri)
• 808ad35 feat: pass cwd to formatters (refs eslint/rfcs#​57) (#​13392) (Toru Nagashima)
• f1b7499 feat: support async formatters (#​15243) (MO)

Bug Fixes

• 4940cc5 fix: mark --rulesdir option as deprecated in CLI docs (#​15310) (Kevin Partington)

Documentation

• 54deec5 docs: update integrations.md (#​15380) (Vlad Sholokhov)
• fa0423a docs: fix typo in PR template (#​15365) (Nitin Kumar)
• e233920 docs: enable a few more markdownlint rules and fix violations (#​15368) (Bryan Mishkin)
• 632176d docs: Dedent needlessly indented example in getter-return docs (#​15363) (Jordan Eldredge)
• 4497e88 docs: Update release notes blog post template (#​15285) (Nicholas C. Zakas)

Chores

• efede90 chore: upgrade @​eslint/eslintrc@​1.0.5 (#​15389) (Milos Djermanovic)
• 0b8c846 chore: fix update-readme to avoid multiple consecutive blank lines (#​15375) (Milos Djermanovic)
• 94b2a8b chore: Use default Chromium binary in M1 Mac tests (#​15371) (Brandon Mills)
• ba58d94 ci: use node v16 for Verify Files (#​15364) (Nitin Kumar)
• 1e32ee5 chore: add jsdoc type annotation to rules (#​15291) (Bryan Mishkin)

webpack-contrib/sass-loader (sass-loader)

v12.4.0

Compare Source

Features

• add support for node-sass 7 (#​1002) (be5cbc9)

webpack-contrib/sass-loader (sass-loader)

webpack/webpack (webpack)

v5.65.0

Compare Source

Features

• static evaluation understands undefined now
• reduce container entry code by a few chars
• use template literals when available and they make sense

Bugfixes

• handle singleton flag without requiredVersion in Module Federation
• upgrade watchpack for context time info bugfix

Performance

• improve RegExp in error message formating for non-quadratic performance

Developer Experience

• automatically insert brackets when output.globalObject contains a non-trival expression
• show error when using script type external with invalid syntax
• expose types for Resolver, StatsOptions and ResolvePluginInstance

Preparations for the future

• hashDigestLength will default to 16 in webpack 6 (experiments.futureDefaults)

webpack/webpack (webpack)

---

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