chore(deps): update all non-major dependencies #106

renovate · 2022-08-19T00:45:40Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
esbuild	`^0.15.5` -> `^0.15.6`
hookable	`^5.1.1` -> `^5.2.2`
magic-string	`^0.26.2` -> `^0.26.3`
mlly	`^0.5.13` -> `^0.5.14`
pkg-types	`^0.3.3` -> `^0.3.4`
pnpm (source)	`7.9.3` -> `7.9.5`
rollup (source)	`^2.78.0` -> `^2.79.0`
rollup-plugin-esbuild	`^4.9.3` -> `^4.10.1`
typescript (source)	`^4.7.4` -> `^4.8.2`
untyped	`^0.4.5` -> `^0.4.7`

Release Notes

evanw/esbuild

`v0.15.6`

Compare Source

Lower for await loops (#1930)

This release lowers for await loops to the equivalent for loop containing await when esbuild is configured such that for await loops are unsupported. This transform still requires at least generator functions to be supported since esbuild's lowering of await currently relies on generators. This new transformation is mostly modeled after what the TypeScript compiler does. Here's an example:

async function f() {
  for await (let x of y)
    x()
}

The code above will now become the following code with --target=es2017 (omitting the code for the __forAwait helper function):

async function f() {
  try {
    for (var iter = __forAwait(y), more, temp, error; more = !(temp = await iter.next()).done; more = false) {
      let x = temp.value;
      x();
    }
  } catch (temp) {
    error = [temp];
  } finally {
    try {
      more && (temp = iter.return) && await temp.call(iter);
    } finally {
      if (error)
        throw error[0];
    }
  }
}

Automatically fix invalid supported configurations (#2497)

The --target= setting lets you tell esbuild to target a specific version of one or more JavaScript runtimes such as chrome80,node14 and esbuild will restrict its output to only those features supported by all targeted JavaScript runtimes. More recently, esbuild introduced the --supported: setting that lets you override which features are supported on a per-feature basis. However, this now lets you configure nonsensical things such as --supported:async-await=false --supported:async-generator=true. Previously doing this could result in esbuild building successfully but producing invalid output.

Starting with this release, esbuild will now attempt to automatically fix nonsensical feature override configurations by introducing more overrides until the configuration makes sense. So now the configuration from previous example will be changed such that async-await=false implies async-generator=false. The full list of implications that were introduced is below:
- async-await=false implies:
  - async-generator=false
  - for-await=false
  - top-level-await=false
- generator=false implies:
  - async-generator=false
- object-accessors=false implies:
  - class-private-accessor=false
  - class-private-static-accessor=false
- class-field=false implies:
  - class-private-field=false
- class-static-field=false implies:
  - class-private-static-field=false
- class=false implies:
  - class-field=false
  - class-private-accessor=false
  - class-private-brand-check=false
  - class-private-field=false
  - class-private-method=false
  - class-private-static-accessor=false
  - class-private-static-field=false
  - class-private-static-method=false
  - class-static-blocks=false
  - class-static-field=false
Implement a small minification improvement (#2496)

Some people write code that contains a label with an immediate break such as x: break x. Previously this code was not removed during minification but it will now be removed during minification starting with this release.
Fix installing esbuild via Yarn with enableScripts: false configured (#2457)

If esbuild is installed with Yarn with the enableScripts: false setting configured, then Yarn will not "unplug" the esbuild package (i.e. it will keep the entire package inside a .zip file). This messes with esbuild's library code that extracts the platform-specific binary executable because that code copies the binary executable into the esbuild package directory, and Yarn's .zip file system shim doesn't let you write to a directory inside of a .zip file. This release fixes this problem by writing to the node_modules/.cache/esbuild directory instead in this case. So you should now be able to use esbuild with Yarn when enableScripts: false is configured.

This fix was contributed by @jonaskuske.

unjs/hookable

Features

add beforeEach and afterEach spies (#46) (949d8b7)

Bug Fixes

deprecate hooks doesn't have to be passed all hooks (#48) (0c4fef0)

5.1.2 (2022-08-23)

Bug Fixes

handle deprecated hooks after being registred (23d9ff4)

5.1.1 (2021-12-21)

Bug Fixes

always return caller result (e9c51df)

`v5.1.2`

Compare Source

rich-harris/magic-string

`v0.26.3`

Compare Source

Performance Improvements

delay guess encoded (#216) (69b13c7)

unjs/mlly

`v0.5.14`

Compare Source

unjs/pkg-types

`v0.3.4`

Compare Source

pnpm/pnpm

`v7.9.5`

Compare Source

Patch Changes

Set NODE_PATH when prefer-symlinked-executables is enabled #5251.
Fail with a meaningful error when the audit endpoint doesn't exist #5200.
Symlink a local dependency to node_modules, even if the target directory doesn't exist #5219.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

Fix pnpm audit bad API response on private registry by @timtong19https://github.com/pnpm/pnpm/pull/5246l/5246
fix: set NODE_PATH when is turned on by @d3https://github.com/pnpm/pnpm/pull/5251l/5251
fix: symlink local dep even when target dir does not exist by @zkochhttps://github.com/pnpm/pnpm/pull/5253l/5253
fix: only set extraEnv for preferSymlinkedExecutables if it's not windows by @d3https://github.com/pnpm/pnpm/pull/5256l/5256

New Contributors

@timtong1982 made their first contributihttps://github.com/pnpm/pnpm/pull/5246l/5246

Full Changelog: pnpm/pnpm@v7.9.4...v7.9.5

`v7.9.4`

Compare Source

Patch Changes

Auto install peer dependencies when auto-install-peers is set to true and the lockfile is up to date #5213.
pnpm env: for Node.js<16 install the x64 build on Darwin ARM as ARM build is not available #5239.
pnpm env: log a message when the node.js tarball starts the download #5241.
Fix pnpm install --merge-git-branch-lockfile when the lockfile is up to date #5212.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

feat(cafs): extend cafs with getFilePathByModeInCafs by @d3https://github.com/pnpm/pnpm/pull/5232l/5232
fix: mergeGitBranchLockfiles when merged lockfile is up-to-date by @chengcybhttps://github.com/pnpm/pnpm/pull/5233l/5233
test: all test packages should be from the @pnpm.e2e scope by @&#8203https://github.com/pnpm/pnpm/pull/5211pm/pull/5211
fix: node<16 download fail on arm chips on macos by @ambar-arkhttps://github.com/pnpm/pnpm/pull/5239l/5239
feat(env): show state on fetching node by @JacobLinCohttps://github.com/pnpm/pnpm/pull/5241l/5241
Fix: install peerDeps which is not optional on headless install by @Shinyaigehttps://github.com/pnpm/pnpm/pull/5243l/5243