search

andreasgerstmayr / fava-dashboards

Custom Dashboards for Beancount in Fava
MIT License
178 stars 21 forks source link

Bump the npm group across 1 directory with 4 updates #71

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 5 months ago

Bumps the npm group with 4 updates in the /frontend directory: echarts, esbuild, puppeteer and typescript.

Updates echarts from 5.5.0 to 5.5.1

Release notes

Sourced from echarts's releases.

5.5.1

  • [Feature] [axis] Support custom axis tick/label positions. #19919 (dvdkon) (Ovilia)
  • [Feature] [bar] Add startValue option. #17078 (jiawulin001)
  • [Feature] [sankey] Add itemStyle.borderRadius option. #19763 (deftliang)
  • [Feature] [time] Add meridian template {a}/{A}. #19888 (maurodesouza)
  • [Feature] [geo] Add totalZoom parameter for the georoam event. #19837 (zhaoxinggang)
  • [Feature] [treemap] Add scaleLimit option to limit the zooming. #18304 (liuyizhou)
  • [Fix] [series] Avoid error caused by seriesData.getLinkedData. #19901 (plainheart)
  • [Fix] [marker] Fix marker label formatter can't get series information. #19898 (plainheart)
  • [Fix] [aria] Avoid error in SSR mode. #19892 (OverflowCat)
  • [Fix] [data] Avoid error when using BigInt values. #19847 (zettca)
  • [Fix] [pie] Fix endAngle is not applied on the empty circle. #19642 (plainheart)
  • [Fix] [toolbox] Fix uncaught reference error in the environment that MouseEvent doesn't exist. #19620 (plainheart)
  • [Fix] [tooltip] Fix tooltip XSS issue when legend name is HTML string. #20045 (plainheart)
  • [Fix] [type] Fix that in users' .d.ts import('echarts/types/dist/shared') can not visit 'echarts/types/dist/shared.d.ts' since v5.5.0. #20030 (100pah)

New Contributors

5.5.1-rc.1

No release notes provided.

Commits
  • 2caf684 Merge pull request #20039 from apache/release-dev
  • 34889d9 build release
  • efa3e5a Merge pull request #20045 from apache/fix/tooltip-xss
  • 6221076 test(tooltip): update test case for tooltip xss
  • c1727a6 refactor(tooltip): add encodeHTMLContent option to specify whether the cont...
  • 9d2bab0 Merge pull request #20044 from apache/dependabot/npm_and_yarn/ws-7.5.10
  • ad947d6 fix(tooltip): fix tooltip XSS issue when legend name is HTML string
  • 4c015dd chore(deps-dev): bump ws from 7.5.7 to 7.5.10
  • 486f24f change version from 5.6.0 to 5.5.1
  • ca9ed74 chore: release 5.6.0
  • Additional commits viewable in compare view


Updates esbuild from 0.21.5 to 0.22.0

Release notes

Sourced from esbuild's releases.

v0.22.0

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

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.22.0

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)

... (truncated)

Commits


Updates puppeteer from 22.11.0 to 22.12.1

Release notes

Sourced from puppeteer's releases.

puppeteer-core: v22.12.1

22.12.1 (2024-06-26)

Bug Fixes

  • execution contexts might be created before previous is destroyed (#12666) (db642d1)
  • reset the viewport after taking a fullPage screenshot if defaultViewport is null (#12650) (0a32283)
  • roll to Chrome 126.0.6478.126 (r1300313) (#12656) (32ed82c)
  • use RAF-based polling for ARIA selectors (#12664) (56d1d3f)

puppeteer: v22.12.1

22.12.1 (2024-06-26)

Miscellaneous Chores

  • puppeteer: Synchronize puppeteer versions

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • puppeteer-core bumped from 22.12.0 to 22.12.1

puppeteer-core: v22.12.0

22.12.0 (2024-06-21)

Features

  • support AbortSignal in page.waitForRequest/Response/NetworkIdle/Frame (#12621) (54ecea7)
  • webdriver: support for PageEvent.Popup (#12612) (293926b)

Bug Fixes

puppeteer: v22.12.0

22.12.0 (2024-06-21)

Miscellaneous Chores

  • puppeteer: Synchronize puppeteer versions

... (truncated)

Commits
  • 1886390 chore: release main (#12659)
  • db642d1 fix: execution contexts might be created before previous is destroyed (#12666)
  • 56d1d3f fix: use RAF-based polling for ARIA selectors (#12664)
  • 0a32283 fix: reset the viewport after taking a fullPage screenshot if defaultViewport...
  • 5d762be docs: fix some broken links (#12660)
  • 866f720 build(deps): relax dependency versions for non-puppeteer dependencies (#12649)
  • 32ed82c fix: roll to Chrome 126.0.6478.126 (r1300313) (#12656)
  • fbd6ca5 docs: various docs improvements (#12651)
  • 9808d46 chore(deps): Bump glob from 10.4.1 to 10.4.2 in the dependencies group (#12639)
  • add2890 docs: fix various typos (#12648)
  • Additional commits viewable in compare view


Updates typescript from 5.4.5 to 5.5.2

Release notes

Sourced from typescript's releases.

TypeScript 5.5

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.5 RC

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.5 Beta

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

Commits
  • ce2e60e Update LKG
  • f3b21a2 🤖 Pick PR #58931 (Defer creation of barebonesLibSourc...) into release-5.5 (#...
  • 7b1620b 🤖 Pick PR #58811 (fix(58801): "Move to file" on globa...) into release-5.5 (#...
  • 5367ae1 Bump version to 5.5.2 and LKG
  • 02132e5 🤖 Pick PR #58895 (Fix global when typescript.js loade...) into release-5.5 (#...
  • 45b1e3c 🤖 Pick PR #58872 (Fix declaration emit crash) into release-5.5 (#58874)
  • 17933ee 🤖 Pick PR #58810 (Fixed declaration emit issue relate...) into release-5.5 (#...
  • 552b07e 🤖 Pick PR #58786 (Fixed declaration emit crash relate...) into release-5.5 (#...
  • 39c9eeb Pick #58857 to release-5.5 (#58858)
  • 2b0009c 🤖 Pick PR #58846 (Ensure the updates with crashes rev...) into release-5.5 (#...
  • 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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 4 months ago

Looks like these dependencies are updatable in another way, so this is no longer needed.