chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@babel/compat-data	^7.14.0 -> ^7.14.4
@babel/core (source)	^7.14.2 -> ^7.14.3
@babel/helper-compilation-targets	^7.13.16 -> ^7.14.4
@babel/plugin-transform-runtime (source)	^7.14.2 -> ^7.14.3
@babel/preset-env (source)	^7.14.2 -> ^7.14.4
@nuxt/loading-screen	^2.0.3 -> ^2.0.4
@nuxt/telemetry	^1.3.3 -> ^1.3.6
@nuxtjs/eslint-config	^6.0.0 -> ^6.0.1
@nuxtjs/eslint-config-typescript	^6.0.0 -> ^6.0.1
@types/node	12.20.13 -> 12.20.14
@types/webpack	4.41.28 -> 4.41.29
@typescript-eslint/eslint-plugin	^4.23.0 -> ^4.26.0
@typescript-eslint/parser	^4.23.0 -> ^4.26.0
caniuse-lite	^1.0.30001228 -> ^1.0.30001233
chrome-launcher	^0.13.4 -> ^0.14.0
core-js-compat	^3.12.1 -> ^3.13.1
esbuild	^0.12.1 -> ^0.12.5
eslint (source)	^7.26.0 -> ^7.27.0
execa	^5.0.0 -> ^5.0.1
improved-yarn-audit	^2.3.2 -> ^2.3.3
jiti	^1.9.2 -> ^1.10.1
jsdom	^16.5.3 -> ^16.6.0
node-html-parser	^3.3.0 -> ^3.3.4
optimize-css-assets-webpack-plugin	^5.0.4 -> ^5.0.6
rollup (source)	2.48.0 -> 2.50.5
rollup-plugin-esbuild	^4.2.3 -> ^4.3.1
rollup-plugin-license	^2.3.0 -> ^2.4.0
sass	^1.32.13 -> ^1.34.0
typescript (source)	~4.2 -> ~4.3
ufo	^0.7.4 -> ^0.7.5
vue	^2.6.12 -> ^2.6.13
vue-server-renderer	^2.6.12 -> ^2.6.13
vue-template-compiler	^2.6.12 -> ^2.6.13
watchpack	^2.1.1 -> ^2.2.0
webpack-bundle-analyzer	^4.4.1 -> ^4.4.2
webpack-dev-middleware	^4.2.0 -> ^4.3.0

---

Release Notes

babel/babel

v7.14.4

Compare Source

👓 Spec Compliance

• babel-parser
  • #​13377 disallow surrogate in the end of contextual name (@​JLHwung)
  • #​13328 perf: minimize identifier lookahead when parsing let (@​JLHwung)
• babel-plugin-transform-typescript
  • #​13314 [ts] Insert export {} when necessary to imply ESM (@​wbinnssmith)

🐛 Bug Fix

• babel-plugin-transform-typescript
  • #​13381 [ts] Remove override modifier (@​sosukesuzuki)
• Other
  • #​13338 Fix error when parsing ignored files with @babel/eslint-parser (@​devfservant)
• babel-parser
  • #​13333 refactor: add parse*Literal parser routines (@​JLHwung)

🏃‍♀️ Performance

• babel-plugin-transform-block-scoping
  • #​13376 Improve performance (@​sokra)
• babel-parser
  • #​13341 Faster tokenizer lookahead (@​JLHwung)
  • #​13328 perf: minimize identifier lookahead when parsing let (@​JLHwung)

🔬 Output optimization

• babel-plugin-proposal-object-rest-spread, babel-plugin-transform-block-scoping, babel-plugin-transform-destructuring, babel-plugin-transform-react-constant-elements, babel-preset-env
  • #​13384 Hoist omitted keys from object spread operator (@​alanorozco)

nuxt/loading-screen

v2.0.4

Compare Source

nuxt/telemetry

v1.3.6

Compare Source

v1.3.5

Compare Source

v1.3.4

Compare Source

nuxt/eslint-config

v6.0.1

Compare Source

typescript-eslint/typescript-eslint

v4.26.0

Compare Source

Bug Fixes

• eslint-plugin: [no-type-alias] consider type imports as alias types (#​3433) (d4f0774)
• generate library types for TypeScript v4.3 (#​3460) (ed4776a), closes #​3449

Features

• eslint-plugin: [member-ordering] add callback as an ordering type of node (#​3354) (d134b1f)
• eslint-plugin: [space-infix-ops] Add support for Union and intersection of type declarations (#​3360) (3d29323)
• scope-manager: reduce generated lib file size (#​3468) (258116b)

v4.25.0

Compare Source

Bug Fixes

• corrected no-unsupported-browser-code in roadmap as unimplemented (#​3407) (2319b0e)
• experimental-utils: fix isAwaitKeyword predicate in ast-utils (#​3290) (c15da67)

Features

• typescript-estree: [TS4.3] support overrides on class members (#​3429) (21d1b62)
• typescript-estree: add support for getter/setter signatures on types (#​3427) (b830b7f), closes #​3272 #​3272

v4.24.0

Compare Source

Bug Fixes

• eslint-plugin: [no-shadow] fix static class method generics shadowing class generics (#​3393) (b1e1c8a), closes #​2592
• eslint-plugin: [no-unsafe-*] special case handling for the empty map constructor with no generics (#​3394) (cae4f4a), closes #​2109

Features

• eslint-plugin: [dot-notation] optionally allow square bracket notation where an index signature exists in conjunction with noPropertyAccessFromIndexSignature (#​3361) (37ec2c2)

GoogleChrome/chrome-launcher

v0.14.0

Compare Source

• ac1f4aff move to minimum node 12; remove rimraf (#​237)
• dec646c4 deps: remove mkdirp for fs.mkdirSync (#​234)
• 83ab178a update minimum node version (#​222)
• a5f6eb2f add additional chrome flags (#​227)
• 3a7c9610 reword unset-CHROME_PATH error message
• b1b8dc74 rename disabled TranslateUI to Translate to match Chrome (#​225)
• beb41360 chore: update dependencies and test targets (#​221)
• df9d564a tests: migrate from travis to github actions (#​228)
• 673da08b tests: add mac/win bots to ci (#​232)
• a700ae0c docs: fix readme's getInstallations() section (#​212)
• chrome-flags-for-tools.md update
  • 4b98587d massive update and refactor (#​226)
  • e45b100f minor tweaks to headless and others
  • 3a90c21b fix links
  • 8429ca93 add feature flags description
  • 21db5f9f even more documented flags (#​231)

zloirock/core-js

v3.13.1

Compare Source

• Overwrites get-own-property-symbols third-party Symbol polyfill if it's used since it causes a stack overflow, #​774
• Added a workaround of possible browser crash on Object.prototype accessors methods in WebKit ~ Android 4.0, #​232

v3.13.0

Compare Source

• Accessible Object#hasOwnProperty (Object.hasOwn) proposal moved to the stage 3, May 2021 TC39 meeting

evanw/esbuild

v0.12.5

Compare Source

• Add support for lowering tagged template literals to ES5 (#​297)

  This release adds support for lowering tagged template literals such as String.raw`\unicode` to target environments that don't support them such as --target=es5 (non-tagged template literals were already supported). Each literal turns into a function call to a helper function:

  // Original code
  console.log(String.raw`\unicode`)
  
  // Lowered code
  console.log(String.raw(__template([void 0], ["\\unicode"])));

• Change class field behavior to match TypeScript 4.3

  TypeScript 4.3 includes a subtle breaking change that wasn't mentioned in the TypeScript 4.3 blog post: class fields will now be compiled with different semantics if "target": "ESNext" is present in tsconfig.json. Specifically in this case useDefineForClassFields will default to true when not specified instead of false. This means class field behavior in TypeScript code will now match JavaScript instead of doing something else:

  class Base {
    set foo(value) { console.log('set', value) }
  }
  class Derived extends Base {
    foo = 123
  }
  new Derived()

  In TypeScript 4.2 and below, the TypeScript compiler would generate code that prints set 123 when tsconfig.json contains "target": "ESNext" but in TypeScript 4.3, the TypeScript compiler will now generate code that doesn't print anything. This is the difference between "assign" semantics and "define" semantics. With this release, esbuild has been changed to follow the TypeScript 4.3 behavior.

• Avoid generating the character sequence </script> (#​1322)

  If the output of esbuild is inlined into a <script>...</script> tag inside an HTML file, the character sequence </script> inside the JavaScript code will accidentally cause the script tag to be terminated early. There are at least four such cases where this can happen:

  console.log('</script>')
  console.log(1</script>/.exec(x).length)
  console.log(String.raw`</script>`)
  // @&#8203;license </script>

  With this release, esbuild will now handle all of these cases and avoid generating the problematic character sequence:

  console.log('<\/script>');
  console.log(1< /script>/.exec(x).length);
  console.log(String.raw(__template(["<\/script>"], ["<\/script>"])));
  // @&#8203;license <\/script>

• Change the triple-slash reference comment for Deno (#​1325)

  The comment in esbuild's JavaScript API implementation for Deno that references the TypeScript type declarations has been changed from /// <reference path="./mod.d.ts" /> to /// <reference types="./mod.d.ts" />. This comment was copied from Deno's documentation but apparently Deno's documentation was incorrect. The comment in esbuild's Deno bundle has been changed to reflect Deno's latest documentation.

v0.12.4

Compare Source

• Reorder name preservation before TypeScript decorator evaluation (#​1316)

  The --keep-names option ensures the .name property on functions and classes remains the same after bundling. However, this was being enforced after TypeScript decorator evaluation which meant that the decorator could observe the incorrect name. This has been fixed and now .name preservation happens before decorator evaluation instead.

• Potential fix for a determinism issue (#​1304)

  This release contains a potential fix for an unverified issue with non-determinism in esbuild. The regression was apparently introduced in 0.11.13 and may be related to parallelism that was introduced around the point where dynamic import() expressions are added to the list of entry points. Hopefully this fix should resolve the regression.

• Respect target in tsconfig.json (#​277)

  Each JavaScript file that esbuild bundles will now be transformed according to the target language level from the nearest enclosing tsconfig.json file. This is in addition to esbuild's own --target setting; the two settings are merged by transforming any JavaScript language feature that is unsupported in either esbuild's configured --target value or the target property in the tsconfig.json file.

v0.12.3

Compare Source

• Ensure JSX element names start with a capital letter (#​1309)

  The JSX specification only describes the syntax and says nothing about how to interpret it. But React (and therefore esbuild) treats JSX tags that start with a lower-case ASCII character as strings instead of identifiers. That way the tag <i/> always refers to the italic HTML element i and never to a local variable named i.

  However, esbuild may rename identifiers for any number of reasons such as when minification is enabled. Previously esbuild could sometimes rename identifiers used as tag names such that they start with a lower-case ASCII character. This is problematic when JSX syntax preservation is enabled since subsequent JSX processing would then turn these identifier references into strings.

  With this release, esbuild will now make sure identifiers used in tag names start with an upper-case ASCII character instead when JSX syntax preservation is enabled. This should avoid problems when using esbuild with JSX transformation tools.

• Fix a single hyphen being treated as a CSS name (#​1310)

  CSS identifiers are allowed to start with a - character if (approximately) the following character is a letter, an escape sequence, a non-ASCII character, the character _, or another - character. This check is used in certain places when printing CSS to determine whether a token is a valid identifier and can be printed as such or whether it's an invalid identifier and needs to be quoted as a string. One such place is in attribute selectors such as [a*=b].

  However, esbuild had a bug where a single - character was incorrectly treated as a valid identifier in this case. This is because the end of string became U+FFFD (the Unicode replacement character) which is a non-ASCII character and a valid name-start code point. With this release a single - character is no longer treated as a valid identifier. This fix was contributed by @​lbwa.

v0.12.2

Compare Source

• Fix various code generation and minification issues (#​1305)

  This release fixes the following issues, which were all identified by running esbuild against the latest UglifyJS test suite:

  • The in operator is now surrounded parentheses inside arrow function expression bodies inside for loop initializers:

    // Original code
    for ((x => y in z); 0; ) ;
    
    // Old output
    for ((x) => y in z; 0; ) ;
    
    // New output
    for ((x) => (y in z); 0; ) ;

    Without this, the in operator would cause the for loop to be considered a for-in loop instead.

  • The statement return undefined; is no longer minified to return; inside async generator functions:

    // Original code
    return undefined;
    
    // Old output
    return;
    
    // New output
    return void 0;

    Using return undefined; inside an async generator function has the same effect as return await undefined; which schedules a task in the event loop and runs code in a different order than just return;, which doesn't hide an implicit await expression.

  • Property access expressions are no longer inlined in template tag position:

    // Original code
    (null, a.b)``, (null, a[b])``;
    
    // Old output
    a.b``, a[b]``;
    
    // New output
    (0, a.b)``, (0, a[b])``;

    The expression a.b`c` is different than the expression (0, a.b)`c`. The first calls the function a.b with a as the value for this but the second calls the function a.b with the default value for this (the global object in non-strict mode or undefined in strict mode).

  • Verbatim __proto__ properties inside object spread are no longer inlined when minifying:

    // Original code
    x = { ...{ __proto__: { y: true } } }.y;
    
    // Old output
    x = { __proto__: { y: !0 } }.y;
    
    // New output
    x = { ...{ __proto__: { y: !0 } } }.y;

    A verbatim (i.e. non-computed non-method) property called __proto__ inside an object literal actually sets the prototype of the surrounding object literal. It does not add an "own property" called __proto__ to that object literal, so inlining it into the parent object literal would be incorrect. The presence of a __proto__ property now stops esbuild from applying the object spread inlining optimization when minifying.

  • The value of this has now been fixed for lowered private class members that are used as template tags:

    // Original code
    x = (new (class {
      a = this.#c``;
      b = 1;
      #c() { return this }
    })).a.b;
    
    // Old output
    var _c, c_fn, _a;
    x = new (_a = class {
      constructor() {
        __privateAdd(this, _c);
        __publicField(this, "a", __privateMethod(this, _c, c_fn)``);
        __publicField(this, "b", 1);
      }
    }, _c = new WeakSet(), c_fn = function() {
      return this;
    }, _a)().a.b;
    
    // New output
    var _c, c_fn, _a;
    x = new (_a = class {
      constructor() {
        __privateAdd(this, _c);
        __publicField(this, "a", __privateMethod(this, _c, c_fn).bind(this)``);
        __publicField(this, "b", 1);
      }
    }, _c = new WeakSet(), c_fn = function() {
      return this;
    }, _a)().a.b;

    The value of this here should be an instance of the class because the template tag is a property access expression. However, it was previously the default value (the global object in non-strict mode or undefined in strict mode) instead due to the private member transformation, which is incorrect.

  • Invalid escape sequences are now allowed in tagged template literals

    This implements the template literal revision feature: https://github.com/tc39/proposal-template-literal-revision. It allows you to process tagged template literals using custom semantics that don't follow JavaScript escape sequence rules without causing a syntax error:

    console.log((x => x.raw)`invalid \unicode escape sequence`)

eslint/eslint

v7.27.0

Compare Source

• 2c0868c Chore: merge all html formatter files into html.js (#​14612) (Milos Djermanovic)
• 9e9b5e0 Update: no-unused-vars false negative with comma operator (fixes #​14325) (#​14354) (Nitin Kumar)
• afe9569 Chore: use includes instead of indexOf (#​14607) (Mikhail Bodrov)
• c0f418e Chore: Remove lodash (#​14287) (Stephen Wade)
• 52655dd Update: no-restricted-imports custom message for patterns (fixes #​11843) (#​14580) (Alex Holden)
• 967b1c4 Chore: Fix typo in large.js (#​14589) (Ikko Ashimine)
• 2466a05 Sponsors: Sync README with website (ESLint Jenkins)
• fe29f18 Sponsors: Sync README with website (ESLint Jenkins)
• 086c1d6 Chore: add more test cases for no-sequences (#​14579) (Nitin Kumar)
• 6a2ced8 Docs: Update README team and sponsors (ESLint Jenkins)

sindresorhus/execa

v5.0.1

Compare Source

• Fix timeout option validation (#​463) 427c5c2

djfdyuruiry/improved-yarn-audit

v2.3.3

• Fix ENOBUFS error when there's huge amounts of output #​23

unjs/jiti

v1.10.1

Compare Source

v1.10.0

Compare Source

Features

• enable allowDeclareFields for babel transform (#​33) (914499c)

1.9.2 (2021-05-11)

Bug Fixes

• spread when pushing babel plugins from transformOptions (#​31) (f25960a)

1.9.1 (2021-04-09)

jsdom/jsdom

v16.6.0

Compare Source

• Added parentNode.replaceChildren(). (ninevra)
• Fixed jsdom's handling of when code running inside the jsdom throws null or undefined as an exception. (mbest)
• Removed the dependency on the deprecated request package, in the process fixing several issues with the XMLHttpRequest implementation around header processing. Special thanks to vegardbb for completing this months-long effort!

taoqf/node-fast-html-parser

v3.3.4

Compare Source

• Merge pull request #​123 from nonara/trim-fix 0632085
• test: Improve testing d914efa
• style: Normalize indents to tab 0195dd3
• Refactored to implement with structuredText b75a51d
• fix issue #​115 d4d06ed

v3.3.3

Compare Source

• Merge pull request #​118 from hugmanrique/main bc6ba6e
• nextElementSibling returns an HTMLElement 607c003

v3.3.2

Compare Source

• issue #​115 8cd256f

v3.3.1

Compare Source

• Merge pull request #​122 from lamplightdev/main e4e8116
• Fixes #​62 - Escape double quotes in attribute values e9ec888

NMFR/optimize-css-assets-webpack-plugin

v5.0.6

Compare Source

v5.0.5

Compare Source

rollup/rollup

---

Configuration

📅 Schedule: At any time (no schedule defined).

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

[codecov-commenter]

Codecov Report

Merging #9298 (7dced4d) into dev (b9bfb9d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #9298   +/-   ##
=======================================
  Coverage   65.14%   65.14%           
=======================================
  Files          94       94           
  Lines        4106     4106           
  Branches     1124     1124           
=======================================
  Hits         2675     2675           
  Misses       1153     1153           
  Partials      278      278           

Flag	Coverage Δ
unittests	65.14% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b9bfb9d...7dced4d. Read the comment docs.