Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update all non-major dependencies #20

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update all non-major dependencies #20

wants to merge 1 commit into from
+1,777 −1,439

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 1, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@rollup/pluginutils (source) ^5.1.0 -> ^5.1.3 age adoption passing confidence
@sxzz/eslint-config ^3.13.0 -> ^3.17.4 age adoption passing confidence
@types/node (source) ^20.14.9 -> ^20.17.6 age adoption passing confidence
@vue-macros/test-utils (source) ^1.4.0 -> ^1.7.0 age adoption passing confidence
bumpp ^9.4.1 -> ^9.8.1 age adoption passing confidence
esbuild ^0.21.5 -> ^0.24.0 age adoption passing confidence
eslint (source) ^9.6.0 -> ^9.14.0 age adoption passing confidence
magic-string ^0.30.10 -> ^0.30.12 age adoption passing confidence
pnpm (source) 9.4.0 -> 9.12.3 age adoption passing confidence
prettier (source) ^3.3.2 -> ^3.3.3 age adoption passing confidence
rollup (source) ^4.18.0 -> ^4.25.0 age adoption passing confidence
tsup (source) ^8.1.0 -> ^8.3.5 age adoption passing confidence
tsx (source) ^4.15.8 -> ^4.19.2 age adoption passing confidence
typescript (source) ^5.5.2 -> ^5.6.3 age adoption passing confidence
unplugin ^1.10.1 -> ^1.15.0 age adoption passing confidence
vite (source) ^5.3.2 -> ^5.4.10 age adoption passing confidence
vitest (source) ^2.0.3 -> ^2.1.4 age adoption passing confidence
webpack ^5.92.1 -> ^5.96.1 age adoption passing confidence

Release Notes

rollup/plugins (@​rollup/pluginutils)

v5.1.3

2024-10-23

Bugfixes

v5.1.2

2024-09-23

Bugfixes
  • fix: optimize createFilter and normalizePath (#​1750)

v5.1.1

2024-09-22

Bugfixes
  • fix: improve regex performance (#​1753)
sxzz/eslint-config (@​sxzz/eslint-config)

v3.17.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.17.3

Compare Source

   🐞 Bug Fixes
  • Disable @typescript-eslint/no-unused-expressions for markdown files  -  by @​sxzz (54300)
    View changes on GitHub

v3.17.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.17.1

Compare Source

   🚀 Features
  • Enable @typescript-eslint/no-unused-expressions  -  by @​sxzz (f5932)
   🐞 Bug Fixes
    View changes on GitHub

v3.17.0

Compare Source

   🚀 Features
    View changes on GitHub

v3.16.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.16.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.16.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.16.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.16.0

Compare Source

   🚀 Features
    View changes on GitHub

v3.15.1

Compare Source

   🚀 Features
    View changes on GitHub

v3.15.0

Compare Source

   🚀 Features
    View changes on GitHub

v3.14.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
vue-macros/vue-macros (@​vue-macros/test-utils)

v1.7.0

Minor Changes

v1.6.2

Patch Changes

v1.6.1

Compare Source

Patch Changes

v1.6.0

Compare Source

Minor Changes
Patch Changes
  • 4e2cca7 Thanks @​sxzz! - Remove dev condition from exports of package.json

v1.5.0

Compare Source

Minor Changes
antfu/bumpp (bumpp)

v9.8.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v9.8.0

Compare Source

   🚀 Features
    View changes on GitHub

v9.7.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v9.7.0

Compare Source

   🚀 Features
    View changes on GitHub

v9.6.1

Compare Source

   🚀 Features
    View changes on GitHub

v9.6.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v9.5.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v9.5.1

Compare Source

   🚀 Features
    View changes on GitHub

v9.5.0

Compare Source

v9.4.2

Compare Source

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 (#​3802)

    This release drops support for the following operating systems:

    • Windows 7
    • Windows 8
    • Windows Server 2008
    • Windows Server 2012

    This is because the Go programming language dropped support for these operating system versions in Go 1.21, and this release updates esbuild from Go 1.20 to Go 1.22.

    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.21). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild.exe --version

    In addition, this release increases the minimum required node version for esbuild's JavaScript API from node 12 to node 18. Node 18 is the oldest version of node that is still being supported (see node's release schedule for more information). This increase is because of an incompatibility between the JavaScript that the Go compiler generates for the esbuild-wasm package and versions of node before node 17.4 (specifically the crypto.getRandomValues function).

  • Update await using behavior to match TypeScript

    TypeScript 5.5 subtly changes the way await using behaves. This release updates esbuild to match these changes in TypeScript. You can read more about these changes in microsoft/TypeScript#58624.

  • Allow es2024 as a target environment

    The ECMAScript 2024 specification was just approved, so it has been added to esbuild as a possible compilation target. You can read more about the features that it adds here: https://2ality.com/2024/06/ecmascript-2024.html. The only addition that's relevant for esbuild is the regular expression /v flag. With --target=es2024, regular expressions that use the /v flag will now be passed through untransformed instead of being transformed into a call to new RegExp.

  • Publish binaries for OpenBSD on 64-bit ARM (#​3665, #​3674)

    With this release, you should now be able to install the esbuild npm package in OpenBSD on 64-bit ARM, such as on an Apple device with an M1 chip.

    This was contributed by @​ikmckenz.

  • Publish binaries for WASI (WebAssembly System Interface) preview 1 (#​3300, #​3779)

    The upcoming WASI (WebAssembly System Interface) standard is going to be a way to run WebAssembly outside of a JavaScript host environment. In this scenario you only need a .wasm file without any supporting JavaScript code. Instead of JavaScript providing the APIs for the host environment, the WASI standard specifies a "system interface" that WebAssembly code can access directly (e.g. for file system access).

    Development versions of the WASI specification are being released using preview numbers. The people behind WASI are currently working on preview 2 but the Go compiler has released support for preview 1, which from what I understand is now considered an unsupported legacy release. However, some people have requested that esbuild publish binary executables that support WASI preview 1 so they can experiment with them.

    This release publishes esbuild precompiled for WASI preview 1 to the @esbuild/wasi-preview1 package on npm (specifically the file @esbuild/wasi-preview1/esbuild.wasm). This binary executable has not been tested and won't be officially supported, as it's for an old preview release of a specification that has since moved in another direction. If it works for you, great! If not, then you'll likely have to wait for the ecosystem to evolve before using esbuild with WASI. For example, it sounds like perhaps WASI preview 1 doesn't include support for opening network sockets so esbuild's local development server is unlikely to work with WASI preview 1.

  • Warn about onResolve plugins not setting a path (#​3790)

    Plugins that return values from onResolve without resolving the path (i.e. without setting either path or external: true) will now cause a warning. This is because esbuild only uses return values from onResolve if it successfully resolves the path, and it's not good for invalid input to be silently ignored.

  • Add a new Go API for running the CLI with plugins (#​3539)

    With esbuild's Go API, you can now call cli.RunWithPlugins(args, plugins) to pass an array of esbuild plugins to be used during the build process. This allows you to create a CLI that behaves similarly to esbuild's CLI but with additional Go plugins enabled.

    This was contributed by @​edewit.

eslint/eslint (eslint)

v9.14.0

Compare Source

v9.13.0

Compare Source

v9.12.0

Compare Source

Features

Bug Fixes

Documentation

  • ecbd522 docs: Mention code explorer (#​18978) (Nicholas C. Zakas)
  • 7ea4ecc docs: Clarifying the Use of Meta Objects (#​18697) (Amaresh S M)
  • d3e4b2e docs: Clarify how to exclude .js files (#​18976) (Milos Djermanovic)
  • 57232ff docs: Mention plugin-kit in language docs (#​18973) (Nicholas C. Zakas)
  • b80ed00 docs: Update README (GitHub Actions Bot)
  • cb69ab3 docs: Update README (GitHub Actions Bot)
  • 7fb0d95 docs: Update README (GitHub Actions Bot)
  • 493348a docs: Update README (GitHub Actions Bot)
  • 87a582c docs: fix typo in id-match rule (#​18944) (Jay)

Chores

v9.11.1

Compare Source

v9.11.0

Compare Source

Features

  • ec30c73 feat: add "eslint/universal" to export Linter (#​18883) (唯然)
  • c591da6 feat: Add language to types (#​18917) (Nicholas C. Zakas)
  • 492eb8f feat: limit the name given to ImportSpecifier in id-length (#​18861) (Tanuj Kanti)
  • 19c6856 feat: Add no-useless-constructor suggestion (#​18799) (Jordan Thomson)
  • a48f8c2 feat: add type FormatterFunction, update LoadedFormatter (#​18872) (Francesco Trotta)

Bug Fixes

  • 5e5f39b fix: add missing types for no-restricted-exports rule (#​18914) (Kristóf Poduszló)
  • 8f630eb fix: add missing types for no-param-reassign options (#​18906) (Kristóf Poduszló)
  • d715781 fix: add missing types for no-extra-boolean-cast options (#​18902)

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 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 renovate bot added the dependencies label Jul 1, 2024
@stackblitz StackBlitz
Copy link

stackblitz bot commented Jul 1, 2024

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 36a3f83 to c9ebdc2 Compare July 8, 2024 15:53
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from c590452 to 2ca681c Compare July 17, 2024 17:19
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from fba932e to 1cbd35c Compare July 20, 2024 18:48
@socket-security Socket Security
Copy link

socket-security bot commented Jul 20, 2024 •
edited
Loading

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@rollup/[email protected] None +3 219 kB guybedford, lukastaegert, rich_harris, ...1 more
npm/@sxzz/[email protected] Transitive: environment, eval, filesystem, shell, unsafe +201 38.4 MB sxzz
npm/@types/[email protected] None +1 2.3 MB types
npm/@vue-macros/[email protected] Transitive: environment, eval, filesystem, shell, unsafe +89 18 MB sxzz
npm/[email protected] filesystem, unsafe Transitive: environment, network, shell +74 7.22 MB antfu
npm/[email protected] environment, filesystem, network, shell 0 134 kB esbuild, evanw
npm/[email protected] environment Transitive: eval, filesystem, shell, unsafe +85 10.4 MB eslintbot
npm/[email protected] None +1 577 kB antfu
npm/[email protected] environment, filesystem, unsafe 0 7.7 MB prettier-bot
npm/[email protected] environment +1 1.36 MB rolldownbot
npm/[email protected] None +1 2.62 MB lukastaegert
npm/[email protected] eval, filesystem Transitive: environment, network, shell, unsafe +71 6.86 MB egoist
npm/[email protected] Transitive: filesystem +3 680 kB hirokiosame
npm/[email protected] None 0 22.4 MB typescript-bot
npm/[email protected] filesystem, unsafe Transitive: environment +2 787 kB antfu
npm/[email protected] Transitive: environment, filesystem, network, shell +5 3.77 MB antfu, patak, soda, ...2 more
npm/[email protected] Transitive: environment, filesystem, shell, unsafe +30 3.67 MB antfu, oreanno, patak, ...1 more
npm/[email protected] environment, filesystem, network, unsafe Transitive: eval, shell +74 16.1 MB evilebottnawi, jhnns, sokra, ...1 more

🚮 Removed packages: npm/@rollup/[email protected], npm/@sxzz/[email protected], npm/@types/[email protected], npm/@vue-macros/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from d786234 to 0df9c25 Compare July 25, 2024 11:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from ebafe17 to 8b35455 Compare October 23, 2024 16:52
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 15 times, most recently from 47f0590 to 9fe4cda Compare November 1, 2024 01:20
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 46c6379 to e81e509 Compare November 4, 2024 11:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants