unchartedsoftware / grafer

Large graph rendering library.
Apache License 2.0
3 stars 2 forks source link

build(deps-dev): bump the dev-deps group across 1 directory with 11 updates #203

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps the dev-deps group with 11 updates in the / directory:

Package From To
@typescript-eslint/eslint-plugin 7.1.0 7.15.0
@typescript-eslint/parser 7.1.0 7.15.0
esbuild 0.14.54 0.22.0
globby 14.0.1 14.0.2
karma-esbuild 2.2.5 2.3.0
lit 3.1.2 3.1.4
mocha 10.3.0 10.5.2
@types/mocha 10.0.6 10.0.7
rimraf 5.0.5 5.0.7
tslib 2.6.2 2.6.3
typescript 5.3.3 5.5.3

Updates @typescript-eslint/eslint-plugin from 7.1.0 to 7.15.0

Release notes

Sourced from @​typescript-eslint/eslint-plugin's releases.

v7.15.0

7.15.0 (2024-07-01)

🚀 Features

  • eslint-plugin: [array-type] detect Readonly<string[]> case (#8752)
  • eslint-plugin: back-port new rules around empty object types from v8 (#9443)

đź©ą Fixes

  • disable EXPERIMENTAL_useProjectService in disabled-type-checked shared config (#9459)
  • eslint-plugin: [no-unsafe-return] differentiate a types-error any from a true any (#9254)
  • eslint-plugin: [no-unsafe-call] differentiate a types-error any from a true any (#9304)
  • utils: clean outdated RuleTester export (#9322)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

v7.14.1

7.14.1 (2024-06-24)

🚀 Features

  • support TypeScript 5.5 (#9397)
  • ast-spec: tighter types and documentation for declaration/* (#9211)

đź©ą Fixes

  • keep warnAbountTSVersion in sync with package.json (#9400)
  • eslint-plugin: [no-extraneous-class] handle abstract members (#9367)
  • eslint-plugin: [prefer-nullish-coalescing] handle intersected primitive types (#9378)
  • eslint-plugin: [no-invalid-this] support AccessorProperty (#9411)
  • eslint-plugin: [prefer-nullish-coalescing] treat enums and literals as their underlying primitive types (#9376)
  • eslint-plugin: [prefer-nullish-coalescing] ensure ternary fix does not remove parens (#9380)

❤️ Thank You

... (truncated)

Changelog

Sourced from @​typescript-eslint/eslint-plugin's changelog.

7.15.0 (2024-07-01)

🚀 Features

  • eslint-plugin: [array-type] detect Readonly<string[]> case

  • eslint-plugin: back-port new rules around empty object types from v8

đź©ą Fixes

  • disable EXPERIMENTAL_useProjectService in disabled-type-checked shared config

  • eslint-plugin: [no-unsafe-return] differentiate a types-error any from a true any

  • eslint-plugin: [no-unsafe-call] differentiate a types-error any from a true any

❤️ Thank You

  • auvred
  • Kim Sang Du
  • rgehbt
  • Vinccool96

You can read about our versioning strategy and releases on our website.

7.14.1 (2024-06-24)

đź©ą Fixes

  • eslint-plugin: [prefer-nullish-coalescing] treat enums and literals as their underlying primitive types

  • eslint-plugin: [prefer-nullish-coalescing] ensure ternary fix does not remove parens

❤️ Thank You

  • Jake Bailey

You can read about our versioning strategy and releases on our website.

7.14.0 (2024-06-24)

🚀 Features

  • support TypeScript 5.5

... (truncated)

Commits
  • 2865d31 chore(release): publish 7.15.0
  • 2671de5 feat(eslint-plugin): back-port new rules around empty object types from v8 (#...
  • 05142c5 fix(eslint-plugin): [no-unsafe-call] differentiate a types-error any from a t...
  • a466e07 fix: disable EXPERIMENTAL_useProjectService in disabled-type-checked shar...
  • 3694d8f fix(eslint-plugin): [no-unsafe-return] differentiate a types-error any from a...
  • 9dba021 feat(eslint-plugin): [array-type] detect Readonly\<string[]> case (#8752)
  • b4fe94f chore(release): publish 7.14.1
  • f29150f fix(eslint-plugin): [prefer-nullish-coalescing] ensure ternary fix does not r...
  • 9b7731d fix(eslint-plugin): [prefer-nullish-coalescing] treat enums and literals as t...
  • dfc4469 chore(release): publish 7.14.0
  • Additional commits viewable in compare view


Updates @typescript-eslint/parser from 7.1.0 to 7.15.0

Release notes

Sourced from @​typescript-eslint/parser's releases.

v7.15.0

7.15.0 (2024-07-01)

🚀 Features

  • eslint-plugin: [array-type] detect Readonly<string[]> case (#8752)
  • eslint-plugin: back-port new rules around empty object types from v8 (#9443)

đź©ą Fixes

  • disable EXPERIMENTAL_useProjectService in disabled-type-checked shared config (#9459)
  • eslint-plugin: [no-unsafe-return] differentiate a types-error any from a true any (#9254)
  • eslint-plugin: [no-unsafe-call] differentiate a types-error any from a true any (#9304)
  • utils: clean outdated RuleTester export (#9322)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

v7.14.1

7.14.1 (2024-06-24)

🚀 Features

  • support TypeScript 5.5 (#9397)
  • ast-spec: tighter types and documentation for declaration/* (#9211)

đź©ą Fixes

  • keep warnAbountTSVersion in sync with package.json (#9400)
  • eslint-plugin: [no-extraneous-class] handle abstract members (#9367)
  • eslint-plugin: [prefer-nullish-coalescing] handle intersected primitive types (#9378)
  • eslint-plugin: [no-invalid-this] support AccessorProperty (#9411)
  • eslint-plugin: [prefer-nullish-coalescing] treat enums and literals as their underlying primitive types (#9376)
  • eslint-plugin: [prefer-nullish-coalescing] ensure ternary fix does not remove parens (#9380)

❤️ Thank You

... (truncated)

Changelog

Sourced from @​typescript-eslint/parser's changelog.

7.15.0 (2024-07-01)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.14.1 (2024-06-24)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.14.0 (2024-06-24)

🚀 Features

  • support TypeScript 5.5

❤️ Thank You

  • Brad Zacher
  • cm-ayf
  • Jake Bailey
  • James Zhan
  • Joshua Chen
  • yoshi2no

You can read about our versioning strategy and releases on our website.

7.13.1 (2024-06-17)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

7.13.0 (2024-06-10)

🚀 Features

  • parser, typescript-estree: export withoutProjectParserOptions utility

❤️ Thank You

  • Fotis Papadogeorgopoulos
  • Joshua Chen
  • Kirk Waiblinger

... (truncated)

Commits
  • 2865d31 chore(release): publish 7.15.0
  • b4fe94f chore(release): publish 7.14.1
  • dfc4469 chore(release): publish 7.14.0
  • 1212a8f chore(release): publish 7.13.1
  • 8a178ed chore(release): publish 7.13.0
  • c9a6dd9 feat(parser, typescript-estree): export withoutProjectParserOptions utility (...
  • 7e93b28 chore(release): publish 7.12.0
  • 2bbf656 fix(types): correct typing ParserOptions (#9202)
  • e360541 chore(release): publish 7.11.0
  • c18226e chore(release): publish 7.10.0
  • Additional commits viewable in compare view


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

Changelog: 2022

This changelog documents all esbuild versions published in the year 2022 (versions 0.14.11 through 0.16.12).

0.16.12

  • Loader defaults to js for extensionless files (#2776)

    Certain packages contain files without an extension. For example, the yargs package contains the file yargs/yargs which has no extension. Node, Webpack, and Parcel can all understand code that imports yargs/yargs because they assume that the file is JavaScript. However, esbuild was previously unable to understand this code because it relies on the file extension to tell it how to interpret the file. With this release, esbuild will now assume files without an extension are JavaScript files. This can be customized by setting the loader for "" (the empty string, representing files without an extension) to another loader. For example, if you want files without an extension to be treated as CSS instead, you can do that like this:

    • CLI:

      esbuild --bundle --loader:=css
      
    • JS:

      esbuild.build({
        bundle: true,
        loader: { '': 'css' },
      })
      
    • Go:

      api.Build(api.BuildOptions{
        Bundle: true,
        Loader: map[string]api.Loader{"": api.LoaderCSS},
      })
      

    In addition, the "type" field in package.json files now only applies to files with an explicit .js, .jsx, .ts, or .tsx extension. Previously it was incorrectly applied by esbuild to all files that had an extension other than .mjs, .mts, .cjs, or .cts including extensionless files. So for example an extensionless file in a "type": "module" package is now treated as CommonJS instead of ESM.

0.16.11

  • Avoid a syntax error in the presence of direct eval (#2761)

    The behavior of nested function declarations in JavaScript depends on whether the code is run in strict mode or not. It would be problematic if esbuild preserved nested function declarations in its output because then the behavior would depend on whether the output was run in strict mode or not instead of respecting the strict mode behavior of the original source code. To avoid this, esbuild transforms nested function declarations to preserve the intended behavior of the original source code regardless of whether the output is run in strict mode or not:

    // Original code
    if (true) {
      function foo() {}
      console.log(!!foo)
      foo = null
      console.log(!!foo)
    }
    

... (truncated)

Commits


Updates globby from 14.0.1 to 14.0.2

Release notes

Sourced from globby's releases.

v14.0.2

  • Fix types f600250

https://github.com/sindresorhus/globby/compare/v14.0.1...v14.0.2

Commits


Updates karma-esbuild from 2.2.5 to 2.3.0

Release notes

Sourced from karma-esbuild's releases.

v2.3.0

What's Changed

Full Changelog: https://github.com/marvinhagemeister/karma-esbuild/compare/v2.2.5...v2.3.0

Commits
Maintainer changes

This version was pushed to npm by jridgewell, a new releaser for karma-esbuild since your current version.


Updates lit from 3.1.2 to 3.1.4

Release notes

Sourced from lit's releases.

lit-html@3.1.4

Patch Changes

  • #4646 abf30b3e - The value provided by the ref() directive will always be undefined when the element is disconnected.

lit@3.1.4

Patch Changes

  • #4646 abf30b3e - The value provided by the ref() directive will always be undefined when the element is disconnected.

lit-html@3.1.3

Patch Changes

  • #4570 bd881370 - Fix the lit-html marker length to be consistently 9 characters.

lit@3.1.3

Patch Changes

  • #4570 bd881370 - Fix the lit-html marker length to be consistently 9 characters.
Changelog

Sourced from lit's changelog.

3.1.4

Patch Changes

  • #4646 abf30b3e - The value provided by the ref() directive will always be undefined when the element is disconnected.

3.1.3

Patch Changes

  • #4570 bd881370 - Fix the lit-html marker length to be consistently 9 characters.
Commits


Updates mocha from 10.3.0 to 10.5.2

Release notes

Sourced from mocha's releases.

v10.5.2

What's Changed

New Contributors

Full Changelog: https://github.com/mochajs/mocha/compare/v10.5.1...v10.5.2

v10.5.1

What's Changed

New Contributors

Full Changelog: https://github.com/mochajs/mocha/compare/v10.5.0...v10.5.1

v10.5.0

:tada: Enhancements

:bug: Fixes

:nut_and_bolt: Other

v10.4.0

10.4.0 / 2024-03-26

:tada: Enhancements

:bug: Fixes

:nut_and_bolt: Other

... (truncated)

Changelog

Sourced from mocha's changelog.

10.5.2 / 2024-05-25

:bug: Fixes

10.5.1 / 2024-05-24

:bug: Fixes

10.5.0 / 2024-05-24

:tada: Enhancements

:bug: Fixes

:nut_and_bolt: Other

10.4.0 / 2024-03-26

:tada: Enhancements

:bug: Fixes

:nut_and_bolt: Other

... (truncated)

Commits
  • b2a6358 Release 10.5.2
  • a3bb86d docs: add 10.5.2 to CHANGELOG.md
  • 02c04c4 fix: better tracking of seen objects in error serialization (#5032)
  • 103c56b Release v10.5.1
  • 545b66d docs: add 10.5.1 to CHANGELOG.md
  • dbe229d fix: Add error handling for nonexistent file case with --file option (#5086)
  • b9ce511 Release v10.5.0
  • 12c88a7 Docs: add 10.5.0 to CHANGELOG.md
  • b6aa7e8 chore: rename 'master' to 'main' in docs and tooling (#5130)
  • 67a8124 fix: include stack in browser uncaught error reporting (#5107)
  • Additional commits viewable in compare view


Updates @types/mocha from 10.0.6 to 10.0.7

Commits


Updates rimraf from 5.0.5 to 5.0.7

Commits


Updates tslib from 2.6.2 to 2.6.3

Release notes

Sourced from tslib's releases.

v2.6.3

What's Changed

Full Changelog: https://github.com/microsoft/tslib/compare/v2.6.2...v2.6.3

Commits


Updates typescript from 5.3.3 to 5.5.3

Release notes

Sourced from typescript's releases.

TypeScript 5.5.3

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

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:

... (truncated)

Commits
  • f0e9921 Bump version to 5.5.3 and LKG
  • 738bd60 Cherry-pick #58966 to release-5.5 (#59002)
  • 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 (#...
  • 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

Superseded by #204.