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.

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

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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 21, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@rollup/plugin-node-resolve (source) ^15.2.3 -> ^15.3.0 age adoption passing confidence
@types/node (source) ^20.12.7 -> ^20.17.9 age adoption passing confidence
@vitest/coverage-v8 (source) ^1.5.0 -> ^1.6.0 age adoption passing confidence
@webassemblyjs/helper-wasm-bytecode 1.12.1 -> 1.14.1 age adoption passing confidence
@webassemblyjs/ieee754 (source) 1.12.1 -> 1.14.1 age adoption passing confidence
@webassemblyjs/leb128 (source) 1.12.1 -> 1.14.1 age adoption passing confidence
@webassemblyjs/utf8 1.12.1 -> 1.14.1 age adoption passing confidence
@webassemblyjs/wasm-parser ^1.12.1 -> ^1.14.1 age adoption passing confidence
assemblyscript (source) ^0.27.27 -> ^0.27.31 age adoption passing confidence
automd ^0.3.7 -> ^0.3.12 age adoption passing confidence
changelogen ^0.5.5 -> ^0.5.7 age adoption passing confidence
esbuild ^0.20.2 -> ^0.24.0 age adoption passing confidence
eslint (source) ^8.57.0 -> ^8.57.1 age adoption passing confidence
eslint-config-unjs ^0.2.1 -> ^0.4.2 age adoption passing confidence
jiti ^1.21.0 -> ^1.21.6 age adoption passing confidence
magic-string ^0.30.9 -> ^0.30.14 age adoption passing confidence
miniflare (source) ^3.20240405.1 -> ^3.20241106.1 age adoption passing confidence
mlly ^1.6.1 -> ^1.7.3 age adoption passing confidence
pkg-types ^1.0.3 -> ^1.2.1 age adoption passing confidence
pnpm (source) 9.0.5 -> 9.14.4 age adoption passing confidence
prettier (source) ^3.2.5 -> ^3.4.1 age adoption passing confidence
rollup (source) ^4.14.2 -> ^4.28.0 age adoption passing confidence
typescript (source) ^5.4.5 -> ^5.7.2 age adoption passing confidence
unplugin ^1.10.1 -> ^1.16.0 age adoption passing confidence
vite (source) ^5.2.8 -> ^5.4.11 age adoption passing confidence
vitest (source) ^1.5.0 -> ^1.6.0 age adoption passing confidence

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)

v1.6.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v1.5.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    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.31

Compare Source

New features
  • include runtime from current directory instead of lib (#​2884) (285afb1)
Other

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

v0.27.29

Compare Source

Bug fixes
Other

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

v0.3.11

Compare Source

compare changes

🩹 Fixes
  • transform: Filter empty issues and keep stack trace (83845d6)
🏡 Chore
❤️ Contributors

v0.3.10

Compare Source

compare changes

💅 Refactors
  • badges: Link to npm.chart.dev for npm downloads (#​75)
🏡 Chore
❤️ Contributors

v0.3.9

Compare Source

compare changes

🚀 Enhancements
  • Add support for deno as package manager (#​74)
🏡 Chore
❤️ Contributors

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
❤️ Contributors
unjs/changelogen (changelogen)

v0.5.7

Compare Source

compare changes

🩹 Fixes
  • bump: Avoid using + for canary suffix (#​224)
❤️ Contributors

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
❤️ Contributors
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.


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 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 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 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 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 renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from e27e566 to ce4c59e Compare November 13, 2024 13:46
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 85e43b0 to e788037 Compare November 20, 2024 11:26
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from e3b37eb to be21010 Compare November 28, 2024 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants