search

AxisCommunications / media-stream-library-js

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

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

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 3 months ago

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

Package From To
@biomejs/biome 1.7.0 1.7.3
cypress 13.7.3 13.10.0
esbuild 0.20.2 0.21.3
semver 7.6.0 7.6.2
stylelint 16.3.1 16.6.0
tsx 4.7.2 4.11.0
@vitejs/plugin-react 4.2.1 4.3.0
react 18.2.0 18.3.1
@types/react 18.2.79 18.3.3
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>

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

Release notes

Sourced from cypress's releases.

v13.10.0

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

v13.9.0

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

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

Release notes

Sourced from esbuild's releases.

v0.21.3

  • Implement the decorator metadata proposal (#3760)

    This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:

    // Shim the "Symbol.metadata" symbol
Symbol.metadata ??= Symbol('Symbol.metadata')

    const track = (_, context) => {
(context.metadata.names ||= []).push(context.name)
}
    

    class Foo {
@​track foo = 1
@​track bar = 2
}
    

    // Prints ["foo", "bar"]
console.log(Foo[Symbol.metadata].names)

    ⚠️ WARNING ⚠️

    This proposal has been marked as "stage 3" which means "recommended for implementation". 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 decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

  • Fix bundled decorators in derived classes (#3768)

    In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:

    class Foo extends Object {
  @(x => x) foo() {
    return Foo
  }
}
console.log(new Foo().foo())

  • Fix tsconfig.json files inside symlinked directories (#3767)

    This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

v0.21.2

  • Correct this in field and accessor decorators (#3761)

    This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:

    const dec = () => function() { this.bar = true }

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.3

  • Implement the decorator metadata proposal (#3760)

    This release implements the decorator metadata proposal, which is a sub-proposal of the decorators proposal. Microsoft shipped the decorators proposal in TypeScript 5.0 and the decorator metadata proposal in TypeScript 5.2, so it's important that esbuild also supports both of these features. Here's a quick example:

    // Shim the "Symbol.metadata" symbol
Symbol.metadata ??= Symbol('Symbol.metadata')

    const track = (_, context) => {
(context.metadata.names ||= []).push(context.name)
}
    

    class Foo {
@​track foo = 1
@​track bar = 2
}
    

    // Prints ["foo", "bar"]
console.log(Foo[Symbol.metadata].names)

    ⚠️ WARNING ⚠️

    This proposal has been marked as "stage 3" which means "recommended for implementation". 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 decorator metadata may need to be updated as the feature continues to evolve. If/when that happens, I will update esbuild's implementation to match the specification. I will not be supporting old versions of the specification.

  • Fix bundled decorators in derived classes (#3768)

    In certain cases, bundling code that uses decorators in a derived class with a class body that references its own class name could previously generate code that crashes at run-time due to an incorrect variable name. This problem has been fixed. Here is an example of code that was compiled incorrectly before this fix:

    class Foo extends Object {
  @(x => x) foo() {
    return Foo
  }
}
console.log(new Foo().foo())

  • Fix tsconfig.json files inside symlinked directories (#3767)

    This release fixes an issue with a scenario involving a tsconfig.json file that extends another file from within a symlinked directory that uses the paths feature. In that case, the implicit baseURL value should be based on the real path (i.e. after expanding all symbolic links) instead of the original path. This was already done for other files that esbuild resolves but was not yet done for tsconfig.json because it's special-cased (the regular path resolver can't be used because the information inside tsconfig.json is involved in path resolution). Note that this fix no longer applies if the --preserve-symlinks setting is enabled.

0.21.2

  • Correct this in field and accessor decorators (#3761)

    This release changes the value of this in initializers for class field and accessor decorators from the module-level this value to the appropriate this value for the decorated element (either the class or the instance). It was previously incorrect due to lack of test coverage. Here's an example of a decorator that doesn't work without this change:

... (truncated)

Commits
  • efa3dd2 publish 0.21.3 to npm
  • 5e7cf25 fix #3760: implement decorator metadata proposal
  • bd0b13b lowering: always propagate class expression names
  • 90acd14 explicit bitwise operators for initializer flags
  • ba548df move decorator initializer list to after the class
  • 66b7c6d fix #3768: bundled decorators in derived classes
  • 6e6f15f fix #3767: tsconfig.json files inside symlinks
  • b7dcb95 transform: reuse lowerField for auto-accessors
  • b24180e publish 0.21.2 to npm
  • f82e0ad fix #3761: this in field and accessor decorators
  • Additional commits viewable in compare view


Updates semver from 7.6.0 to 7.6.2

Release notes

Sourced from semver's releases.

v7.6.2

7.6.2 (2024-05-09)

Bug Fixes

v7.6.1

7.6.1 (2024-05-04)

Bug Fixes

Dependencies

Chores

Changelog

Sourced from semver's changelog.

7.6.2 (2024-05-09)

Bug Fixes

7.6.1 (2024-05-04)

Bug Fixes

Dependencies

Chores

Commits
  • eb1380b chore: release 7.6.2 (#714)
  • 6466ba9 fix(lru): use map.delete() directly (#713)
  • 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
  • Additional commits viewable in compare view


Updates stylelint from 16.3.1 to 16.6.0

Release notes

Sourced from stylelint's releases.

16.6.0

16.5.0

16.4.0

Changelog

Sourced from stylelint's changelog.

16.6.0

16.5.0

16.4.0

Commits
  • 141c511 16.6.0
  • 71d3d4b Prepare 16.6.0 (#7681)
  • c0b52c5 Fix missing GitHub Sponsor for npm fund (#7707)
  • 8364760 Fix selector-not-notation autofix of the "simple" option (#7703)
  • c4ea9d4 Refactor types for flattenNestedSelectorsForRule and `getSelectorSourceInde...
  • e0d8fdd Refactor to jsonFormatter (#7705)
  • c76a5d3 Fix no-descending-specificity end positions (#7701)
  • 024fa7e Refactor to add selectorSourceIndex utility (#7702)
  • 2427d9d Bump @​csstools/selector-specificity from 3.1.0 to 3.1.1 (#7697)
  • a6a8447 Bump @​changesets/cli from 2.27.1 to 2.27.3 in the changesets group across 1 d...
  • Additional commits viewable in compare view


Updates tsx from 4.7.2 to 4.11.0

Release notes

Sourced from tsx's releases.

v4.11.0

4.11.0 (2024-05-23)

Bug Fixes

  • only error on invalid tsconfig if explicitly passed in (#30) (b6bf39b)

Features

  • esm api: configurable tsconfig (3f42ae3)

This release is also available on:

v4.10.5

4.10.5 (2024-05-18)

Bug Fixes

This release is also available on:

v4.10.4

4.10.4 (2024-05-17)

Bug Fixes

This release is also available on:

... (truncated)

Commits
  • b6bf39b fix: only error on invalid tsconfig if explicitly passed in (#30)
  • 3f42ae3 feat(esm api): configurable tsconfig
  • 52d696c docs: use .md extension in links
  • b54131c refactor: reuse tsconfig util
  • eeaefd6 test: separate tsconfig tests
  • 9cf2115 test: refactor organize fixtures
  • a71c437 chore: update tsconfig.json
  • 86cf87c fix: handle parsing variable of
  • 4a8a2dc fix(cjs): support file url (#18)
  • 942e9bc fix: V8 coverage support
  • Additional commits viewable in compare view


Updates @vitejs/plugin-react from 4.2.1 to 4.3.0

Release notes

Sourced from @​vitejs/plugin-react's releases.

v4.3.0

Fix support for React compiler

Don't set retainLines: true when the React compiler is used. This creates whitespace issues and the compiler is modifying the JSX too much to get correct line numbers after that. If you want to use the React compiler and get back correct line numbers for tools like vite-plugin-react-click-to-component to work, you should update your config to something like:

export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', {}]]
  if (command === 'serve') {
    babelPlugins.push(['@babel/plugin-transform-react-jsx-development', {}])
  }

return {
plugins: [react({ babel: { plugins: babelPlugins } })],
}
})

Support HMR for class components

This is a long overdue and should fix some issues people had with HMR when migrating from CRA.

Changelog

Sourced from @​vitejs/plugin-react's changelog.

4.3.0 (2024-05-22)

Fix support for React compiler

Don't set retainLines: true when the React compiler is used. This creates whitespace issues and the compiler is modifying the JSX too much to get correct line numbers after that. If you want to use the React compiler and get back correct line numbers for tools like vite-plugin-react-click-to-component to work, you should update your config to something like:

export default defineConfig(({ command }) => {
  const babelPlugins = [['babel-plugin-react-compiler', {}]]
  if (command === 'serve') {
    babelPlugins.push(['@babel/plugin-transform-react-jsx-development', {}])
  }

return {
plugins: [react({ babel: { plugins: babelPlugins } })],
}
})

Support HMR for class components

This is a long overdue and should fix some issues people had with HMR when migrating from CRA.

Commits


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
  • f1338f8 Export React.act fr... _Description has been truncated_
dependabot[bot] commented 3 months ago

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