search

AxisCommunications / media-stream-library-js

JavaScript library to handle media streams on the command line (Node.js) and in the browser.
MIT License
303 stars 102 forks source link

chore(deps-dev): bump the dev-dependencies group across 1 directory with 12 updates #951

Closed dependabot[bot] closed 5 months ago

dependabot[bot] commented 6 months ago

Bumps the dev-dependencies group with 12 updates in the / directory:

Package From To
@biomejs/biome 1.7.0 1.7.3
cypress 13.7.3 13.8.1
esbuild 0.20.2 0.21.1
semver 7.6.0 7.6.1
stylelint 16.3.1 16.5.0
tsx 4.7.2 4.9.3
react 18.2.0 18.3.1
@types/react 18.2.79 18.3.1
react-dom 18.2.0 18.3.1
@types/react-dom 18.2.25 18.3.0
vite 5.2.8 5.2.11
react-is 18.2.0 18.3.1

Updates @biomejs/biome from 1.7.0 to 1.7.3

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.7.3

CLI

Bug fixes

Linter

New features

Bug fixes

  • noBlankTarget no longer hangs when applying a code fix (#2675).

    Previously, the following code made Biome hangs when applying a code fix.

    <a href="https://example.com" rel="" target="_blank"></a>

    Contributed by @​Conaclos

  • noRedeclare no longer panics on conditional type (#2659).

    This is a regression introduced by #2394. This regression makes noRedeclare panics on every conditional types with infer bindings.

    Contributed by @​Conaclos

  • noUnusedLabels and noConfusingLabels now ignore svelte reactive statements (#2571).

    The rules now ignore reactive Svelte blocks in Svelte components.

    <script>
$: { /* reactive block */ }
</script>

    Contributed by @​Conaclos

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

1.7.3 (2024-05-06)

CLI

Bug fixes

Linter

New features

Bug fixes

  • noBlankTarget no longer hangs when applying a code fix (#2675).

    Previously, the following code made Biome hangs when applying a code fix.

    <a href="https://example.com" rel="" target="_blank"></a>

    Contributed by @​Conaclos

  • noRedeclare no longer panics on conditional type (#2659).

    This is a regression introduced by #2394. This regression makes noRedeclare panics on every conditional types with infer bindings.

    Contributed by @​Conaclos

  • noUnusedLabels and noConfusingLabels now ignore svelte reactive statements (#2571).

    The rules now ignore reactive Svelte blocks in Svelte components.

    <script>
$: { /* reactive block */ }
</script>

... (truncated)

Commits
  • b9f90b7 release: v1.7.3 (#2722)
  • cb0182e feat(linter): implement NoUnmatchableAnbSelector (#2706)
  • f77ab54 feat(linter): implement useExplicitLengthCheck (#2631)
  • afa5004 feat(biome_css_analyzer): noUnknownSelectorPseudoElement (#2655)
  • 150dd0e feat(biome_css_analyzer): implement noDuplicateAtImportRules (#2658)
  • 773a735 fix(linter): fix typo in rule name. useConsistentBuiltinInstatiation to `us...
  • 2c70d3f release: v1.7.2 (#2651)
  • 46c378e feat(biome_css_analyzer): noUnknownFunction (#2570)
  • de063b4 feat(lint/useDefaultSwitchClause): add rule (#2605)
  • b3ed181 feat(linter): Implement useGenericFontNames (#2573)
  • Additional commits viewable in compare view


Updates cypress from 13.7.3 to 13.8.1

Release notes

Sourced from cypress's releases.

v13.8.1

Changelog: https://docs.cypress.io/guides/references/changelog#13-8-1

v13.8.0

Changelog: https://docs.cypress.io/guides/references/changelog#13-8-0

Commits


Updates esbuild from 0.20.2 to 0.21.1

Release notes

Sourced from esbuild's releases.

v0.21.1

  • Fix a regression with --keep-names (#3756)

    The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:

    // Original code
x = { get y() {} }

    // Output from version 0.21.0 (with --keep-names)
x = { get y: /* @PURE */ __name(function() {
}, "y") };
    

    // Output from this version (with --keep-names)
x = { get y() {
} };

v0.21.0

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

  • Implement the JavaScript decorators proposal (#104)

    With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:

    const log = (fn, context) => function() {
  console.log(`before ${context.name}`)
  const it = fn.apply(this, arguments)
  console.log(`after ${context.name}`)
  return it
}

    class Foo {
@​log static foo() {
console.log('in foo')
}
}
    

    // Logs "before foo", "in foo", "after foo"
Foo.foo()

    Note that this feature is different than the existing "TypeScript experimental decorators" feature that esbuild already implements. It uses similar syntax but behaves very differently, and the two are not compatible (although it's sometimes possible to write decorators that work with both). TypeScript experimental decorators will still be supported by esbuild going forward as they have been around for a long time, are very widely used, and let you do certain things that are not possible with JavaScript decorators (such as decorating function parameters). By default esbuild will parse and transform JavaScript decorators, but you can tell esbuild to parse and transform TypeScript experimental decorators instead by setting "experimentalDecorators": true in your tsconfig.json file.

    Probably at least half of the work for this feature went into creating a test suite that exercises many of the proposal's edge cases: https://github.com/evanw/decorator-tests. It has given me a reasonable level of confidence that esbuild's initial implementation is acceptable. However, I don't have access to a significant sample of real code that uses JavaScript decorators. If you're currently using JavaScript decorators in a real code base, please try out esbuild's implementation and let me know if anything seems off.

    ⚠️ WARNING ⚠️

    This proposal has been in the works for a very long time (work began around 10 years ago in 2014) and it is finally getting close to becoming part of the JavaScript language. However, it's still a work in progress and isn't a part of JavaScript yet, so keep in mind that any code that uses JavaScript decorators may need to be updated as the feature continues to evolve. The decorators proposal is pretty close to its final form but it can and likely will undergo some small behavioral adjustments before it ends up becoming a part of the standard. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.1

  • Fix a regression with --keep-names (#3756)

    The previous release introduced a regression with the --keep-names setting and object literals with get/set accessor methods, in which case the generated code contained syntax errors. This release fixes the regression:

    // Original code
x = { get y() {} }

    // Output from version 0.21.0 (with --keep-names)
x = { get y: /* @PURE */ __name(function() {
}, "y") };
    

    // Output from this version (with --keep-names)
x = { get y() {
} };

0.21.0

This release doesn't contain any deliberately-breaking changes. However, it contains a very complex new feature and while all of esbuild's tests pass, I would not be surprised if an important edge case turns out to be broken. So I'm releasing this as a breaking change release to avoid causing any trouble. As usual, make sure to test your code when you upgrade.

  • Implement the JavaScript decorators proposal (#104)

    With this release, esbuild now contains an implementation of the upcoming JavaScript decorators proposal. This is the same feature that shipped in TypeScript 5.0 and has been highly-requested on esbuild's issue tracker. You can read more about them in that blog post and in this other (now slightly outdated) extensive blog post here: https://2ality.com/2022/10/javascript-decorators.html. Here's a quick example:

    const log = (fn, context) => function() {
  console.log(`before ${context.name}`)
  const it = fn.apply(this, arguments)
  console.log(`after ${context.name}`)
  return it
}

    class Foo {
@​log static foo() {
console.log('in foo')
}
}
    

    // Logs "before foo", "in foo", "after foo"
Foo.foo()

    Note that this feature is different than the existing "TypeScript experimental decorators" feature that esbuild already implements. It uses similar syntax but behaves very differently, and the two are not compatible (although it's sometimes possible to write decorators that work with both). TypeScript experimental decorators will still be supported by esbuild going forward as they have been around for a long time, are very widely used, and let you do certain things that are not possible with JavaScript decorators (such as decorating function parameters). By default esbuild will parse and transform JavaScript decorators, but you can tell esbuild to parse and transform TypeScript experimental decorators instead by setting "experimentalDecorators": true in your tsconfig.json file.

    Probably at least half of the work for this feature went into creating a test suite that exercises many of the proposal's edge cases: https://github.com/evanw/decorator-tests. It has given me a reasonable level of confidence that esbuild's initial implementation is acceptable. However, I don't have access to a significant sample of real code that uses JavaScript decorators. If you're currently using JavaScript decorators in a real code base, please try out esbuild's implementation and let me know if anything seems off.

    ⚠️ WARNING ⚠️

... (truncated)

Commits
  • e876394 publish 0.21.1 to npm
  • 4abc387 adjust decorator source map locations
  • e7a9256 fix #3756: regression with --keep-names
  • 33cbbea run make update-compat-table
  • c6da2c3 publish 0.21.0 to npm
  • 4bc834c initial implementation of the decorators proposal (#3754)
  • 07cdbe0 some small adjustments to runtime library code
  • 71b3d9f split off lowerPrivateMethod from lowerMethod
  • 0861625 printer: preserve single-line status of block body
  • f426153 runtime: make some helper functions more compact
  • Additional commits viewable in compare view


Updates semver from 7.6.0 to 7.6.1

Release notes

Sourced from semver's releases.

v7.6.1

7.6.1 (2024-05-04)

Bug Fixes

Dependencies

Chores

Changelog

Sourced from semver's changelog.

7.6.1 (2024-05-04)

Bug Fixes

Dependencies

Chores

Commits
  • d777418 chore: release 7.6.1 (#706)
  • 988a8de deps: uninstall lru-cache (#709)
  • 5feeb7f chore: postinstall for dependabot template-oss PR
  • dd09b60 chore: bump @​npmcli/template-oss to 4.22.0
  • c570a34 fix(linting): no-unused-vars
  • ad8ff11 fix: use internal cache implementation
  • 3fabe4d deps: remove lru-cache
  • ec49cdc chore: chore: chore: postinstall for dependabot template-oss PR
  • 074156f chore: bump @​npmcli/template-oss from 4.21.3 to 4.21.4
  • b236c3d chore: add benchmarks (#696)
  • Additional commits viewable in compare view


Updates stylelint from 16.3.1 to 16.5.0

Release notes

Sourced from stylelint's releases.

16.5.0

16.4.0

Changelog

Sourced from stylelint's changelog.

16.5.0

16.4.0

Commits
  • fb54d13 16.5.0
  • 8b4beb9 Prepare 16.5.0 (#7653)
  • 45cb671 Bump @​stylelint/remark-preset from 5.0.0 to 5.1.0 in the stylelint group (#7672)
  • c6456b2 Bump remark-cli from 12.0.0 to 12.0.1 (#7673)
  • b0b8173 Bump rollup from 4.16.3 to 4.17.2 (#7671)
  • c56f714 Revert "Refactor Cosmiconfig types" (#7661)
  • f87f784 Fix shorthand-property-no-redundant-values false negatives for functions (#...
  • c85f75b Fix value-no-vendor-prefix false positives/negatives (#7658)
  • 68cb920 Fix value-no-vendor-prefix false negatives (#7654)
  • d159c1b Refactor matchesStringOrRegExp() utility (#7651)
  • Additional commits viewable in compare view


Updates tsx from 4.7.2 to 4.9.3

Release notes

Sourced from tsx's releases.

v4.9.3

4.9.3 (2024-05-06)

Bug Fixes

  • import implicit extensions from packages (8022fcf), closes #542

This release is also available on:

v4.9.2

4.9.2 (2024-05-06)

Bug Fixes

This release is also available on:

v4.9.1

4.9.1 (2024-05-04)

Bug Fixes

  • tsImport: handle importing packages (#14) (96bc596)

This release is also available on:

v4.9.0

4.9.0 (2024-05-03)

Features

... (truncated)

Commits
  • 8022fcf fix: import implicit extensions from packages
  • 3a0ea18 fix(esm): resolve absolute paths (#544)
  • b407435 docs: remove extraneous path from vscode usage (#539)
  • 96bc596 fix(tsImport): handle importing packages (#14)
  • 63631ac chore(package.json): update keywords
  • 4f515ab feat: register() & tsImport() via esm/api (#12)
  • 8eb1674 test: node 22 (#13)
  • 4c8646a test(api): CLI usage (#11)
  • 933eb7a refactor: remove unused source map logic (#10)
  • 625e6c3 chore(tsconfig): use module: preserve
  • Additional commits viewable in compare view


Updates react from 18.2.0 to 18.3.1

Release notes

Sourced from react's releases.

18.3.1 (April 26, 2024)

  • Export act from react f1338f

18.3.0 (April 25, 2024)

This release is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.

Read the React 19 Upgrade Guide for more info.

React

  • Allow writing to this.refs to support string ref codemod 909071
  • Warn for deprecated findDOMNode outside StrictMode c3b283
  • Warn for deprecated test-utils methods d4ea75
  • Warn for deprecated Legacy Context outside StrictMode 415ee0
  • Warn for deprecated string refs outside StrictMode #25383
  • Warn for deprecated defaultProps for function components #25699
  • Warn when spreading key #25697
  • Warn when using act from test-utils d4ea75

React DOM

  • Warn for deprecated unmountComponentAtNode 8a015b
  • Warn for deprecated renderToStaticNodeStream #28874
Changelog

Sourced from react's changelog.

18.3.1 (April 26, 2024)

  • Export act from react f1338f

18.3.0 (April 25, 2024)

This release is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.

Read the React 19 Upgrade Guide for more info.

React

  • Allow writing to this.refs to support string ref codemod 909071
  • Warn for deprecated findDOMNode outside StrictMode c3b283
  • Warn for deprecated test-utils methods d4ea75
  • Warn for deprecated Legacy Context outside StrictMode 415ee0
  • Warn for deprecated string refs outside StrictMode #25383
  • Warn for deprecated defaultProps for function components #25699
  • Warn when spreading key #25697
  • Warn when using act from test-utils d4ea75

React DOM

  • Warn for deprecated unmountComponentAtNode 8a015b
  • Warn for deprecated renderToStaticNodeStream #28874
Commits
Maintainer changes

This version was pushed to npm by react-bot, a new releaser for react since your current version.


Updates @types/react from 18.2.79 to 18.3.1

Commits


Updates react-dom from 18.2.0 to 18.3.1

Release notes

Sourced from react-dom's releases.

18.3.1 (April 26, 2024)

  • Export act from react f1338f

18.3.0 (April 25, 2024)

This release is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.

Read the React 19 Upgrade Guide for more info.

React

  • Allow writing to this.refs to support string ref codemod 909071
  • Warn for deprecated findDOMNode outside StrictMode c3b283
  • Warn for deprecated test-utils methods d4ea75
  • Warn for deprecated Legacy Context outside StrictMode 415ee0
  • Warn for deprecated string refs outside StrictMode #25383
  • Warn for deprecated defaultProps for function components #25699
  • Warn when spreading key #25697
  • Warn when using act from test-utils d4ea75

React DOM

  • Warn for deprecated unmountComponentAtNode 8a015b
  • Warn for deprecated renderToStaticNodeStream #28874
Changelog

Sourced from react-dom's changelog.

18.3.1 (April 26, 2024)

  • Export act from react f1338f

18.3.0 (April 25, 2024)

This release is identical to 18.2 but adds warnings for deprecated APIs and other changes that are needed for React 19.

Read the React 19 Upgrade Guide for more info.

React

  • Allow writing to this.refs to support string ref codemod 909071
  • Warn for deprecated findDOMNode outside StrictMode c3b283
  • Warn for deprecated test-utils methods d4ea75
  • Warn for deprecated Legacy Context outside StrictMode 415ee0
  • Warn for deprecated string refs outside StrictMode #25383
  • Warn for deprecated defaultProps for function components #25699
  • Warn when spreading key #25697
  • Warn when using act from test-utils d4ea75

React DOM

  • Warn for deprecated unmountComponentAtNode 8a015b
  • Warn for deprecated renderToStaticNodeStream #28874
Commits
  • d6c42f7 Bump to 18.3.1
  • 8a015b6 Add deprecation warning for unmountComponentAtNode
  • c3b2839 Add deprecation warning for findDOMNode
  • d4ea75d ReactDOMTestUtils deprecation warnings
  • 7548c01 Deprecate renderToStaticNodeStream (#28872) (#28874)
  • 5894232 Enable warning for defaultProps on function components for everyone (#25699)
  • c2a246e Turn on string ref deprecation warning for everybody (not codemoddable) (#25383)
  • 2cfb474 Bump version from 18.2 to 18.3
  • See full diff in compare view
Maintainer changes

This version was pushed to npm by react-bot, a new relea... _Description has been truncated_

dependabot[bot] commented 5 months ago

Superseded by #952.