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 14 updates #969

Closed dependabot[bot] closed 3 months ago

dependabot[bot] commented 3 months ago

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

Package From To
@biomejs/biome 1.7.0 1.8.0
cypress 13.7.3 13.11.0
esbuild 0.20.2 0.21.4
semver 7.6.0 7.6.2
stylelint 16.3.1 16.6.1
tsx 4.7.2 4.12.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.12
react-is 18.2.0 18.3.1
jsdom 24.0.0 24.1.0

Updates @biomejs/biome from 1.7.0 to 1.8.0

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.8.0

Analyzer

New features

  • Allow suppression comments to suppress individual instances of rules. This is used for the lint rule useExhaustiveDependencies, which is now able to suppress specific dependencies. Fixes #2509. Contributed by @​arendjr

Enhancements

  • Assume Astro object is always a global when processing .astro files. Contributed by @​minht11
  • Assume Vue compiler macros are globals when processing .vue files. (#2771) Contributed by @​dyc3

CLI

New features

  • New clean command. Use this new command to clean after the biome-logs directory, and remove all the log files.

    biome clean

  • Add two new options --only and --skip to the command biome lint (#58).

    The --only option allows you to run a given rule or rule group, For example, the following command runs only the style/useNamingConvention and style/noInferrableTypes rules. If the rule is disabled in the configuration, then its severity level is set to error for a recommended rule or warn otherwise.

    biome lint --only=style/useNamingConvention --only=style/noInferrableTypes

    Passing a group does not change the severity level of the rules in the group. All the disabled rules in the group will remain disabled. To ensure that the group is run, the recommended field of the group is enabled. The nursery group cannot be passed, as no rules are enabled by default in the nursery group.

    The --skip option allows you to skip the execution of a given group or a given rule. For example, the following command skips the style group and the suspicious/noExplicitAny rule.

    biome lint --skip=style --skip=suspicious/noExplicitAny

    You can also use --only and --skip together. --skip oevrrides --only. The following command executes only the rules from the style group, but the style/useNamingConvention rule.

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

1.8.0 (2024-06-04)

Analyzer

New features

  • Allow suppression comments to suppress individual instances of rules. This is used for the lint rule useExhaustiveDependencies, which is now able to suppress specific dependencies. Fixes #2509. Contributed by @​arendjr

Enhancements

  • Assume Astro object is always a global when processing .astro files. Contributed by @​minht11
  • Assume Vue compiler macros are globals when processing .vue files. (#2771) Contributed by @​dyc3

CLI

New features

  • New clean command. Use this new command to clean after the biome-logs directory, and remove all the log files.

    biome clean

  • Add two new options --only and --skip to the command biome lint (#58).

    The --only option allows you to run a given rule or rule group, For example, the following command runs only the style/useNamingConvention and style/noInferrableTypes rules. If the rule is disabled in the configuration, then its severity level is set to error for a recommended rule or warn otherwise.

    biome lint --only=style/useNamingConvention --only=style/noInferrableTypes

    Passing a group does not change the severity level of the rules in the group. All the disabled rules in the group will remain disabled. To ensure that the group is run, the recommended field of the group is enabled. The nursery group cannot be passed, as no rules are enabled by default in the nursery group.

    The --skip option allows you to skip the execution of a given group or a given rule. For example, the following command skips the style group and the suspicious/noExplicitAny rule.

    biome lint --skip=style --skip=suspicious/noExplicitAny

    You can also use --only and --skip together. --skip oevrrides --only. The following command executes only the rules from the style group, but the style/useNamingConvention rule.

... (truncated)

Commits
  • 378c05e release: v1.8.0 (#3033)
  • 44b5c29 refactor(noEvolvingAny): rename into noEvolvingTypes (#2959)
  • bc30892 feat(noUnusedFunctionParameters): add lint for unused function parameters, in...
  • 9a7d790 feat: add noLabelWithoutControl rule (#2987)
  • 21e2512 feat: allow "info" severity for analyzer rules (#3014)
  • f793b72 feat(linter): implement useDateNow (#2925)
  • e52084a feat(css_parser): add parsing css modules @​value at rule (#2985)
  • fec262f feat(linter): implement useErrorMessage (#2978)
  • b3da3ae refactor(migrate/eslint): improve naming-convention migration (#2968)
  • 125f34b ci: fix nightly version and restore update of manifest (#2953)
  • Additional commits viewable in compare view


Updates cypress from 13.7.3 to 13.11.0

Release notes

Sourced from cypress's releases.

v13.11.0

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

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
  • 09c6876 chore: release 13.11.0 (#29615)
  • e790891 feat: add option to ignore chrome preferences (#29447)
  • 4ccdd86 misc: Add generic types to net-stubbing for use in intercept and wait (#29508)
  • 687eb60 fix: Launchpad perpetual loading state, in certain circumstances (#29597)
  • f2894c4 perf: optimize reduce in wrapConsoleProps (#29501)
  • 41faa7e chore: Update Chrome (stable) to 125.0.6422.141 and Chrome (beta) to 126.0.64...
  • ea83415 chore: move questions-remain into cypress repo (#29542)
  • e6b422c chore: release @​cypress/webpack-dev-server-v3.9.0
  • cf6b29d feat: support Next.JS version 14 (#29558)
  • 2cf5cf8 chore(deps): Security upgrade micromatch from 4.0.4 to 4.0.6 (#29559)
  • Additional commits viewable in compare view


Updates esbuild from 0.20.2 to 0.21.4

Release notes

Sourced from esbuild's releases.

v0.21.4

  • Update support for import assertions and import attributes in node (#3778)

    Import assertions (the assert keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with --target=node22 or above:

    ▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with]

    example.mjs:1:40:
  1 │ import json from "esbuild/package.json" assert { type: "json" }
    │                                         ~~~~~~
    ╵                                         with

    

    Did you mean to use "with" instead of "assert"?

    Import attributes (the with keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with --target=node18.N if N is 20 or greater.

  • Fix for await transform when a label is present

    This release fixes a bug where the for await transform, which wraps the loop in a try statement, previously failed to also move the loop's label into the try statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:

    // Original code
async function test() {
  outer: for await (const x of [Promise.resolve([0, 1])]) {
    for (const y of x) if (y) break outer
    throw 'fail'
  }
}

    // Old output (with --target=es6)
function test() {
return __async(this, null, function* () {
outer: try {
for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
const x = temp.value;
for (const y of x) if (y) break outer;
throw "fail";
}
} catch (temp) {
error = [temp];
} finally {
try {
more && (temp = iter.return) && (yield temp.call(iter));
} finally {
if (error)
throw error[0];
}
}

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.4

  • Update support for import assertions and import attributes in node (#3778)

    Import assertions (the assert keyword) have been removed from node starting in v22.0.0. So esbuild will now strip them and generate a warning with --target=node22 or above:

    ▲ [WARNING] The "assert" keyword is not supported in the configured target environment ("node22") [assert-to-with]

    example.mjs:1:40:
  1 │ import json from "esbuild/package.json" assert { type: "json" }
    │                                         ~~~~~~
    ╵                                         with

    

    Did you mean to use "with" instead of "assert"?

    Import attributes (the with keyword) have been backported to node 18 starting in v18.20.0. So esbuild will no longer strip them with --target=node18.N if N is 20 or greater.

  • Fix for await transform when a label is present

    This release fixes a bug where the for await transform, which wraps the loop in a try statement, previously failed to also move the loop's label into the try statement. This bug only affects code that uses both of these features in combination. Here's an example of some affected code:

    // Original code
async function test() {
  outer: for await (const x of [Promise.resolve([0, 1])]) {
    for (const y of x) if (y) break outer
    throw 'fail'
  }
}

    // Old output (with --target=es6)
function test() {
return __async(this, null, function* () {
outer: try {
for (var iter = __forAwait([Promise.resolve([0, 1])]), more, temp, error; more = !(temp = yield iter.next()).done; more = false) {
const x = temp.value;
for (const y of x) if (y) break outer;
throw "fail";
}
} catch (temp) {
error = [temp];
} finally {
try {
more && (temp = iter.return) && (yield temp.call(iter));
} finally {
if (error)
throw error[0];
}

... (truncated)

Commits


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

Release notes

Sourced from stylelint's releases.

16.6.1

16.6.0

16.5.0

16.4.0

Changelog

Sourced from stylelint's changelog.

16.6.1

16.6.0

16.5.0

16.4.0

Commits


Updates tsx from 4.7.2 to 4.12.0

Release notes

Sourced from tsx's releases.

v4.12.0

4.12.0 (2024-06-06)

Bug Fixes

  • cjs: make resolver chainable (585f117)
  • esm: named import from CommonJS file (#33) (7c85303)

Features

  • cjs: support query for cache busting (#37) (e1464cf)

Performance Improvements

  • esm: only try extensions if file path (72d0896)

This release is also available on:

v4.11.2

4.11.2 (2024-06-03)

Bug Fixes

This release is also available on:

v4.11.1

4.11.1 (2024-06-03)

Bug Fixes

  • cjs/api: resolve correct module and types when imported (#566) (5e70105)

... (truncated)

Commits
  • 7c85303 fix(esm): named import from CommonJS file (#33)
  • e1464cf feat(cjs): support query for cache busting (#37)
  • 585f117 fix(cjs): make resolver chainable
  • 48dd7ab chore: upgrade lintroll
  • a150ac1 refactor(cjs): rename to register.ts
  • 72d0896 perf(esm): only try extensions if file path
  • a33c96a refactor(cjs): resolveTsFilename
  • 4ef6632 test: log to use util.inspect
  • e8bb062 chore: upgrade node version
  • 42e2745 chore: upgrade dev deps
  • 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
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.3

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 ... _Description has been truncated_
dependabot[bot] commented 3 months ago

Superseded by #970.