search

unchartedsoftware / grafer

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

build(deps-dev): bump the dev-deps group with 8 updates #157

Closed dependabot[bot] closed 11 months ago

dependabot[bot] commented 11 months ago

Bumps the dev-deps group with 8 updates:

Package From To
@types/chai 4.3.10 4.3.11
@types/mocha 10.0.4 10.0.6
@types/resize-observer-browser 0.1.10 0.1.11
@typescript-eslint/eslint-plugin 6.12.0 6.13.1
@typescript-eslint/parser 6.12.0 6.13.1
esbuild 0.14.54 0.19.8
karma-esbuild 2.2.5 2.3.0
typescript 5.2.2 5.3.2

Updates @types/chai from 4.3.10 to 4.3.11

Commits


Updates @types/mocha from 10.0.4 to 10.0.6

Commits


Updates @types/resize-observer-browser from 0.1.10 to 0.1.11

Commits


Updates @typescript-eslint/eslint-plugin from 6.12.0 to 6.13.1

Release notes

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

v6.13.1

6.13.1 (2023-11-28)

Bug Fixes

  • default to parse all JSDoc and provide options to configure it (#7999) (779e13e)

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

v6.13.0

6.13.0 (2023-11-27)

Note for eslint plugin authors and other API consumers

TypeScript v5.3 shipped with a type change that was incompatible with our types. This change has been fixed and will be released in v5.3.3. Until that time you can work around this error using skipLibCheck.

Bug Fixes

  • typescript-estree: ensure backwards compat with pre-5.3 import attributes (#7967) (810fc8c)

Features

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

Changelog

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

6.13.1 (2023-11-28)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

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

6.13.0 (2023-11-27)

Note: Version bump only for package @​typescript-eslint/eslint-plugin

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

Commits


Updates @typescript-eslint/parser from 6.12.0 to 6.13.1

Release notes

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

v6.13.1

6.13.1 (2023-11-28)

Bug Fixes

  • default to parse all JSDoc and provide options to configure it (#7999) (779e13e)

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

v6.13.0

6.13.0 (2023-11-27)

Note for eslint plugin authors and other API consumers

TypeScript v5.3 shipped with a type change that was incompatible with our types. This change has been fixed and will be released in v5.3.3. Until that time you can work around this error using skipLibCheck.

Bug Fixes

  • typescript-estree: ensure backwards compat with pre-5.3 import attributes (#7967) (810fc8c)

Features

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

Changelog

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

6.13.1 (2023-11-28)

Note: Version bump only for package @​typescript-eslint/parser

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

6.13.0 (2023-11-27)

Note: Version bump only for package @​typescript-eslint/parser

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

Commits


Updates esbuild from 0.14.54 to 0.19.8

Release notes

Sourced from esbuild's releases.

v0.19.8

  • Add a treemap chart to esbuild's bundle analyzer (#2848)

    The bundler analyzer on esbuild's website (https://esbuild.github.io/analyze/) now has a treemap chart type in addition to the two existing chart types (sunburst and flame). This should be more familiar for people coming from other similar tools, as well as make better use of large screens.

  • Allow decorators after the export keyword (#104)

    Previously esbuild's decorator parser followed the original behavior of TypeScript's experimental decorators feature, which only allowed decorators to come before the export keyword. However, the upcoming JavaScript decorators feature also allows decorators to come after the export keyword. And with TypeScript 5.0, TypeScript now also allows experimental decorators to come after the export keyword too. So esbuild now allows this as well:

    // This old syntax has always been permitted:
@decorator export class Foo {}
@decorator export default class Foo {}

    // This new syntax is now permitted too:
export @​decorator class Foo {}
export default @​decorator class Foo {}

    In addition, esbuild's decorator parser has been rewritten to fix several subtle and likely unimportant edge cases with esbuild's parsing of exports and decorators in TypeScript (e.g. TypeScript apparently does automatic semicolon insertion after interface and export interface but not after export default interface).

  • Pretty-print decorators using the same whitespace as the original

    When printing code containing decorators, esbuild will now try to respect whether the original code contained newlines after the decorator or not. This can make generated code containing many decorators much more compact to read:

    // Original code
class Foo {
  @a @b @c abc
  @x @y @z xyz
}

    // Old output
class Foo {
@​a
@​b
@​c
abc;
@​x
@​y
@​z
xyz;
}
    

    // New output
class Foo {
@​a @​b @​c abc;
@​x @​y @​z xyz;
}

... (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
  • e97bd67 publish 0.19.8 to npm
  • 65b3058 mention the treemap in the release notes (#2848)
  • 16883d4 add whitespace change to release notes
  • 7383d0d decorators: printing preserves newline-tail status
  • 7edc83d reword an experimental decorators error message
  • f3d5352 remove a now-unused field
  • e755189 ts: forbid regular decorators on declare fields
  • 69c9e7f allow decorators to come after export (#104)
  • 7baefdb fix a panic with "export default interface\n"
  • a8313d2 use "check" for decorator validation, not "guess"
  • Additional commits viewable in compare view


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 typescript from 5.2.2 to 5.3.2

Release notes

Sourced from typescript's releases.

TypeScript 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.3 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.3 Beta

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on npm.

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 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 11 months ago

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