chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@rollup/plugin-commonjs	^22.0.0 -> ^22.0.1
esbuild	^0.14.47 -> ^0.14.49
mkdist	^0.3.10 -> ^0.3.13
mlly	^0.5.3 -> ^0.5.4
pathe	^0.3.0 -> ^0.3.2
pnpm (source)	7.3.0 -> 7.5.2
rollup (source)	^2.75.7 -> ^2.77.0

---

Release Notes

rollup/plugins

v22.0.1

2022-06-24

Bugfixes

• fix: Only proxy detected commonjs entry points (#​1180)

evanw/esbuild

v0.14.49

Compare Source

• Keep inlined constants when direct eval is present (#​2361)

  Version 0.14.19 of esbuild added inlining of certain const variables during minification, which replaces all references to the variable with the initializer and then removes the variable declaration. However, this could generate incorrect code when direct eval is present because the direct eval could reference the constant by name. This release fixes the problem by preserving the const variable declaration in this case:

  // Original code
  console.log((() => { const x = 123; return x + eval('x') }))
  
  // Old output (with --minify)
  console.log(()=>123+eval("x"));
  
  // New output (with --minify)
  console.log(()=>{const x=123;return 123+eval("x")});

• Fix an incorrect error in TypeScript when targeting ES5 (#​2375)

  Previously when compiling TypeScript code to ES5, esbuild could incorrectly consider the following syntax forms as a transformation error:

  0 ? ([]) : 1 ? ({}) : 2;

  The error messages looked like this:

  ✘ [ERROR] Transforming destructuring to the configured target environment ("es5") is not supported yet
  
      example.ts:1:5:
        1 │ 0 ? ([]) : 1 ? ({}) : 2;
          ╵      ^
  
  ✘ [ERROR] Transforming destructuring to the configured target environment ("es5") is not supported yet
  
      example.ts:1:16:
        1 │ 0 ? ([]) : 1 ? ({}) : 2;
          ╵                 ^
  

  These parenthesized literals followed by a colon look like the start of an arrow function expression followed by a TypeScript return type (e.g. ([]) : 1 could be the start of the TypeScript arrow function ([]): 1 => 1). Unlike in JavaScript, parsing arrow functions in TypeScript requires backtracking. In this case esbuild correctly determined that this expression wasn't an arrow function after all but the check for destructuring was incorrectly not covered under the backtracking process. With this release, the error message is now only reported if the parser successfully parses an arrow function without backtracking.

• Fix generated TypeScript enum comments containing */ (#​2369, #​2371)

  TypeScript enum values that are equal to a number or string literal are inlined (references to the enum are replaced with the literal value) and have a /* ... */ comment after them with the original enum name to improve readability. However, this comment is omitted if the enum name contains the character sequence */ because that would end the comment early and cause a syntax error:

  // Original TypeScript
  enum Foo { '/*' = 1, '*/' = 2 }
  console.log(Foo['/*'], Foo['*/'])
  
  // Generated JavaScript
  console.log(1 /* /* */, 2);

  This was originally handled correctly when TypeScript enum inlining was initially implemented since it was only supported within a single file. However, when esbuild was later extended to support TypeScript enum inlining across files, this special case where the enum name contains */ was not handled in that new code. Starting with this release, esbuild will now handle enums with names containing */ correctly when they are inlined across files:

  // foo.ts
  export enum Foo { '/*' = 1, '*/' = 2 }
  
  // bar.ts
  import { Foo } from './foo'
  console.log(Foo['/*'], Foo['*/'])
  
  // Old output (with --bundle --format=esm)
  console.log(1 /* /* */, 2 /* */ */);
  
  // New output (with --bundle --format=esm)
  console.log(1 /* /* */, 2);

  This fix was contributed by @​magic-akari.

• Allow declare class fields to be initialized (#​2380)

  This release fixes an oversight in the TypeScript parser that disallowed initializers for declare class fields. TypeScript actually allows the following limited initializer expressions for readonly fields:

  declare const enum a { b = 0 }
  
  class Foo {
    // These are allowed by TypeScript
    declare readonly a = 0
    declare readonly b = -0
    declare readonly c = 0n
    declare readonly d = -0n
    declare readonly e = 'x'
    declare readonly f = `x`
    declare readonly g = a.b
    declare readonly h = a['b']
  
    // These are not allowed by TypeScript
    declare readonly x = (0)
    declare readonly y = null
    declare readonly z = -a.b
  }

  So with this release, esbuild now allows initializers for declare class fields too. To future-proof this in case TypeScript allows more expressions as initializers in the future (such as null), esbuild will allow any expression as an initializer and will leave the specifics of TypeScript's special-casing here to the TypeScript type checker.

• Fix a bug in esbuild's feature compatibility table generator (#​2365)

  Passing specific JavaScript engines to esbuild's --target flag restricts esbuild to only using JavaScript features that are supported on those engines in the output files that esbuild generates. The data for this feature is automatically derived from this compatibility table with a script: https://kangax.github.io/compat-table/.

  However, the script had a bug that could incorrectly consider a JavaScript syntax feature to be supported in a given engine even when it doesn't actually work in that engine. Specifically this bug happened when a certain aspect of JavaScript syntax has always worked incorrectly in that engine and the bug in that engine has never been fixed. This situation hasn't really come up before because previously esbuild pretty much only targeted JavaScript engines that always fix their bugs, but the two new JavaScript engines that were added in the previous release (Hermes and Rhino) have many aspects of the JavaScript specification that have never been implemented, and may never be implemented. For example, the let and const keywords are not implemented correctly in those engines.

  With this release, esbuild's compatibility table generator script has been fixed and as a result, esbuild will now correctly consider a JavaScript syntax feature to be unsupported in a given engine if there is some aspect of that syntax that is broken in all known versions of that engine. This means that the following JavaScript syntax features are no longer considered to be supported by these engines (represented using esbuild's internal names for these syntax features):

  Hermes:

  • arrow
  • const-and-let
  • default-argument
  • generator
  • optional-catch-binding
  • optional-chain
  • rest-argument
  • template-literal

  Rhino:

  • arrow
  • const-and-let
  • destructuring
  • for-of
  • generator
  • object-extensions
  • template-literal

  IE:

  • const-and-let

v0.14.48

Compare Source

• Enable using esbuild in Deno via WebAssembly (#​2323)

  The native implementation of esbuild is much faster than the WebAssembly version, but some people don't want to give Deno the --allow-run permission necessary to run esbuild and are ok waiting longer for their builds to finish when using the WebAssembly backend. With this release, you can now use esbuild via WebAssembly in Deno. To do this you will need to import from wasm.js instead of mod.js:

  import * as esbuild from 'https://deno.land/x/esbuild@v0.14.48/wasm.js'
  const ts = 'let test: boolean = true'
  const result = await esbuild.transform(ts, { loader: 'ts' })
  console.log('result:', result)

  Make sure you run Deno with --allow-net so esbuild can download the WebAssembly module. Using esbuild like this starts up a worker thread that runs esbuild in parallel (unless you call esbuild.initialize({ worker: false }) to tell esbuild to run on the main thread). If you want to, you can call esbuild.stop() to terminate the worker if you won't be using esbuild anymore and you want to reclaim the memory.

  Note that Deno appears to have a bug where background WebAssembly optimization can prevent the process from exiting for many seconds. If you are trying to use Deno and WebAssembly to run esbuild quickly, you may need to manually call Deno.exit(0) after your code has finished running.

• Add support for font file MIME types (#​2337)

  This release adds support for font file MIME types to esbuild, which means they are now recognized by the built-in local web server and they are now used when a font file is loaded using the dataurl loader. The full set of newly-added file extension MIME type mappings is as follows:

  • .eot => application/vnd.ms-fontobject
  • .otf => font/otf
  • .sfnt => font/sfnt
  • .ttf => font/ttf
  • .woff => font/woff
  • .woff2 => font/woff2

• Remove "use strict"; when targeting ESM (#​2347)

  All ES module code is automatically in strict mode, so a "use strict"; directive is unnecessary. With this release, esbuild will now remove the "use strict"; directive if the output format is ESM. This change makes the generated output file a few bytes smaller:

  // Original code
  'use strict'
  export let foo = 123
  
  // Old output (with --format=esm --minify)
  "use strict";let t=123;export{t as foo};
  
  // New output (with --format=esm --minify)
  let t=123;export{t as foo};

• Attempt to have esbuild work with Deno on FreeBSD (#​2356)

  Deno doesn't support FreeBSD, but it's possible to build Deno for FreeBSD with some additional patches on top. This release of esbuild changes esbuild's Deno installer to download esbuild's FreeBSD binary in this situation. This configuration is unsupported although in theory everything should work.

• Add some more target JavaScript engines (#​2357)

  This release adds the Rhino and Hermes JavaScript engines to the set of engine identifiers that can be passed to the --target flag. You can use this to restrict esbuild to only using JavaScript features that are supported on those engines in the output files that esbuild generates.

unjs/mkdist

v0.3.13

Compare Source

v0.3.12

Compare Source

v0.3.11

Compare Source

unjs/mlly

v0.5.4

Compare Source

unjs/pathe

v0.3.2

Compare Source

v0.3.1

Compare Source

pnpm/pnpm

v7.5.2

Compare Source

Patch Changes

• Don't print any info messages about .pnpmfile.cjs #​5027.
• Do not print a package with unchanged version in the installation summary #​5031.

Our Gold Sponsors

#### Our Silver Sponsors #### What's Changed * fix: summary reporting by @​zkochan in https://github.com/pnpm/pnpm/pull/5031 * fix: don't print info messages about .pnpmfile.cjs by @​zkochan in https://github.com/pnpm/pnpm/pull/5032

Full Changelog: pnpm/pnpm@v7.5.1...v7.5.2

v7.5.1

Compare Source

Patch Changes

• Don't symlink the autoinstalled peer dependencies to the root of node_modules #​4988.
• Avoid retaining a copy of the contents of files deleted during patching #​5003.
• Remove file reporter logging. Logged file is not useful #​4949.

Our Gold Sponsors

##### Our Silver Sponsors ##### What's Changed * fix: don't symlink the autoinstalled peers to the root of node_modules by @​zkochan in https://github.com/pnpm/pnpm/pull/4998 * feat: use irreversible-delete in pnpm patch-commit by @​webstrand in https://github.com/pnpm/pnpm/pull/5008 * feat(file-reporter): remove file reporter by @​william2958 in https://github.com/pnpm/pnpm/pull/5012 ##### New Contributors * @​webstrand made their first contribution in https://github.com/pnpm/pnpm/pull/5008 * @​william2958 made their first contribution in https://github.com/pnpm/pnpm/pull/5012

Full Changelog: pnpm/pnpm@v7.5.0...v7.5.1

v7.5.0

Compare Source

Minor Changes

• A new value rolling for option save-workspace-protocol. When selected, pnpm will save workspace versions using a rolling alias (e.g. "foo": "workspace:^") instead of pinning the current version number (e.g. "foo": "workspace:^1.0.0"). Usage example, in the root of your workspace, create a .npmrc with the following content:

  save-workspace-protocol=rolling
  

Patch Changes

• pnpm remove <pkg> should not fail in a workspace that has patches #​4954
• The hash of the patch file should be the same on both Windows and POSIX #​4961.
• pnpm env use should throw an error on a system that use the MUSL libc.

Our Gold Sponsors

#### Our Silver Sponsors #### What's Changed * fix(env): throw an error on a system that uses MUSL libc by @​zkochan in https://github.com/pnpm/pnpm/pull/4958 * feat: use workspace spec alias by default in pnpm add by @​javier-garcia-meteologica in https://github.com/pnpm/pnpm/pull/4947 * fix(patch): the hash of the patch file should be the same on both Windows and POSIX by @​zkochan in https://github.com/pnpm/pnpm/pull/4969

Full Changelog: pnpm/pnpm@v7.4.1...v7.5.0

v7.4.1

Compare Source

Patch Changes

• pnpm install in a workspace with patches should not fail when doing partial installation #​4954.
• Never skip lockfile resolution when the lockfile is not up-to-date and --lockfile-only is used. Even if frozen-lockfile is true #​4951.
• Never add an empty patchedDependencies field to pnpm-lock.yaml.

Our Gold Sponsors

#### Our Silver Sponsors #### What's Changed * fix(lockfile): never add an empty `patchedDependencies` field to `pnpm-lock.yaml` by @​zkochan in https://github.com/pnpm/pnpm/pull/4948 * Add "refs/"+refname to resolution options by @​rotu in https://github.com/pnpm/pnpm/pull/4953 * fix: --lockfile-only in CI and with frozen-lockfile=true by @​zkochan in https://github.com/pnpm/pnpm/pull/4955 * fix: partial install in workspace with patches should not fail by @​zkochan in https://github.com/pnpm/pnpm/pull/4956 #### New Contributors * @​rotu made their first contribution in https://github.com/pnpm/pnpm/pull/4953

Full Changelog: pnpm/pnpm@v7.4.0...v7.4.1

v7.4.0

Compare Source

Minor Changes

• Dependencies patching is possible via the pnpm.patchedDependencies field of the package.json.
  To patch a package, the package name, exact version, and the relative path to the patch file should be specified. For instance:

  {
    "pnpm": {
      "patchedDependencies": {
        "eslint@1.0.0": "./patches/eslint@1.0.0.patch"
      }
    }
  }

• Two new commands added: pnpm patch and pnpm patch-commit.

  pnpm patch <pkg> prepares a package for patching. For instance, if you want to patch express v1, run:

  pnpm patch express@1.0.0
  

  pnpm will create a temporary directory with express@1.0.0 that you can modify with your changes.
  Once you are read with your changes, run:

  pnpm patch-commit <path to temp folder>
  

  This will create a patch file and write it to <project>/patches/express@1.0.0.patch.
  Also, it will reference this new patch file from the patchedDependencies field in package.json:

  {
    "pnpm": {
      "patchedDependencies": {
        "express@1.0.0": "patches/express@1.0.0.patch"
      }
    }
  }

• A new experimental command added: pnpm deploy. The deploy command takes copies a project from a workspace and installs all of its production dependencies (even if some of those dependencies are other projects from the workspace).

  For example, the new command will deploy the project named foo to the dist directory in the root of the workspace:

  pnpm --filter=foo deploy dist
  

• package-import-method supports a new option: clone-or-copy.

• New setting added: include-workspace-root. When it is set to true, the run, exec, add, and test commands will include the root package, when executed recursively #​4906

Patch Changes

• Don't crash when pnpm update --interactive is cancelled with Ctrl+c.

• The use-node-version setting should work with prerelease Node.js versions. For instance:

  use-node-version=18.0.0-rc.3
  

• Return early when the lockfile is up-to-date.

• Resolve native workspace path for case-insensitive file systems #​4904.

• Don't link local dev dependencies, when prod dependencies should only be installed.

• pnpm audit --fix should not add an override for a vulnerable package that has no fixes released.

• Update the compatibility database.

Our Gold Sponsors

#### Our Silver Sponsors #### What's Changed * feat: patch package by @​zkochan in https://github.com/pnpm/pnpm/pull/4885 * feat: add `patch` and `patch-commit` commands by @​zkochan in https://github.com/pnpm/pnpm/pull/4900 * fix(env): `use-node-version` should work with prerelease versions by @​zkochan in https://github.com/pnpm/pnpm/pull/4903 * refactor: create @​pnpm/node.fetcher by @​zkochan in https://github.com/pnpm/pnpm/pull/4908 * feat(patch): update patched dependencies on install by @​zkochan in https://github.com/pnpm/pnpm/pull/4905 * fix: throw an error if not all patches were applied by @​zkochan in https://github.com/pnpm/pnpm/pull/4911 * fix: a modified patch should update the deps on install by @​zkochan in https://github.com/pnpm/pnpm/pull/4918 * fix: packages should be patched even when scripts are ignored by @​zkochan in https://github.com/pnpm/pnpm/pull/4922 * fix: patch package even if it is not in the onlyBuiltDependencies list by @​zkochan in https://github.com/pnpm/pnpm/pull/4925 * fix: respect include-workspace-root npmrc option by @​shirotech in https://github.com/pnpm/pnpm/pull/4928 * fix: install --lockfile-only should exit early by @​zkochan in https://github.com/pnpm/pnpm/pull/4932 * fix: resolve real path for case insensitive systems by @​mdogadailo in https://github.com/pnpm/pnpm/pull/4935 * feat: deploy command by @​zkochan in https://github.com/pnpm/pnpm/pull/4933 * fix: use recursive for deploy command directory creation by @​ragrag in https://github.com/pnpm/pnpm/pull/4943 * fix: don't fail when the patched pkg appears multiple times by @​zkochan in https://github.com/pnpm/pnpm/pull/4945 #### New Contributors * @​shirotech made their first contribution in https://github.com/pnpm/pnpm/pull/4928 * @​mdogadailo made their first contribution in https://github.com/pnpm/pnpm/pull/4935 * @​ragrag made their first contribution in https://github.com/pnpm/pnpm/pull/4943

Full Changelog: pnpm/pnpm@v7.3.0...v7.4.0

rollup/rollup

v2.77.0

Compare Source

2022-07-15

Features

• Introduce maxParallelFileOps to limit both read and write operations, default to 20 and replaces maxParallelFileRead (#​4570)

Bug Fixes

• Avoid including variables referenced from return statements that are never reached (#​4573)

Pull Requests

• #​4570: Introduce maxParallelFileOps to limit parallel writes (@​lukastaegert)
• #​4572: Document more ways to read package.json in ESM (@​berniegp)
• #​4573: Do not include unused return expressions (@​lukastaegert)

v2.76.0

Compare Source

2022-07-08

Features

• Allow setting a sourcmapBaseUrl for absolute paths in sourcemaps (#​4527)

Bug Fixes

• Support absolute CLI plugin paths on Windows (#​4533)

Pull Requests

• #​4527: Add sourcemapBaseUrl option (@​nickgarlis)
• #​4533: Add support for absolute plugin paths (@​ygoe)
• #​4538: chore: Included githubactions in the dependabot config (@​naveensrinivasan)
• #​4546: Adapt Node versions on CI to prepare for v3 (@​lukastaegert)
• #​4556: Improve error message for invalid patterns (@​DysphoricUnicorn)
• #​4559: Update dependencies (@​lukastaegert)
• #​4560: Bump peter-evans/create-or-update-comment from 1 to 2 (@​dependabot)
• #​4561: Bump peter-evans/find-comment from 1 to 2 (@​dependabot)
• #​4562: Bump codecov/codecov-action from 1 to 3 (@​dependabot)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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, click this checkbox.

---

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