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 4 updates #179

Closed dependabot[bot] closed 6 months ago

dependabot[bot] commented 7 months ago

Bumps the dev-deps group with 4 updates: @typescript-eslint/eslint-plugin, @typescript-eslint/parser, esbuild and karma-esbuild.

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

Release notes

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

v7.1.1

7.1.1 (2024-03-04)

🩹 Fixes

  • typescript-eslint: apply ignores to all extended configs passed to config helper function (#8567)

❤️ Thank You

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

Changelog

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

7.1.1 (2024-03-04)

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

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

Commits
  • 88b7463 chore(release): publish 7.1.1
  • 6954a4a test(eslint-plugin): [no-unused-vars] add export import namespace testcase (#...
  • See full diff in compare view


Updates @typescript-eslint/parser from 7.1.0 to 7.1.1

Release notes

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

v7.1.1

7.1.1 (2024-03-04)

🩹 Fixes

  • typescript-eslint: apply ignores to all extended configs passed to config helper function (#8567)

❤️ Thank You

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

Changelog

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

7.1.1 (2024-03-04)

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.

Commits


Updates esbuild from 0.14.54 to 0.20.1

Release notes

Sourced from esbuild's releases.

v0.20.1

  • Fix a bug with the CSS nesting transform (#3648)

    This release fixes a bug with the CSS nesting transform for older browsers where the generated CSS could be incorrect if a selector list contained a pseudo element followed by another selector. The bug was caused by incorrectly mutating the parent rule's selector list when filtering out pseudo elements for the child rules:

    /* Original code */
    .foo {
      &:after,
      & .bar {
        color: red;
      }
    }
    

    /* Old output (with --supported:nesting=false) */ .foo .bar, .foo .bar { color: red; }

    /* New output (with --supported:nesting=false) */ .foo:after, .foo .bar { color: red; }

  • Constant folding for JavaScript inequality operators (#3645)

    This release introduces constant folding for the < > <= >= operators. The minifier will now replace these operators with true or false when both sides are compile-time numeric or string constants:

    // Original code
    console.log(1 < 2, '🍕' > '🧀')
    

    // Old output (with --minify) console.log(1<2,"🍕">"🧀");

    // New output (with --minify) console.log(!0,!1);

  • Better handling of __proto__ edge cases (#3651)

    JavaScript object literal syntax contains a special case where a non-computed property with a key of __proto__ sets the prototype of the object. This does not apply to computed properties or to properties that use the shorthand property syntax introduced in ES6. Previously esbuild didn't correctly preserve the "sets the prototype" status of properties inside an object literal, meaning a property that sets the prototype could accidentally be transformed into one that doesn't and vice versa. This has now been fixed:

    // Original code
    function foo(__proto__) {
      return { __proto__: __proto__ } // Note: sets the prototype
    

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


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

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