build: update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@typescript-eslint/eslint-plugin	4.32.0 -> 4.33.0
@typescript-eslint/parser	4.32.0 -> 4.33.0
core-js	3.18.1 -> 3.18.2
esbuild	0.13.3 -> 0.13.4
esbuild-wasm	0.13.3 -> 0.13.4
inquirer	8.1.5 -> 8.2.0
less (source)	4.1.1 -> 4.1.2
mini-css-extract-plugin	2.3.0 -> 2.4.1
postcss (source)	8.3.8 -> 8.3.9
webpack	5.55.1 -> 5.57.1
webpack-dev-server	4.3.0 -> 4.3.1

---

Release Notes

typescript-eslint/typescript-eslint

v4.33.0

Compare Source

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

zloirock/core-js

v3.18.2

Compare Source

• Early { Array, %TypedArray% }.fromAsync errors moved to the promise, per the latest changes of the spec draft
• Internal ToInteger(OrInfinity) operation returns +0 for -0 argument, ES2020+ update
• Fixed theoretical problems with handling bigint in Number constructor wrapper
• Fixed String.raw with extra arguments
• Fixed some missed dependencies in entry points
• Some other minor fixes and improvements
• Refactoring

evanw/esbuild

v0.13.4

Compare Source

• Fix permission issues with the install script (#​1642)

  The esbuild package contains a small JavaScript stub file that implements the CLI (command-line interface). Its only purpose is to spawn the binary esbuild executable as a child process and forward the command-line arguments to it.

  The install script contains an optimization that replaces this small JavaScript stub with the actual binary executable at install time to avoid the overhead of unnecessarily creating a new node process. This optimization can't be done at package publish time because there is only one esbuild package but there are many supported platforms, so the binary executable for the current platform must live outside of the esbuild package.

  However, the optimization was implemented with an unlink operation followed by a link operation. This means that if the first step fails, the package is left in a broken state since the JavaScript stub file is deleted but not yet replaced.

  With this release, the optimization is now implemented with a link operation followed by a rename operation. This should always leave the package in a working state even if either step fails.

• Add a fallback for npm install esbuild --no-optional (#​1647)

  The installation method for esbuild's platform-specific binary executable was recently changed in version 0.13.0. Before that version esbuild downloaded it in an install script, and after that version esbuild lets the package manager download it using the optionalDependencies feature in package.json. This change was made because downloading the binary executable in an install script never really fully worked. The reasons are complex but basically there are a variety of edge cases where people people want to install esbuild in environments that they have customized such that downloading esbuild isn't possible. Using optionalDependencies instead lets the package manager deal with it instead, which should work fine in all cases (either that or your package manager has a bug, but that's not esbuild's problem).

  There is one case where this new installation method doesn't work: if you pass the --no-optional flag to npm to disable the optionalDependencies feature. If you do this, you prevent esbuild from being installed. This is not a problem with esbuild because you are manually enabling a flag to change npm's behavior such that esbuild doesn't install correctly. However, people still want to do this.

  With this release, esbuild will now fall back to the old installation method if the new installation method fails. THIS MAY NOT WORK. The new optionalDependencies installation method is the only supported way to install esbuild with npm. The old downloading installation method was removed because it doesn't always work. The downloading method is only being provided to try to be helpful but it's not the supported installation method. If you pass --no-optional and the download fails due to some environment customization you did, the recommended fix is to just remove the --no-optional flag.

• Support the new .mts and .cts TypeScript file extensions

  The upcoming version 4.5 of TypeScript has two new file extensions: .mts and .cts. Files with these extensions can be imported using the .mjs and .cjs, respectively. So the statement import "./foo.mjs" in TypeScript can actually succeed even if the file ./foo.mjs doesn't exist on the file system as long as the file ./foo.mts does exist. The import path with the .mjs extension is automatically re-routed to the corresponding file with the .mts extension at type-checking time by the TypeScript compiler. See the TypeScript 4.5 beta announcement for details.

  With this release, esbuild will also automatically rewrite .mjs to .mts and .cjs to .cts when resolving import paths to files on the file system. This should make it possible to bundle code written in this new style. In addition, the extensions .mts and .cts are now also considered valid TypeScript file extensions by default along with the .ts extension.

• Fix invalid CSS minification of margin and padding (#​1657)

  CSS minification does collapsing of margin and padding related properties. For example:

  /* Original CSS */
  div {
    margin: auto;
    margin-top: 5px;
    margin-left: 5px;
  }
  
  /* Minified CSS */
  div{margin:5px auto auto 5px}

  However, while this works for the auto keyword, it doesn't work for other keywords. For example:

  /* Original CSS */
  div {
    margin: inherit;
    margin-top: 5px;
    margin-left: 5px;
  }
  
  /* Minified CSS */
  div{margin:inherit;margin-top:5px;margin-left:5px}

  Transforming this to div{margin:5px inherit inherit 5px}, as was done in previous releases of esbuild, is an invalid transformation and results in incorrect CSS. This release of esbuild fixes this CSS transformation bug.

SBoudrias/Inquirer.js

v8.2.0

Compare Source

• checkbox prompt: Update the help message to be more complete. And the help message is now shown until a selection is made.

webpack-contrib/mini-css-extract-plugin

v2.4.1

Compare Source

v2.4.0

Compare Source

Performance

• migrate on new API, this improves performance and memory usage a lot, you need to have at least webpack 5.52.0 (recommended latest stable), for older versions the old API will be used (except explicit enabling of the experimentalUseImportModule option)

Features

• added support for supports() and layer() in @import at-rule (#​843) (e751080)

Bug Fixes

• crash with the exportLocalsConvention option (#​844) (0f8d501)

postcss/postcss

v8.3.9

Compare Source

• Replaced nanocolors to picocolors.
• Reduced package size.

webpack/webpack

v5.57.1

Compare Source

Bugfix

• fix experiments.cacheUnaffected which broke by last release

v5.57.0

Compare Source

Performance

• reduce number of hash.update calls
• allow ExternalModules to be unsafe cached
• improve hashing performance of module lists (StringXor)

Bugfixes

• experiments.cacheUnaffected
  • handle module/chunk id changes correctly
  • cache modules with async blocks
  • show errors when using incompatible options

v5.56.1

Compare Source

Bugfix

• DefinePlugin: fix conflict with older variants of the plugin

v5.56.0

Compare Source

Performance

• make DefinePlugin rebuild check more efficient performance and memory wise

webpack/webpack-dev-server

v4.3.1

Compare Source

---

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.

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