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

renovate · 2024-04-21T02:21:25Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@rollup/plugin-node-resolve (source)	`^15.2.3` -> `^15.3.0`
@types/node (source)	`^20.12.7` -> `^20.17.6`
@vitest/coverage-v8 (source)	`^1.5.0` -> `^1.6.0`
@webassemblyjs/helper-wasm-bytecode	`1.12.1` -> `1.14.1`
@webassemblyjs/ieee754 (source)	`1.12.1` -> `1.14.1`
@webassemblyjs/leb128 (source)	`1.12.1` -> `1.14.1`
@webassemblyjs/utf8	`1.12.1` -> `1.14.1`
@webassemblyjs/wasm-parser	`^1.12.1` -> `^1.14.1`
assemblyscript (source)	`^0.27.27` -> `^0.27.30`
automd	`^0.3.7` -> `^0.3.12`
changelogen	`^0.5.5` -> `^0.5.7`
esbuild	`^0.20.2` -> `^0.24.0`
eslint (source)	`^8.57.0` -> `^8.57.1`
eslint-config-unjs	`^0.2.1` -> `^0.4.1`
jiti	`^1.21.0` -> `^1.21.6`
magic-string	`^0.30.9` -> `^0.30.12`
miniflare (source)	`^3.20240405.1` -> `^3.20241106.0`
mlly	`^1.6.1` -> `^1.7.2`
pkg-types	`^1.0.3` -> `^1.2.1`
pnpm (source)	`9.0.5` -> `9.12.3`
prettier (source)	`^3.2.5` -> `^3.3.3`
rollup (source)	`^4.14.2` -> `^4.25.0`
typescript (source)	`^5.4.5` -> `^5.6.3`
unplugin	`^1.10.1` -> `^1.15.0`
vite (source)	`^5.2.8` -> `^5.4.10`
vitest (source)	`^1.5.0` -> `^1.6.0`

Release Notes

rollup/plugins (@rollup/plugin-node-resolve)

`v15.3.0`

2024-09-23

Features

feat: allow preferBuiltins to be a function (#1694)

`v15.2.4`

2024-09-22

Updates

chore: remove is-builtin-module (#1735)

vitest-dev/vitest (@vitest/coverage-v8)

View changes on GitHub

`v1.5.3`

Compare Source

🐞 Bug Fixes

Use package.json name for a workspace project if not provided - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5608 (48fba)
Backport jest iterable equality within object - by @sukovanej in https://github.com/vitest-dev/vitest/issues/5621 (30e5d)
browser: Support benchmark - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5622 (becab)
reporter: Use default error formatter for JUnit - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5629 (20060)

View changes on GitHub

`v1.5.2`

Compare Source

🐞 Bug Fixes

Check for null before storing in weakmap - by @sheremet-va (ce368)

View changes on GitHub

`v1.5.1`

Compare Source

🚀 Features

api: startVitest() to accept stdout and stdin - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5493 (780b1)
- This is listed as a feature, but it doesn't increase the minor version because startVitest API is experimental and doesn't follow semver.

🐞 Bug Fixes

Close vite servers on all resolved projects - by @surc54 in https://github.com/vitest-dev/vitest/issues/5544 (413ec)
Fix default import.meta.env.PROD: false - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5561 (9c649)
Resolve cwd correctly when initiating projects - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5582 (ec9d7)
Always run onTestFinished in reverse order - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5598 (23f29)
browser:
- Disable fileParallelism by default on browser pool - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5528 (5c69f)
- Dispose tester iframe on done - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5595 (b2135)
coverage:
- Fix bundling of v8-to-istanbul - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5549 (df6a4)
- Prevent crash when cleanOnRerun is disabled - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5540 (ea3c1)
- thresholds to compare files relative to root - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5574 (80265)
expect:
- Fix toEqual and toMatchObject with circular references - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5535 (9e641)
vitest:
- Fix false positive file filter match with leading slash - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5578 (316eb)
- Watch the output directory correctly - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5584 (e40f9)
- StubEnv casts boolean on PROD/SSR/DEV - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5590 (4da88)

View changes on GitHub

xtuc/webassemblyjs (@webassemblyjs/helper-wasm-bytecode)

`v1.14.1`

Compare Source

`v1.14.0`

Compare Source

`v1.13.2`

Compare Source

`v1.13.1`

Compare Source

`v1.13.0`

Compare Source

xtuc/webassemblyjs (@webassemblyjs/ieee754)

`v1.14.1`

Compare Source

`v1.14.0`

Compare Source

`v1.13.2`

Compare Source

`v1.13.1`

Compare Source

`v1.13.0`

Compare Source

xtuc/webassemblyjs (@webassemblyjs/leb128)

`v1.14.1`

Compare Source

`v1.14.0`

Compare Source

`v1.13.2`

Compare Source

`v1.13.1`

Compare Source

`v1.13.0`

Compare Source

AssemblyScript/assemblyscript (assemblyscript)

`v0.27.30`

Compare Source

Bug fixes

strictly check operator overload ambiguity (#2762) (dfc8a65)
Operator overload is an internal mechanism, it can support to compare user-defined class, but it need to be limited.
a == b and b == a should run the same function and get the same result in semantic level. Allowing ambiguity is bug prone.
report error for mulitple union type (#2872) (1847c8f)

Other

bump dependence typescript: 4.7.4 → 5.5.4 (#2868) (4bd1c12)

`v0.27.29`

Compare Source

Bug fixes

std/portable included twice (#2860) (f79391c)

Other

chore: bump braces from 3.0.2 to 3.0.3 (#2850) (acdb242)

`v0.27.28`

Compare Source

Bug fixes

detect execution environment when loading wasm module (#2855) (78963c5)

Other

chore: temporary disable std/math.release.wat check in aarch64 osx (#2856) (be49610)

unjs/automd (automd)

`v0.3.12`

Compare Source

compare changes

🩹 Fixes

jsdocs: Disable jiti fs cache and module cache to avoid race conditions (4c7138b)

❤️ Contributors

Pooya Parsa (@pi0)

`v0.3.11`

Compare Source

compare changes

🩹 Fixes

transform: Filter empty issues and keep stack trace (83845d6)

🏡 Chore

release: V0.3.10 (b88f28c)
Add automd to lint:fix script (1ed252e)
Update dependencies (0c038a2)

❤️ Contributors

Pooya Parsa (@pi0)

`v0.3.10`

Compare Source

compare changes

💅 Refactors

badges: Link to npm.chart.dev for npm downloads (#75)

🏡 Chore

Update deps (3ad5dd2)

❤️ Contributors

Pooya Parsa (@pi0)
Sébastien Chopin [email protected]

`v0.3.9`

Compare Source

compare changes

🚀 Enhancements

Add support for deno as package manager (#74)

🏡 Chore

Update dependencies (0828a0b)

❤️ Contributors

Pooya Parsa (@pi0)
Bartek Iwańczuk [email protected]

`v0.3.8`

Compare Source

compare changes

🚀 Enhancements

Upgrade c12 with jiti v2 with esm support (a42d4d2)

🩹 Fixes

version should be obtained automatically when set to true (#59)

📖 Documentation

Add jsdocs for main exports (#55)

🏡 Chore

Apply automated fixes (5ce5ba3)
Update deps (cde3b3a)
Update eslint to v9 (9e68077)

❤️ Contributors

Byron (@byronogis)
Pooya Parsa (@pi0)
Max (@onmax)

unjs/changelogen (changelogen)

`v0.5.7`

Compare Source

compare changes

🩹 Fixes

bump: Avoid using + for canary suffix (#224)

❤️ Contributors

Pooya Parsa (@pi0)

`v0.5.6`

Compare Source

compare changes

🚀 Enhancements

Add option to sign git tags (#117)
git: Support parse git messages that have prefix emoji (#146)

🩹 Fixes

github: Use bearer token (#180)
Handle repo name with multiple segments (#219)
Lowercase scope when filtering (#199)

💅 Refactors

Replace execa with execSync (#222)
Use human readable date for canary versions (#223)
Update execCommand (68127be)

🏡 Chore

Apply automated lint fixes (72c407f)
Update ci (bcb16cb)
Update non major deps (7f714c9)
Update to eslint v9 (fd40be9)
Apply automated lint fixes (673255b)
Update deps (3cfbe27)

❤️ Contributors

Pooya Parsa (@pi0)
Klein Petr (@kleinpetr)
Wan Chiu (@wan54)
Jianqi Pan (@Jannchie)
Vasily Kuzin [email protected]
Daniel Roe (@danielroe)

evanw/esbuild (esbuild)

`v0.24.0`

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.23.0 or ~0.23.0. See npm's documentation about semver for more information.

Drop support for older platforms (#3902)

This release drops support for the following operating system:
- macOS 10.15 Catalina
This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:
```
git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version
```
Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.
Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.
Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.
Work around more issues with Deno 1.31+ (#3917)

This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

This fix was contributed by @Joshix-1.

`v0.23.1`

Compare Source

Allow using the node: import prefix with es* targets (#3821)

The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:
```
// Original code
import fs from 'node:fs'
fs.open

// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "fs";
fs.open;

// New output (with --bundle --format=esm --platform=node --target=node18,es2022)
import fs from "node:fs";
fs.open;
```
Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.
Fix incorrect location of certain error messages (#3845)

This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.
Print comments before case clauses in switch statements (#3838)

With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).
Fix a memory leak with pluginData (#3825)

With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

`v0.23.0`

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.22.0 or ~0.22.0. See npm's documentation about semver for more information.

Revert the recent change to avoid bundling dependencies for node (#3819)

This release reverts the recent change in version 0.22.0 that made --packages=external the default behavior with --platform=node. The default is now back to --packages=bundle.

I've just been made aware that Amazon doesn't pin their dependencies in their "AWS CDK" product, which means that whenever esbuild publishes a new release, many people (potentially everyone?) using their SDK around the world instantly starts using it without Amazon checking that it works first. This change in version 0.22.0 happened to break their SDK. I'm amazed that things haven't broken before this point. This revert attempts to avoid these problems for Amazon's customers. Hopefully Amazon will pin their dependencies in the future.

In addition, this is probably a sign that esbuild is used widely enough that it now needs to switch to a more complicated release model. I may have esbuild use a beta channel model for further development.
Fix preserving collapsed JSX whitespace (#3818)

When transformed, certain whitespace inside JSX elements is ignored completely if it collapses to an empty string. However, the whitespace should only be ignored if the JSX is being transformed, not if it's being preserved. This release fixes a bug where esbuild was previously incorrectly ignoring collapsed whitespace with --jsx=preserve. Here is an example:
```
// Original code
<Foo>
  <Bar />
</Foo>

// Old output (with --jsx=preserve)
<Foo><Bar /></Foo>;

// New output (with --jsx=preserve)
<Foo>
  <Bar />
</Foo>;
```

`v0.22.0`

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.21.0 or ~0.21.0. See npm's documentation about semver for more information.

Omit packages from bundles by default when targeting node (#1874, #2830, #2846, #2915, #3145, #3294, #3323, #3582, #3809, #3815)

This breaking change is an experiment. People are commonly confused when using esbuild to bundle code for node (i.e. for --platform=node) because some packages may not be intended for bundlers, and may use node-specific features that don't work with a bundler. Even though esbuild's "getting started" instructions say to use --packages=external to work around this problem, many people don't read the documentation and don't do this, and are then confused when it doesn't work. So arguably this is a bad default behavior for esbuild to have if people keep tripping over this.

With this release, esbuild will now omit packages from the bundle by default when the platform is node (i.e. the previous behavior of --packages=external is now the default in this case). Note that your dependencies must now be present on the file system when your bundle is run. If you don't want this behavior, you can do --packages=bundle to allow packages to be included in the bundle (i.e. the previous default behavior). Note that --packages=bundle doesn't mean all packages are bundled, just that packages are allowed to be bundled. You can still exclude individual packages from the bundle using --external: even when --packages=bundle is present.

The --packages= setting considers all import paths that "look like" package imports in the original source code to be package imports. Specifically import paths that don't start with a path segment of / or . or .. are considered to be package imports. The only two exceptions to this rule are subpath imports (which start with a # character) and TypeScript path remappings via paths and/or baseUrl in tsconfig.json (which are applied first).
Drop support for older platforms ([#&chore(deps): update autofix-ci/action digest to ea32e3a #8

Configuration

📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from af9d805 to 76a839a Compare April 27, 2024 12:51

renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 044e684 to 6e46f52 Compare May 3, 2024 18:18

renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from cf3ed48 to 7f945bd Compare May 12, 2024 22:33

renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from bb109d3 to e295e08 Compare May 14, 2024 19:58

renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from cb1e72c to 5bb947a Compare October 16, 2024 16:08

renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from a2a6c6d to ab05bd9 Compare October 23, 2024 16:39

renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from d72d87d to 56f51e5 Compare October 31, 2024 06:09

renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from c270c81 to 47892d8 Compare November 6, 2024 23:02

renovate bot force-pushed the renovate/all-minor-patch branch from 47892d8 to 2127d37 Compare November 8, 2024 16:56

chore(deps): update all non-major dependencies

5876daa

renovate bot force-pushed the renovate/all-minor-patch branch from 2127d37 to 5876daa Compare November 9, 2024 10:41

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

renovate bot commented Apr 21, 2024 •

edited

Loading

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

Are you sure you want to change the base?

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

Conversation

renovate bot commented Apr 21, 2024 • edited Loading

Release Notes

Features

Updates

🚀 Features

🐞 Bug Fixes

🏎 Performance

🐞 Bug Fixes

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

Bug fixes

Other

Bug fixes

Other

Bug fixes

Other

🩹 Fixes

❤️ Contributors

🩹 Fixes

🏡 Chore

❤️ Contributors

💅 Refactors

🏡 Chore

❤️ Contributors

🚀 Enhancements

🏡 Chore

❤️ Contributors

🚀 Enhancements

🩹 Fixes

📖 Documentation

🏡 Chore

❤️ Contributors

🩹 Fixes

❤️ Contributors

🚀 Enhancements

🩹 Fixes

💅 Refactors

🏡 Chore

❤️ Contributors

Configuration

renovate bot commented Apr 21, 2024 •

edited

Loading