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

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

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

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

wants to merge 1 commit into from

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
@sxzz/eslint-config ^3.13.0 -> ^3.17.4 age adoption passing confidence
@types/node (source) ^20.14.9 -> ^20.16.5 age adoption passing confidence
@vue-macros/test-utils (source) ^1.4.0 -> ^1.7.0 age adoption passing confidence
bumpp ^9.4.1 -> ^9.5.2 age adoption passing confidence
esbuild ^0.21.5 -> ^0.23.1 age adoption passing confidence
eslint (source) ^9.6.0 -> ^9.10.0 age adoption passing confidence
magic-string ^0.30.10 -> ^0.30.11 age adoption passing confidence
pnpm (source) 9.4.0 -> 9.10.0 age adoption passing confidence
prettier (source) ^3.3.2 -> ^3.3.3 age adoption passing confidence
rollup (source) ^4.18.0 -> ^4.22.0 age adoption passing confidence
tsup (source) ^8.1.0 -> ^8.3.0 age adoption passing confidence
tsx (source) ^4.15.8 -> ^4.19.1 age adoption passing confidence
typescript (source) ^5.5.2 -> ^5.6.2 age adoption passing confidence
unplugin ^1.10.1 -> ^1.14.1 age adoption passing confidence
vite (source) ^5.3.2 -> ^5.4.6 age adoption passing confidence
vitest (source) ^2.0.3 -> ^2.1.1 age adoption passing confidence
webpack ^5.92.1 -> ^5.94.0 age adoption passing confidence

Release Notes

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.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.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.10.0

Compare Source

v9.9.1

Compare Source

v9.9.0

Compare Source

Features

  • 41d0206 feat: Add support for TS config files (#​18134) (Arya Emami)
  • 3a4eaf9 feat: add suggestion to require-await to remove async keyword (#​18716) (Dave)

Documentation

  • 9fe068c docs: how to author plugins with configs that extend other configs (#​18753) (Alec Gibson)
  • 48117b2 docs: add version support page in the side navbar (#​18738) (Amaresh S M)
  • fec2951 docs: add version support page to the dropdown (#​18730) (Amaresh S M)
  • 38a0661 docs: Fix typo (#​18735) (Zaina Al Habash)
  • 3c32a9e docs: Update yarn command for creating ESLint config (#​18739) (Temitope Ogunleye)
  • f9ac978 docs: Update README (GitHub Actions Bot)

Chores

v9.8.0

Compare Source

v9.7.0

Compare Source

Features

  • 7bd9839 feat: add support for es2025 duplicate named capturing groups (#​18630) (Yosuke Ota)
  • 1381394 feat: add regex option in no-restricted-imports (#​18622) (Nitin Kumar)

Bug Fixes

  • 14e9f81 fix: destructuring in catch clause in no-unused-vars (#​18636) (Francesco Trotta)

Documentation

  • 9f416db docs: Add Powered by Algolia label to the search. (#​18633) (Amaresh S M)
  • c8d26cb docs: Open JS Foundation -> OpenJS Foundation (#​18649) (Milos Djermanovic)
  • 6e79ac7 docs: loadESLint does not support option cwd (#​18641) (Francesco Trotta)

Chores

rich-harris/magic-string (magic-string)

v0.30.11

Compare Source

Bug Fixes
  • not use negative indices for remove in empty string (#​281) (5c1cba0)
pnpm/pnpm (pnpm)

v9.10.0: pnpm 9.10

Compare Source

Minor Changes

  • Support for a new CLI flag, --exclude-peers, added to the list and why commands. When --exclude-peers is used, peer dependencies are not printed in the results, but dependencies of peer dependencies are still scanned #​8506.

  • Added a new setting to package.json at pnpm.auditConfig.ignoreGhsas for ignoring vulnerabilities by their GHSA code #​6838.

    For instance:

    {
  "pnpm": {
    "auditConfig": {
      "ignoreGhsas": [
        "GHSA-42xw-2xvc-qx8m",
        "GHSA-4w2v-q235-vp99",
        "GHSA-cph5-m8f7-6c5x",
        "GHSA-vh95-rmgr-6w4m"
      ]
    }
  }
}

Patch Changes

  • Throw an exception if pnpm switches to the same version of itself.
  • Reduce memory usage during peer dependencies resolution.

Platinum Sponsors

Gold Sponsors

Our Silver Sponsors

v9.9.0

Compare Source

v9.8.0

Compare Source

v9.7.1

Compare Source

v9.7.0: pnpm 9.7

Compare Source

Minor Changes

  • Added pnpm version management. If the manage-package-manager-versions setting is set to true, pnpm will switch to the version specified in the packageManager field of package.json #​8363. This is the same field used by Corepack. Example:

    {
  "packageManager": "[email protected]"
}

  • Added the ability to apply patch to all versions #​8337.

    If the key of pnpm.patchedDependencies is a package name without a version (e.g. pkg), pnpm will attempt to apply the patch to all versions of the package. Failures will be skipped. If there's only one version of pkg installed, pnpm patch pkg and subsequent pnpm patch-commit $edit_dir will create an entry named pkg in pnpm.patchedDependencies. And pnpm will attempt to apply this patch to other versions of pkg in the future.

  • Change the default edit dir location when running pnpm patch from a temporary directory to node_modules/.pnpm_patches/pkg[@&#8203;version] to allow the code editor to open the edit dir in the same file tree as the main project #​8379.

  • Substitute environment variables in config keys #​6679.

Patch Changes

  • pnpm install should run node-gyp rebuild if the project has a binding.gyp file even if the project d

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/@sxzz/[email protected] Transitive: environment, eval, filesystem, shell, unsafe +207 38.1 MB sxzz
npm/@types/[email protected] None +1 2.26 MB types
npm/@vue-macros/[email protected] Transitive: environment, eval, filesystem, shell, unsafe +99 18.6 MB sxzz
npm/[email protected] environment, filesystem, unsafe Transitive: network, shell +71 7.03 MB antfu
npm/[email protected] None 0 134 kB esbuild, evanw
npm/[email protected] environment Transitive: eval, filesystem, shell, unsafe +89 10.2 MB eslintbot
npm/[email protected] None +1 576 kB antfu
npm/[email protected] environment, filesystem, unsafe 0 7.7 MB prettier-bot
npm/[email protected] environment +1 1.31 MB rolldownbot
npm/[email protected] None +1 2.3 MB eventualbuddha, lukastaegert, rich_harris, ...2 more
npm/[email protected] Transitive: environment, filesystem, network, shell, unsafe +93 7.07 MB egoist, sxzz
npm/[email protected] Transitive: filesystem, unsafe +2 542 kB hirokiosame
npm/[email protected] None 0 22.4 MB typescript-bot
npm/[email protected] Transitive: environment +2 776 kB antfu, sxzz
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.46 MB antfu, oreanno, patak, ...1 more
npm/[email protected] Transitive: environment, eval, filesystem, shell, unsafe +73 15.8 MB evilebottnawi, jhnns, sokra, ...1 more

🚮 Removed packages: 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 85ee0fe to 0a43e25 Compare August 28, 2024 04:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 8 times, most recently from d5a75e9 to baa3212 Compare September 5, 2024 16:58
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from 95f6cdb to bcb02c8 Compare September 13, 2024 17:32
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 880e8e0 to 83de7fa Compare September 17, 2024 04:59
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