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

renovate · 2022-10-02T10:03:26Z

This PR contains the following updates:

Package	Change	Type	Update
@suger-tdy/eslint-config	`1.1.11` -> `1.1.12`	devDependencies	patch
@vitejs/plugin-vue (source)	`3.1.0` -> `3.2.0`	devDependencies	minor
actions/setup-node	`v3.4.1` -> `v3.5.1`	action	minor
esbuild	`0.15.9` -> `0.15.12`	devDependencies	patch
eslint (source)	`8.24.0` -> `8.26.0`	devDependencies	minor
pnpm (source)	`7.12.2` -> `7.14.0`	packageManager	minor
pnpm/action-setup	`v2.2.2` -> `v2.2.4`	action	patch
typescript (source)	`4.8.3` -> `4.8.4`	devDependencies	patch
unbuild	`0.8.11` -> `0.9.4`	devDependencies	minor
unplugin	`^0.9.0` -> `^0.10.0`	dependencies	minor
vite (source)	`3.1.3` -> `3.2.0`	devDependencies	minor
vite-plugin-inspect	`0.7.2` -> `0.7.5`	devDependencies	patch
vitest	`0.23.4` -> `0.24.3`	devDependencies	minor
vue (source)	`3.2.39` -> `3.2.41`	dependencies	patch

Release Notes

vitejs/vite (@vitejs/plugin-vue)

`v3.2.0`

Compare Source

chore(deps): update all non-major dependencies (#10393) (f519423), closes #10393
chore(deps): update all non-major dependencies (#10488) (15aa827), closes #10488
fix(plugin-vue): enable ts in template when using tsx in dev mode (#10180) (a9f9d31), closes #10180
docs: add missing binding in asset import example (#10414) (d7ac96d), closes #10414

`v3.1.2`

Compare Source

Please refer to CHANGELOG.md for details.

`v3.1.1`

Compare Source

Please refer to CHANGELOG.md for details.

actions/setup-node

`v3.5.1`

Compare Source

In scope of this release we updated actions/core to 1.10.0. Moreover, we added logic to print Nodejs, Npm, Yarn versions after installation.

`v3.5.0`

Compare Source

In scope of this release we add support for engines.node. The action will be able to grab the version form package.json#engines.node. https://github.com/actions/setup-node/pull/485. Moreover, we added support for Volta

Besides, we updated @actions/core to 1.9.1 and @actions/cache to 3.0.4

evanw/esbuild

`v0.15.12`

Compare Source

Fix minifier correctness bug with single-use substitutions (#2619)

When minification is enabled, esbuild will attempt to eliminate variables that are only used once in certain cases. For example, esbuild minifies this code:
```
function getEmailForUser(name) {
  let users = db.table('users');
  let user = users.find({ name });
  let email = user?.get('email');
  return email;
}
```
into this code:
```
function getEmailForUser(e){return db.table("users").find({name:e})?.get("email")}
```
However, this transformation had a bug where esbuild did not correctly consider the "read" part of binary read-modify-write assignment operators. For example, it's incorrect to minify the following code into bar += fn() because the call to fn() might modify bar:
```
const foo = fn();
bar += foo;
```
In addition to fixing this correctness bug, this release also improves esbuild's output in the case where all values being skipped over are primitives:
```
function toneMapLuminance(r, g, b) {
  let hdr = luminance(r, g, b)
  let decay = 1 / (1 + hdr)
  return 1 - decay
}
```
Previous releases of esbuild didn't substitute these single-use variables here, but esbuild will now minify this to the following code starting with this release:
```
function toneMapLuminance(e,n,a){return 1-1/(1+luminance(e,n,a))}
```

`v0.15.11`

Compare Source

Fix various edge cases regarding template tags and this (#2610)

This release fixes some bugs where the value of this wasn't correctly preserved when evaluating template tags in a few edge cases. These edge cases are listed below:

async function test() {
  class Foo { foo() { return this } }
  class Bar extends Foo {
    a = async () => super.foo``
    b = async () => super['foo']``
    c = async (foo) => super[foo]``
  }
  function foo() { return this }
  const obj = { foo }
  const bar = new Bar
  console.log(
    (await bar.a()) === bar,
    (await bar.b()) === bar,
    (await bar.c('foo')) === bar,
    { foo }.foo``.foo === foo,
    (true && obj.foo)`` !== obj,
    (false || obj.foo)`` !== obj,
    (null ?? obj.foo)`` !== obj,
  )
}
test()

Each edge case in the code above previously incorrectly printed false when run through esbuild with --minify --target=es6 but now correctly prints true. These edge cases are unlikely to have affected real-world code.

`v0.15.10`

Compare Source

Add support for node's "pattern trailers" syntax (#2569)

After esbuild implemented node's exports feature in package.json, node changed the feature to also allow text after * wildcards in patterns. Previously the * was required to be at the end of the pattern. It lets you do something like this:
```
{
  "exports": {
    "./features/*": "./features/*.js",
    "./features/*.js": "./features/*.js"
  }
}
```
With this release, esbuild now supports these types of patterns too.
Fix subpath imports with Yarn PnP (#2545)

Node has a little-used feature called subpath imports which are package-internal imports that start with # and that go through the imports map in package.json. Previously esbuild had a bug that caused esbuild to not handle these correctly in packages installed via Yarn's "Plug'n'Play" installation strategy. The problem was that subpath imports were being checked after Yarn PnP instead of before. This release reorders these checks, which should allow subpath imports to work in this case.
Link from JS to CSS in the metafile (#1861, #2565)

When you import CSS into a bundled JS file, esbuild creates a parallel CSS bundle next to your JS bundle. So if app.ts imports some CSS files and you bundle it, esbuild will give you app.js and app.css. You would then add both <script src="app.js"></script> and <link href="app.css" rel="stylesheet"> to your HTML to include everything in the page. This approach is more efficient than having esbuild insert additional JavaScript into app.js that downloads and includes app.css because it means the browser can download and parse both the CSS and the JS in parallel (and potentially apply the CSS before the JS has even finished downloading).

However, sometimes it's difficult to generate the <link> tag. One case is when you've added [hash] to the entry names setting to include a content hash in the file name. Then the file name will look something like app-GX7G2SBE.css and may change across subsequent builds. You can tell esbuild to generate build metadata using the metafile API option but the metadata only tells you which generated JS bundle corresponds to a JS entry point (via the entryPoint property), not which file corresponds to the associated CSS bundle. Working around this was hacky and involved string manipulation.

This release adds the cssBundle property to the metafile to make this easier. It's present on the metadata for the generated JS bundle and points to the associated CSS bundle. So to generate the HTML tags for a given JS entry point, you first find the output file with the entryPoint you are looking for (and put that in a <script> tag), then check for the cssBundle property to find the associated CSS bundle (and put that in a <link> tag).

One thing to note is that there is deliberately no jsBundle property mapping the other way because it's not a 1:1 relationship. Two JS bundles can share the same CSS bundle in the case where the associated CSS bundles have the same name and content. In that case there would be no one value for a hypothetical jsBundle property to have.

eslint/eslint

`v8.26.0`

Compare Source

Features

4715787 feat: check Object.create() in getter-return (#16420) (Yuki Hirasawa)
28d1902 feat: no-implicit-globals supports exported block comment (#16343) (Sosuke Suzuki)
e940be7 feat: Use ESLINT_USE_FLAT_CONFIG environment variable for flat config (#16356) (Tomer Aberbach)
dd0c58f feat: Swap out Globby for custom globbing solution. (#16369) (Nicholas C. Zakas)

Bug Fixes

df77409 fix: use baseConfig constructor option in FlatESLint (#16432) (Milos Djermanovic)
33668ee fix: Ensure that glob patterns are matched correctly. (#16449) (Nicholas C. Zakas)
740b208 fix: ignore messages without a ruleId in getRulesMetaForResults (#16409) (Francesco Trotta)
8f9759e fix: --ignore-pattern in flat config mode should be relative to cwd (#16425) (Milos Djermanovic)
325ad37 fix: make getRulesMetaForResults return a plain object in trivial case (#16438) (Francesco Trotta)
a2810bc fix: Ensure that directories can be unignored. (#16436) (Nicholas C. Zakas)
35916ad fix: Ensure unignore and reignore work correctly in flat config. (#16422) (Nicholas C. Zakas)

Documentation

651649b docs: Core concepts page (#16399) (Ben Perlmutter)
631cf72 docs: note --ignore-path not supported with flat config (#16434) (Andy Edwards)
1692840 docs: fix syntax in examples for new config files (#16427) (Milos Djermanovic)
d336cfc docs: Document extending plugin with new config (#16394) (Ben Perlmutter)

Chores

e917a9a ci: add node v19 (#16443) (Koichi ITO)
4b70b91 chore: Add VS Code issues link (#16423) (Nicholas C. Zakas)
232d291 chore: suppress a Node.js deprecation warning (#16398) (Koichi ITO)

`v8.25.0`

Compare Source

Features

173e820 feat: Pass --max-warnings value to formatters (#16348) (Brandon Mills)
6964cb1 feat: remove support for ignore files in FlatESLint (#16355) (Milos Djermanovic)
1cc4b3a feat: id-length counts graphemes instead of code units (#16321) (Sosuke Suzuki)

Documentation

90c6028 docs: Conflicting fixes (#16366) (Ben Perlmutter)
5a3fe70 docs: Add VS to integrations page (#16381) (Maria José Solano)
49bd1e5 docs: remove unused link definitions (#16376) (Nick Schonning)
3bd380d docs: typo cleanups for docs (#16374) (Nick Schonning)
b3a0837 docs: remove duplicate words (#16378) (Nick Schonning)
a682562 docs: add BigInt to new-cap docs (#16362) (Sosuke Suzuki)
f6d57fb docs: Update docs README (#16352) (Ben Perlmutter)
7214347 docs: fix logical-assignment-operators option typo (#16346) (Jonathan Wilsson)

Chores

1f78594 chore: upgrade @eslint/eslintrc @1.3.3 (#16397) (Milos Djermanovic)
8476a9b chore: Remove CODEOWNERS (#16375) (Nick Schonning)
720ff75 chore: use "ci" for Dependabot commit message (#16377) (Nick Schonning)
42f5479 chore: bump actions/stale from 5 to 6 (#16350) (dependabot[bot])
e5e9e27 chore: remove jsdoc dev dependency (#16344) (Milos Djermanovic)

pnpm/pnpm

`v7.14.0`

Compare Source

Minor Changes

Add pnpm doctor command to do checks for known common issues

Patch Changes

Ignore the always-auth setting.

pnpm will never reuse the registry auth token for requesting the package tarball, if the package tarball is hosted on a different domain.

So, for example, if your registry is at https://company.registry.com/ but the tarballs are hosted at https://tarballs.com/, then you will have to configure the auth token for both domains in your .npmrc:
```
@&#8203;my-company:registry=https://company.registry.com/
//company.registry.com/=SOME_AUTH_TOKEN
//tarballs.com/=SOME_AUTH_TOKEN
```

Our Gold Sponsors

Our Silver Sponsors

`v7.13.6`

Compare Source

Patch Changes

Downgrade @pnpm/npm-conf to remove annoying builtin warning #5518.
pnpm link --global <pkg> should not change the type of the dependency #5478.
When the pnpm outdated command fails, print in which directory it failed.

Our Gold Sponsors

Our Silver Sponsors

`v7.13.5`

Compare Source

Patch Changes

Print a warning when cannot read the built-in npm configuration.
Also include missing deeply linked workspace packages at headless installation #5034.
pnpm outdated should work when the package tarballs are hosted on a domain that differs from the registry's domain #5492.
strict-peer-dependencies is set to false by default.

Our Gold Sponsors

Our Silver Sponsors

`v7.13.4`

Compare Source

Patch Changes

pnpm link <pkg> --global should work when a custom target directory is specified with the --dir CLI option #5473.
It should be possible to override dependencies with local packages using overrides #5443.

Our Gold Sponsors

Our Silver Sponsors

`v7.13.3`

Compare Source

Patch Changes

Don't crash when auto-install-peers is set to true and installation is done on a workspace with that has the same dependencies in multiple projects #5454.
Add global option in pnpm link --help #5461.
Show execution time on install, update, add, and remove #1021.
Fix the return path of pnpm pack, when a custom destination directory is used #5471.

Our Gold Sponsors

Our Silver Sponsors

`v7.13.2`

Compare Source

Patch Changes

When linking commands to a directory, remove any .exe files that are already present in that target directory by the same name.

This fixes an issue with pnpm global update on Windows. If pnpm was installed with the standalone script and then updated with pnpm using pnpm add --global pnpm, the exe file initially created by the standalone script should be removed.
When a direct dependency fails to resolve, print the path to the project directory in the error message.
pnpm patch-commit should work when the patch directory is specified with a trailing slash #5449.

Our Gold Sponsors

Our Silver Sponsors

`v7.13.1`

Compare Source

Patch Changes

pnpm update --interactive should not list dependencies ignored via the pnpm.updateConfig.ignoreDependencies setting.

Our Gold Sponsors

Our Silver Sponsors

`v7.13.0`

Compare Source

Minor Changes

Ignore packages listed in package.json > pnpm.updateConfig.ignoreDependencies fields on update/outdated command #5358

For instance, if you don't want webpack automatically to be updated when you run pnpm update --latest, put this to your package.json:
```
{
  "pnpm": {
    "updateConfig": {
      "ignoreDependencies": ["webpack"]
    }
  }
}
```
Patterns are also supported, so you may ignore for instance any packages from a scope: @babel/*.
It is possible now to update all dependencies except the listed ones using !. For instance, update all dependencies, except lodash:
```
  pnpm update !lodash
```
It also works with pattends, for instance:
```
  pnpm update !@&#8203;babel/*
```
And it may be combined with other patterns:
```
  pnpm update @&#8203;babel/* !@&#8203;babel/core
```

Patch Changes

Hooks should be applied on pnpm deploy #5306.
Stop --filter-prod option to run command on all the projects when used on workspace. --filter-prod option now only filter from dependencies and omit devDependencies instead of including all the packages when used on workspace. So what was happening is that if you use --filter-prod on workspace root like this:
```
pnpm --filter-prod ...build-modules exec node -e 'console.log(require(`./package.json`).name)'
```
it was printing all the package of workspace, where it should only print the package name of itself and packages where it has been added as dependency (not as devDependencies)
Don't override the root dependency when auto installing peer dependencies #5412.

Our Gold Sponsors

Our Silver Sponsors

What's Changed

GitHub Workflows security hardening by @sashashuhttps://github.com/pnpm/pnpm/pull/5405l/5405
feat: merge readPackage hook from opts and pnpmfile by @AGrzhttps://github.com/pnpm/pnpm/pull/5403l/5403
feat: excluding deps from update by @zkochhttps://github.com/pnpm/pnpm/pull/5432l/5432
fix: dir path repeated join in link global by @lvhttps://github.com/pnpm/pnpm/pull/5434l/5434
fix: filter-prod flag including all workspace pkgs by @noorulhhttps://github.com/pnpm/pnpm/pull/5437l/5437
Feature: ignore packages listed in package.json > pnpm.updateConfig.ignoreDependencies on update/outdated commands by @Shinyaigehttps://github.com/pnpm/pnpm/pull/5408l/5408
fix: don't override root deps when auto installing peers by @zkochhttps://github.com/pnpm/pnpm/pull/5442l/5442