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 #973

Closed dependabot[bot] closed 2 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.1
cypress 13.7.3 13.11.0
esbuild 0.20.2 0.21.5
semver 7.6.0 7.6.2
stylelint 16.3.1 16.6.1
tsx 4.7.2 4.15.4
@vitejs/plugin-react 4.2.1 4.3.1
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.3.0
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.1

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.8.1

CLI

Bug fixes

  • Fix #3069, prevent overwriting paths when using --staged or --changed options. Contributed by @​unvalley
  • Fix a case where the file link inside a diagnostic wasn't correctly displayed inside a terminal run by VSCode. Contributed by @​uncenter

Configuration

Bug fixes

  • Fix #3067, by assigning the correct default value to indentWidth. Contributed by @​ematipico

Formatter

Bug fixes

  • Fix the bug where whitespace after the & character in CSS nesting was incorrectly trimmed, ensuring proper targeting of child classes #3061. Contributed by @​denbezrukov
  • Fix #3068 where the CSS formatter was inadvertently converting variable declarations and function calls to lowercase. Contributed by @​denbezrukov
  • Fix the formatting of CSS grid layout properties. Contributed by @​denbezrukov

Linter

Bug fixes

  • The noEmptyBlock css lint rule now treats empty blocks containing comments as valid ones. Contributed by @​Sec-ant

  • useLiteralKeys no longer reports quoted member names (#3085).

    Previously useLiteralKeys reported quoted member names that can be unquoted. For example, the rule suggested the following fix:

    - const x = { "prop": 0 };
+ const x = { prop: 0 };

    This conflicted with the option quoteProperties of our formatter.

    The rule now ignores quoted member names.

    Contributed by @​Conaclos

  • noEmptyInterface now ignores empty interfaces in ambient modules (#3110). Contributed by @​Conaclos

  • noUnusedVariables and noUnusedFunctionParameters no longer report the parameters of a constructor type (#3135).

    Previously, arg was reported as unused in a constructor type like:

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

v1.8.1 (2024-06-10)

Analyzer

CLI

Bug fixes

  • Fix #3069, prevent overwriting paths when using --staged or --changed options. Contributed by @​unvalley
  • Fix a case where the file link inside a diagnostic wasn't correctly displayed inside a terminal run by VSCode. Contributed by @​uncenter

Configuration

Bug fixes

  • Fix #3067, by assigning the correct default value to indentWidth. Contributed by @​ematipico

Editors

Formatter

Bug fixes

  • Fix the bug where whitespace after the & character in CSS nesting was incorrectly trimmed, ensuring proper targeting of child classes #3061. Contributed by @​denbezrukov
  • Fix #3068 where the CSS formatter was inadvertently converting variable declarations and function calls to lowercase. Contributed by @​denbezrukov
  • Fix the formatting of CSS grid layout properties. Contributed by @​denbezrukov

JavaScript APIs

Linter

Bug fixes

  • The noEmptyBlock css lint rule now treats empty blocks containing comments as valid ones. Contributed by @​Sec-ant

  • useLiteralKeys no longer reports quoted member names (#3085).

    Previously useLiteralKeys reported quoted member names that can be unquoted. For example, the rule suggested the following fix:

    - const x = { "prop": 0 };
+ const x = { prop: 0 };

    This conflicted with the option quoteProperties of our formatter.

    The rule now ignores quoted member names.

    Contributed by @​Conaclos

... (truncated)

Commits


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

Release notes

Sourced from esbuild's releases.

v0.21.5

  • Fix Symbol.metadata on classes without a class decorator (#3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
import tasty from "./bagel.js" with { type: "bagel" }

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
import tasty from "./tasty.bagel" with { type: "bagel" }

  • Support import attributes with glob-style imports (#3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
  const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
  return unpackLocale(locale, data)
}

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data

    example.ts:2:28:
  2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
    ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.21.5

  • Fix Symbol.metadata on classes without a class decorator (#3781)

    This release fixes a bug with esbuild's support for the decorator metadata proposal. Previously esbuild only added the Symbol.metadata property to decorated classes if there was a decorator on the class element itself. However, the proposal says that the Symbol.metadata property should be present on all classes that have any decorators at all, not just those with a decorator on the class element itself.

  • Allow unknown import attributes to be used with the copy loader (#3792)

    Import attributes (the with keyword on import statements) are allowed to alter how that path is loaded. For example, esbuild cannot assume that it knows how to load ./bagel.js as type bagel:

    // This is an error with "--bundle" without also using "--external:./bagel.js"
import tasty from "./bagel.js" with { type: "bagel" }

    Because of that, bundling this code with esbuild is an error unless the file ./bagel.js is external to the bundle (such as with --bundle --external:./bagel.js).

    However, there is an additional case where it's ok for esbuild to allow this: if the file is loaded using the copy loader. That's because the copy loader behaves similarly to --external in that the file is left external to the bundle. The difference is that the copy loader copies the file into the output folder and rewrites the import path while --external doesn't. That means the following will now work with the copy loader (such as with --bundle --loader:.bagel=copy):

    // This is no longer an error with "--bundle" and "--loader:.bagel=copy"
import tasty from "./tasty.bagel" with { type: "bagel" }

  • Support import attributes with glob-style imports (#3797)

    This release adds support for import attributes (the with option) to glob-style imports (dynamic imports with certain string literal patterns as paths). These imports previously didn't support import attributes due to an oversight. So code like this will now work correctly:

    async function loadLocale(locale: string): Locale {
  const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
  return unpackLocale(locale, data)
}

    Previously this didn't work even though esbuild normally supports forcing the JSON loader using an import attribute. Attempting to do this used to result in the following error:

    ✘ [ERROR] No loader is configured for ".data" files: locales/en-US.data

    example.ts:2:28:
  2 │   const data = await import(`./locales/${locale}.data`, { with: { type: 'json' } })
    ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~

    In addition, this change means plugins can now access the contents of with for glob-style imports.

  • Support ${configDir} in tsconfig.json files (#3782)

    This adds support for a new feature from the upcoming TypeScript 5.5 release. The character sequence ${configDir} is now respected at the start of baseUrl and paths values, which are used by esbuild during bundling to correctly map import paths to file system paths. This feature lets base tsconfig.json files specified via extends refer to the directory of the top-level tsconfig.json file. Here is an example:

... (truncated)

Commits
  • fc37c2f publish 0.21.5 to npm
  • cb11924 fix Symbol.metadata errors in decorator tests
  • b93a2a9 fix #3781: add metadata to all decorated classes
  • 953dae9 fix #3797: import attributes and glob-style import
  • 98cb2ed fix #3782: support ${configDir} in tsconfig.json
  • 8e6603b run make update-compat-table
  • db1b8ca fix #3792: import attributes and the copy loader
  • de572d0 fix non-deterministic import attribute plugin test
  • ae8d1b4 fix #3794: --supported:object-accessors=false
  • 67cbf87 publish 0.21.4 to npm
  • 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.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.15.4

Release notes

Sourced from tsx's releases.

v4.15.4

4.15.4 (2024-06-13)

Bug Fixes

  • cjs: handle re-exports from relative paths (5166122)

This release is also available on:

v4.15.3

4.15.3 (2024-06-13)

Bug Fixes

  • cjs: load json with namespace (6b03a38)

This release is also available on:

v4.15.2

4.15.2 (2024-06-10)

Bug Fixes

  • esm: resolve implicit extension in package subpath (7e1fe22)

This release is also available on:

v4.15.1

4.15.1 (2024-06-09)

Bug Fixes

... (truncated)

Commits
  • 4c53853 test(esm): confirm cjsInterop effectiveness
  • 5166122 fix(cjs): handle re-exports from relative paths
  • 531fafa refactor(cjs): move implicitResolver outside of closure
  • 2a7deea chore(issue): add monetary value
  • 6b03a38 fix(cjs): load json with namespace
  • 817d6b2 chore: improve issue close message
  • 7e1fe22 fix(esm): resolve implicit extension in package subpath
  • fb247eb fix: prevent ERR_DOMAIN_CANNOT_SET_UNCAUGHT_EXCEPTION_CAPTURE
  • c67d746 feat: esbuild 0.21.4
  • edbdfdf feat: esbuild 0.21.3
  • Additional commits viewable in compare view


Updates @vitejs/plugin-react from 4.2.1 to 4.3.1

Release notes

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

v4.3.1

Fix support for React Compiler with React 18

The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom runtimeModule: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43

When using a custom runtimeModule, the plugin will not try to pre-optimize react/compiler-runtime dependency.

Reminder: Vite expect code outside of node_modules to be ESM, so you will need to update the gist with import React from 'react'.

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.1 (2024-06-10)

Fix support for React Compiler with React 18

The previous version made this assumption that the compiler was only usable with React 19, but it's possible to use it with React 18 and a custom runtimeModule: https://gist.github.com/poteto/37c076bf112a07ba39d0e5f0645fec43

When using a custom runtimeModule, the plugin will not try to pre-optimize react/compiler-runtime dependency.

Reminder: Vite expect code outside of node_modules to be ESM, so you will need to update the gist with import React from 'react'.

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

Superseded by #975.