Skip to content

NPM: Bump the npm-dependencies group with 5 updates #3743

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
Merged
merged 1 commit into from
Mar 31, 2025
Merged

NPM: Bump the npm-dependencies group with 5 updates #3743

merged 1 commit into from
Mar 31, 2025

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 31, 2025 •
edited
Loading

Bumps the npm-dependencies group with 5 updates:

Package From To
mermaid 11.5.0 11.6.0
vega 5.33.0 6.1.2
vega-tooltip 0.35.2 1.0.0
esbuild 0.25.1 0.25.2
stylelint 16.16.0 16.17.0

Updates mermaid from 11.5.0 to 11.6.0

Release notes

Sourced from mermaid's releases.

[email protected]

Minor Changes

  • #6408 ad65313 Thanks @​ashishjain0512! - fix: restore curve type configuration functionality for flowcharts. This fixes the issue where curve type settings were not being applied when configured through any of the following methods:

    • Config
    • Init directive (%%{ init: { 'flowchart': { 'curve': '...' } } }%%)
    • LinkStyle command (linkStyle default interpolate ...)

  • #6381 95d73bc Thanks @​thomascizeron! - Add Radar Chart

Patch Changes

Commits
  • 7b20839 Merge pull request #6412 from mermaid-js/changeset-release/master
  • bb9210c Version Packages
  • 16d9b63 Add missing changeset for requirement diagram fix
  • bf3370f Merge pull request #6409 from mermaid-js/release/11.6.0
  • 9f9091e Update mermaid version palceholder
  • d1b1a67 Merge pull request #6410 from aloisklink/test/fix-cypress-on-nodejs-v20.19.0
  • ac625bd test(e2e): fix Cypress config for Node.JS v20.19.0
  • 40b85c3 Merge pull request #6408 from mermaid-js/fix/6193-curve-interpolation
  • f8e329f Merge branch 'develop' into fix/6193-curve-interpolation
  • 9b9cec9 Merge pull request #6386 from bollwyvl/patch-5
  • Additional commits viewable in compare view

Updates vega from 5.33.0 to 6.1.2

Release notes

Sourced from vega's releases.

v6.0.0

changes since v5.33.0

monorepo

vega-typings

docs

Commits
Maintainer changes

This version was pushed to npm by domoritz, a new releaser for vega since your current version.


Updates vega-tooltip from 0.35.2 to 1.0.0

Release notes

Sourced from vega-tooltip's releases.

Release 1.0.0

What's Changed

New Contributors

Full Changelog: vega/vega-tooltip@v0.35.2...v1.0.0

Changelog

Sourced from vega-tooltip's changelog.

1.0.0 (2025-03-27)

Bug Fixes

  • update defaults.ts to fix custom EL_ID replacing logic (#1019) (cc397ff)
Commits
  • 5f3ca5e chore: release v1.0.0
  • ac0a6ba feat!: update to vega 6
  • e7d4614 chore: switch authors to vega
  • 29ae7a7 chore: use local deps for examples, no need for d3 fetch
  • 564eff4 chore(deps): bump codecov/codecov-action from 5.3.1 to 5.4.0 (#1007)
  • 0dbc115 chore: update deps
  • cc397ff fix: update defaults.ts to fix custom EL_ID replacing logic (#1019)
  • 2390265 ci: fix linting
  • 6aebdc7 chore: simpler eslint call
  • fac3f07 chore: simplify prettier setup
  • Additional commits viewable in compare view

Updates esbuild from 0.25.1 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.

Changelog

Sourced from esbuild's changelog.

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

Commits

Updates stylelint from 16.16.0 to 16.17.0

Release notes

Sourced from stylelint's releases.

16.17.0

Changelog

Sourced from stylelint's changelog.

16.17.0 - 2025-03-26

It adds 1 new rule, support for languageOptions to 2 rules, 1 option to a rule, the --compute-edit-info CLI flag (along with support for EditInfo in 3 rules), and fixes 1 bug. EditInfo is useful for automated fixing tools and editor integrations.

Commits

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 dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Mar 31, 2025
@cla-bot cla-bot bot added the cla-signed label Mar 31, 2025
@daveverwer
Copy link
Member

@dependabot rebase

@dependabot
NPM: Bump the npm-dependencies group with 5 updates
87a3a30 
Bumps the npm-dependencies group with 5 updates:

| Package | From | To |
| --- | --- | --- |
| [mermaid](https://github.com/mermaid-js/mermaid) | `11.5.0` | `11.6.0` |
| [vega](https://github.com/vega/vega) | `5.33.0` | `6.1.2` |
| [vega-tooltip](https://github.com/vega/vega-tooltip) | `0.35.2` | `1.0.0` |
| [esbuild](https://github.com/evanw/esbuild) | `0.25.1` | `0.25.2` |
| [stylelint](https://github.com/stylelint/stylelint) | `16.16.0` | `16.17.0` |


Updates `mermaid` from 11.5.0 to 11.6.0
- [Release notes](https://github.com/mermaid-js/mermaid/releases)
- [Changelog](https://github.com/mermaid-js/mermaid/blob/develop/CHANGELOG.md)
- [Commits](https://github.com/mermaid-js/mermaid/compare/[email protected]@11.6.0)

Updates `vega` from 5.33.0 to 6.1.2
- [Release notes](https://github.com/vega/vega/releases)
- [Commits](vega/vega@v5.33.0...v6.1.2)

Updates `vega-tooltip` from 0.35.2 to 1.0.0
- [Release notes](https://github.com/vega/vega-tooltip/releases)
- [Changelog](https://github.com/vega/vega-tooltip/blob/main/CHANGELOG.md)
- [Commits](vega/vega-tooltip@v0.35.2...v1.0.0)

Updates `esbuild` from 0.25.1 to 0.25.2
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.25.1...v0.25.2)

Updates `stylelint` from 16.16.0 to 16.17.0
- [Release notes](https://github.com/stylelint/stylelint/releases)
- [Changelog](https://github.com/stylelint/stylelint/blob/main/CHANGELOG.md)
- [Commits](stylelint/stylelint@16.16.0...16.17.0)

---
updated-dependencies:
- dependency-name: mermaid
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
- dependency-name: vega
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: npm-dependencies
- dependency-name: vega-tooltip
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: npm-dependencies
- dependency-name: esbuild
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-dependencies
- dependency-name: stylelint
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/npm-dependencies-71d097de8f branch from b8e3d1c to 87a3a30 Compare March 31, 2025 08:41
@daveverwer
Copy link
Member

This included a major version update for vega but I tested everything locally and it looks good.

@daveverwer daveverwer enabled auto-merge March 31, 2025 09:44
@daveverwer daveverwer merged commit b6248ad into main Mar 31, 2025
5 of 6 checks passed
@daveverwer daveverwer deleted the dependabot/npm_and_yarn/npm-dependencies-71d097de8f branch March 31, 2025 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@daveverwer daveverwer daveverwer approved these changes

Assignees

No one assigned

Labels

cla-signed dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@daveverwer