play-ruby icon indicating copy to clipboard operation
play-ruby copied to clipboard
verified publisher icon ruby

Bump the dependencies group across 1 directory with 4 updates

Open dependabot[bot] opened this issue 9 months ago • 0 comments

Bumps the dependencies group with 4 updates in the / directory: @bjorn3/browser_wasi_shim, @zip.js/zip.js, esbuild and vitest.

Updates @bjorn3/browser_wasi_shim from 0.3.0 to 0.4.1

Release notes

Sourced from @​bjorn3/browser_wasi_shim's releases.

v0.4.1

What's Changed

Full Changelog: https://github.com/bjorn3/browser_wasi_shim/compare/v0.4.0...v0.4.1

v0.4.0

What's Changed

New Contributors

Full Changelog: https://github.com/bjorn3/browser_wasi_shim/compare/v0.3.0...v0.4.0

Commits
  • c807dae Bump to v0.4.1
  • b152b3e Handle absence of SharedArrayBuffer (#87)
  • 29eea8c Avoid packaging the test and threads subdirectories
  • c9deb6d Bump to v0.4.0
  • 168313f Merge pull request #86 from kateinoigakukun/yt/issue-ino
  • a267bd6 Remove InoIssuer abstraction
  • c488d4b Return unique ino for each node for Filestat and Dirent
  • 94a5651 Merge pull request #85 from oligamiq/main
  • 9ac88bb rename SVG to svg
  • 6c8d7a0 Merge pull request #84 from oligamiq/main
  • Additional commits viewable in compare view

Updates @zip.js/zip.js from 2.7.57 to 2.7.60

Release notes

Sourced from @​zip.js/zip.js's releases.

v2.7.60

v2.7.59

  • Added legacy-5.6 entry point in the package.json file in order to support TypeScript < 5.7 (see #563 and #549)
  • Fixed score on JSR (see #562)
  • Fixed ESLint and Deno lint warnings
  • Updated dev dependencies

v2.7.58

  • Added ArrayBuffer type parameter to Uint8Array by @​UnsungHero97 in the type definition file (see #549)
  • Added exception "Writer not initialized" when using Writer classes implementing Writer#writeUint8Array if Writer#init() has not been previously called (see #560)
  • Fixed infinite loop when using readable.getReader() from Reader classes (see #559)
  • Added more info about encryptionStrengthin the documentation (see #558)
  • Updated development dependencies
  • Added JSR integration via an Action
Commits

Updates esbuild from 0.24.2 to 0.25.2

Release notes

Sourced from esbuild's releases.

v0.25.2

  • Support flags in regular expressions for the API (#4121)

    The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the filter option. Internally these are translated into Go regular expressions. However, this translation previously ignored the flags property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression /\.[jt]sx?$/i is turned into the Go regular expression `(?i)\.[jt]sx?$` internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with the i flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.

  • Fix node-specific annotations for string literal export names (#4100)

    When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as exports.NAME = ... or module.exports = { ... }. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the file export let foo, bar from ESM to CommonJS, esbuild appends this to the end of the file:

    // Annotate the CommonJS export names for ESM import in node:
0 && (module.exports = {
  bar,
  foo
});

    However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:

    // Original code
let foo
export { foo as "foo!" }

    // Old output (with --format=cjs --platform=node)
...
0 && (module.exports = {
"foo!"
});
    

    // New output (with --format=cjs --platform=node)
...
0 && (module.exports = {
"foo!": null
});

  • Basic support for index source maps (#3439, #4109)

    The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.

    This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.

    Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.

    This feature was contributed by @​clyfish.

v0.25.1

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2024

This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).

Commits

Updates vitest from 3.0.7 to 3.1.1

Release notes

Sourced from vitest's releases.

v3.1.1

   🐞 Bug Fixes

    View changes on GitHub

v3.1.0

🚀 Features

🐞 Bug Fixes

🏎 Performance

... (truncated)

Commits
  • a9d36c7 chore: release v3.1.1
  • 69ca425 fix(reporter): print test only once in the verbose mode (#7738)
  • b166efa fix(reporter): report tests in correct order (#7752)
  • b8eda4b chore: release v3.1.0
  • 938da77 fix (ui): rerun individually tests with special chars in name (#7707)
  • 7883acd feat: use providers request interception for module mocking (#7576)
  • a7ecd0f refactor: remove direct imports from rollup (#7751)
  • 5659a0e feat: Added vitest-browser-lit to vitest init browser and docs (#7705)
  • 2702cf4 fix: fix vm tests flakiness (#7741)
  • 12762ea perf(browser): fork jest-dom instead of bundling it (#7605)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

dependabot[bot] avatar Apr 01 '25 17:04 dependabot[bot]