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

renovate · 2022-02-21T01:10:58Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@changesets/cli	`^2.20.0` -> `^2.21.0`
@fontsource/fira-mono	`^4.5.2` -> `^4.5.3`
@sveltejs/kit	`^1.0.0-next.267` -> `^1.0.0-next.278`
@typescript-eslint/eslint-plugin	`^5.11.0` -> `^5.12.0`
@typescript-eslint/parser	`^5.11.0` -> `^5.12.0`
carbon-components-svelte	`^0.58.2` -> `^0.58.3`
esbuild	`^0.14.21` -> `^0.14.23`
eslint-config-prettier	`^8.3.0` -> `^8.4.0`
eslint-plugin-jest	`^26.1.0` -> `^26.1.1`
express (source)	`^4.17.2` -> `^4.17.3`
playwright-core (source)	`^1.19.0` -> `^1.19.1`
pnpm (source)	`^6.30.1` -> `^6.31.0`
rollup (source)	`^2.67.2` -> `^2.67.3`
sass	`^1.49.7` -> `^1.49.8`
vite	`^2.8.1` -> `^2.8.4`
vite-plugin-windicss	`^1.7.0` -> `^1.7.1`

Release Notes

changesets/changesets

`v2.21.0`

Compare Source

Minor Changes

#690 27a5a82 Thanks @Andarist! - Added a new .changeset/config.json option: fixed. It can be used to group packages that should always be released together. If any package from a group is going to be released then all packages from that group will be released together (with the same version).

This is similar to what people often know from Lerna as this is how their fixed/locked mode works.

Patch Changes

#706 0812858 Thanks @Andarist! - Fixed an issue with "none" releases causing package versions being bumped during snapshot releases. In addition to when you create "none" release types explicitly Changesets might create them implicitly in some situations, for example under some circumstances this issue caused snapshot releases to be created sometimes for ignored packages.

#703 15c461d Thanks @Andarist! - Fixed an issue with * dependency ranges not being replaced in premode. Those have to replaced with exact versions because prereleases don't satisfy wildcard ranges. A published prerelease package with such dependency range left untouched won't install correct prerelease dependency version.

#749 d14cf79 Thanks @Andarist! - Fixed an issue that caused created CHANGELOG files not being formatted in the same way as the updated ones (this could happen when calling changeset version for the very first time for a package).

#751 59c7ebc Thanks @Rugvip! - Fixed an issue where dependent packages would sometimes not get bumped properly when exiting prerelease mode.

#703 15c461d Thanks @Andarist! - Fixed an issue with dependant packages being always bumped when their * dependency was bumped.
Updated dependencies [0812858, 15c461d, 27a5a82, 27a5a82, d14cf79, 27a5a82, 0d1debd, 59c7ebc, 15c461d]:
- @changesets/assemble-release-plan @5.1.0
- @changesets/apply-release-plan @5.0.5
- @changesets/types @4.1.0
- @changesets/config @1.7.0
- @changesets/changelog-git @0.1.10
- @changesets/get-release-plan @3.0.6
- @changesets/get-dependents-graph @1.3.1
- @changesets/git @1.3.1
- @changesets/pre @1.0.10
- @changesets/read @0.5.4
- @changesets/write @0.1.7

typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)

`v5.12.0`

Compare Source

Bug Fixes

eslint-plugin: [init-declarations] fix nested namespace (#4544) (fe910e6)
eslint-plugin: [no-unnecessary-type-arguments] Use Symbol to check if it's the same type (#4543) (5b7d8df)
support nested object deconstructuring with type annotation (#4548) (4da9278)

Features

add checking property definition for allowNames option (#4542) (e32bef6)

typescript-eslint/typescript-eslint (@typescript-eslint/parser)

`v5.12.0`

Compare Source

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

carbon-design-system/carbon-components-svelte

`v0.58.3`

Compare Source

Fixes

correctly set deprecation comments for deprecated components
TextInput and PasswordInput should render label if "labelText" slot is used
PasswordInput should not render label if no labelText is provided
StructuredList overflow-y should not be "hidden"
MultiSelect should not prevent default key behavior when open
Switch should have type="button"

evanw/esbuild

`v0.14.23`

Compare Source

Update feature database to indicate that node 16.14+ supports import assertions (#2030)

Node versions 16.14 and above now support import assertions according to these release notes. This release updates esbuild's internal feature compatibility database with this information, so esbuild no longer strips import assertions with --target=node16.14:
```
// Original code
import data from './package.json' assert { type: 'json' }
console.log(data)

// Old output (with --target=node16.14)
import data from "./package.json";
console.log(data);

// New output (with --target=node16.14)
import data from "./package.json" assert { type: "json" };
console.log(data);
```
Basic support for CSS @layer rules (#2027)

This adds basic parsing support for a new CSS feature called @layer that changes how the CSS cascade works. Adding parsing support for this rule to esbuild means esbuild can now minify the contents of @layer rules:
```
/* Original code */
@&#8203;layer a {
  @&#8203;layer b {
    div {
      color: yellow;
      margin: 0.0px;
    }
  }
}

/* Old output (with --minify) */
@&#8203;layer a{@&#8203;layer b {div {color: yellow; margin: 0px;}}}

/* New output (with --minify) */
@&#8203;layer a.b{div{color:#ff0;margin:0}}
```
You can read more about @layer here:
- Documentation: https://developer.mozilla.org/en-US/docs/Web/CSS/[@layer](https://github.com/layer)
- Motivation: https://developer.chrome.com/blog/cascade-layers/
Note that the support added in this release is only for parsing and printing @layer rules. The bundler does not yet know about these rules and bundling with @layer may result in behavior changes since these new rules have unusual ordering constraints that behave differently than all other CSS rules. Specifically the order is derived from the first instance while with every other CSS rule, the order is derived from the last instance.

`v0.14.22`

Compare Source

Preserve whitespace for token lists that look like CSS variable declarations (#2020)

Previously esbuild removed the whitespace after the CSS variable declaration in the following CSS:
```
/* Original input */
@&#8203;supports (--foo: ){html{background:green}}

/* Previous output */
@&#8203;supports (--foo:){html{background:green}}
```
However, that broke rendering in Chrome as it caused Chrome to ignore the entire rule. This did not break rendering in Firefox and Safari, so there's a browser bug either with Chrome or with both Firefox and Safari. In any case, esbuild now preserves whitespace after the CSS variable declaration in this case.

Ignore legal comments when merging adjacent duplicate CSS rules (#2016)

This release now generates more compact minified CSS when there are legal comments in between two adjacent rules with identical content:

/* Original code */
a { color: red }
/* @&#8203;preserve */
b { color: red }

/* Old output (with --minify) */
a{color:red}/* @&#8203;preserve */b{color:red}

/* New output (with --minify) */
a,b{color:red}/* @&#8203;preserve */

Block onResolve and onLoad until onStart ends (#1967)

This release changes the semantics of the onStart callback. All onStart callbacks from all plugins are run concurrently so that a slow plugin doesn't hold up the entire build. That's still the case. However, previously the only thing waiting for the onStart callbacks to finish was the end of the build. This meant that onResolve and/or onLoad callbacks could sometimes run before onStart had finished. This was by design but violated user expectations. With this release, all onStart callbacks must finish before any onResolve and/or onLoad callbacks are run.
Add a self-referential default export to the JS API (#1897)

Some people try to use esbuild's API using import esbuild from 'esbuild' instead of import * as esbuild from 'esbuild' (i.e. using a default import instead of a namespace import). There is no default export so that wasn't ever intended to work. But it would work sometimes depending on which tools you used and how they were configured so some people still wrote code this way. This release tries to make that work by adding a self-referential default export that is equal to esbuild's module namespace object.

More detail: The published package for esbuild's JS API is in CommonJS format, although the source code for esbuild's JS API is in ESM format. The original ESM code for esbuild's JS API has no export named default so using a default import like this doesn't work with Babel-compatible toolchains (since they respect the semantics of the original ESM code). However, it happens to work with node-compatible toolchains because node's implementation of importing CommonJS from ESM broke compatibility with existing conventions and automatically creates a default export which is set to module.exports. This is an unfortunate compatibility headache because it means the default import only works sometimes. This release tries to fix this by explicitly creating a self-referential default export. It now doesn't matter if you do esbuild.build(), esbuild.default.build(), or esbuild.default.default.build() because they should all do the same thing. Hopefully this means people don't have to deal with this problem anymore.
Handle write errors when esbuild's child process is killed (#2007)

If you type Ctrl+C in a terminal when a script that uses esbuild's JS library is running, esbuild's child process may be killed before the parent process. In that case calls to the write() syscall may fail with an EPIPE error. Previously this resulted in an uncaught exception because esbuild didn't handle this case. Starting with this release, esbuild should now catch these errors and redirect them into a general The service was stopped error which should be returned from whatever top-level API calls were in progress.
Better error message when browser WASM bugs are present (#1863)

Safari's WebAssembly implementation appears to be broken somehow, at least when running esbuild. Sometimes this manifests as a stack overflow and sometimes as a Go panic. Previously a Go panic resulted in the error message Can't find variable: fs but this should now result in the Go panic being printed to the console. Using esbuild's WebAssembly library in Safari is still broken but now there's a more helpful error message.

More detail: When Go panics, it prints a stack trace to stderr (i.e. file descriptor 2). Go's WebAssembly shim calls out to node's fs.writeSync() function to do this, and it converts calls to fs.writeSync() into calls to console.log() in the browser by providing a shim for fs. However, Go's shim code stores the shim on window.fs in the browser. This is undesirable because it pollutes the global scope and leads to brittle code that can break if other code also uses window.fs. To avoid this, esbuild shadows the global object by wrapping Go's shim. But that broke bare references to fs since the shim is no longer stored on window.fs. This release now stores the shim in a local variable named fs so that bare references to fs work correctly.
Undo incorrect dead-code elimination with destructuring (#1183)

Previously esbuild eliminated these statements as dead code if tree-shaking was enabled:
```
let [a] = {}
let { b } = null
```
This is incorrect because both of these lines will throw an error when evaluated. With this release, esbuild now preserves these statements even when tree shaking is enabled.
Update to Go 1.17.7

The version of the Go compiler used to compile esbuild has been upgraded from Go 1.17.6 to Go 1.17.7, which contains a few compiler and security bug fixes.

prettier/eslint-config-prettier

`v8.4.0`

Compare Source

Added: [vue/quote-props]. Thanks to @xcatliu!

jest-community/eslint-plugin-jest

`v26.1.1`

Compare Source

Bug Fixes

docs: use the correct function name (#1056) (7435556)

expressjs/express

`v4.17.3`

Compare Source

===================

deps: accepts@~1.3.8
- deps: mime-types@~2.1.34
- deps: [email protected]
deps: [email protected]
- deps: [email protected]
- deps: [email protected]
- deps: [email protected]
deps: [email protected]
deps: [email protected]
- Fix handling of __proto__ keys
pref: remove unnecessary regexp for trust proxy

Microsoft/playwright

`v1.19.1`

Compare Source

Highlights

This patch includes the following bug fixes:

https://github.com/microsoft/playwright/issues/12075 - [Question] After update to 1.19 firefox fails to runhttps://github.com/microsoft/playwright/issues/120900 - [BUG] did something change on APIRequest/Response APIs ?

Browser Versions

Chromium 100.0.4863.0
Mozilla Firefox 96.0.1
WebKit 15.4

This version was also tested against the following stable channels:

Google Chrome 98
Microsoft Edge 98

pnpm/pnpm

`v6.31.0`

Compare Source

Minor Changes

Added --shell-mode/-c option support to pnpm exec #4328

--shell-mode: shell interpreter. See: https://github.com/sindresorhus/execa/tree/484f28de7c35da5150155e7a523cbb20de161a4f#shell

Usage example:

pnpm -r --shell-mode exec -- echo \"\$PNPM_PACKAGE_NAME\"
pnpm -r -c exec -- echo \"\$PNPM_PACKAGE_NAME\"

{
  "scripts": {
    "check": " pnpm -r --shell-mode exec -- echo \"\\$PNPM_PACKAGE_NAME\""
  }
}

Patch Changes

Remove meaningless keys from publishConfig when the pack or publish commands are used #4311
The pnpx, pnpm dlx, pnpm create, and pnpm exec commands should set the npm_config_user_agent env variable #3985.

What's Changed

fix: the dlx and create commands should set npm_config_user_agent by @zkochan in https://github.com/pnpm/pnpm/pull/4317
refactor(publish): remove meaningless key in publishConfig by @BlackHole1 in https://github.com/pnpm/pnpm/pull/4334
feat(exec): support shell interpreter by @BlackHole1 in https://github.com/pnpm/pnpm/pull/4328

New Contributors

@BlackHole1 made their first contribution in https://github.com/pnpm/pnpm/pull/4334

Full Changelog: pnpm/pnpm@v6.30.1...v6.31.0

rollup/rollup

`v2.67.3`

Compare Source

2022-02-18

Bug Fixes

Do not swallow other errors when unfinished hook actions are detected (#4409)
Add additional information to output when there are unfinished hook actions (#4409)

Pull Requests

#4399: docs: remove const (@TrickyPi)
#4401: Improve test stability by getting independent of module id ordering in more places (@lukastaegert)
#4403: fix: remove unnecessary property descriptor spread (@dnalborczyk)
#4404: refactor: use map for import descriptions + re-export descriptions (@dnalborczyk)
#4405: refactor: module exports to map (@dnalborczyk)
#4406: Fix a typo in 'Direct plugin communication' code example (@younesmln)
#4407: Document how resolveId is cached (@lukastaegert)
#4409: Print ids for unfinished moduleParsed and shouldTransformCachedModule hooks (@lukastaegert)

sass/dart-sass

`v1.49.8`

Compare Source

Fixed a bug where some plain CSS imports would not be emitted.

JS API

Fix a bug where inspecting the Sass module in the Node.js console crashed on
Node 17.

Embedded Sass

Fix a bug where source map URLs were incorrectly generated when passing
importers to the legacy API.

vitejs/vite

`v2.8.4`

Compare Source

Bug Fixes

don't replace NODE_ENV in vite:client-inject (#6935) (2b70003)
normalize postcss dependency messages (#6959) (3f3f473)
revert #6935, bypass replacing process.env.NODE_ENV in ssr (#6970) (b8218b0)

`v2.8.3`

Compare Source

Bug Fixes

revert update dotenv-expand #6703, fix #6858 (#6934) (a9a1ae2)

`v2.8.2`

Compare Source

Features

custom manifest file name (#6667) (e385346)
make import.meta.glob and import.meta.globEager generic (#5073) (78e84c8)

Performance Improvements

improve isFileReadable performance (#6868) (62cbe68)
lazy import preview function (#6898) (2eabcb9)

antfu/vite-plugin-windicss

`v1.7.1`

Compare Source

Features

check name2 and value not to be undefined (#279) (bd2738f)

Configuration

📅 Schedule: "before 3am on Monday" (UTC).

🚦 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 WhiteSource Renovate. View repository job log here.

chore(deps): update all non-major dependencies

52780d2

renovate bot added the dependencies label Feb 21, 2022

dominikg approved these changes Feb 21, 2022

View reviewed changes

bluwy approved these changes Feb 21, 2022

View reviewed changes

bluwy merged commit 3107bf0 into main Feb 21, 2022

bluwy deleted the renovate/all-minor-patch branch February 21, 2022 04:27

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

renovate bot commented Feb 21, 2022

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

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

Conversation

renovate bot commented Feb 21, 2022

Release Notes

Minor Changes

Patch Changes

Bug Fixes

Features

Bug Fixes

Highlights

Browser Versions

Minor Changes

Patch Changes

What's Changed

New Contributors

Bug Fixes

Pull Requests

JS API

Embedded Sass

Bug Fixes

Bug Fixes

Features

Performance Improvements

Features

Configuration