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 15 updates #985

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

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

Package From To
@biomejs/biome 1.7.0 1.8.3
cypress 13.7.3 13.12.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.8
typescript 5.4.5 5.5.2
@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.2
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.3

Release notes

Sourced from @​biomejs/biome's releases.

CLI v1.8.3

CLI

Bug fixes

  • Fix #3104 by suppressing node warnings when using biome migrate. Contributed by @​SuperchupuDev

  • Force colors to be off when using the GitHub reporter to properly create annotations in GitHub actions (#3148). Contributed by @​Sec-ant

Parser

Bug fixes

Formatter

Bug fixes

Linter

New features

Bug fixes

  • useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #3247. Contributed by @​Conaclos
  • Fixes #3066 by taking into account the dependencies declared in the package.json. Contributed by @​ematipico
  • The code action of the useArrowFunction rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #3292. Contributed by @​Sec-ant

Enhancements

  • Enhance tailwind sorting lint rule #1274 with variant support.

    Every preconfigured variant is assigned a weight that concurs on establishing the output sorting order. Since nesting variants on the same utility class is possible, the resulting weight is the Bitwise XOR of all the variants weight for that class. Dynamic variants (e.g. has-[.custom-class], group-[:checked]) are also supported and they take the weight of their base variant name the custom value attached (e.g. has-[.custom-class] takes has weight). Arbitrary variants (e.g. [&nth-child(2)]) don't have a weight assigned and they are placed after every known variant. Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last. Screen variants (e.g. sm:, max-md:, min-lg:) are not supported yet.

    Contributed by @​lutaok

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

v1.8.3 (2024-06-27)

CLI

Bug fixes

  • Fix #3104 by suppressing node warnings when using biome migrate. Contributed by @​SuperchupuDev

  • Force colors to be off when using the GitHub reporter to properly create annotations in GitHub actions (#3148). Contributed by @​Sec-ant

Parser

Bug fixes

Formatter

Bug fixes

Linter

New features

Bug fixes

  • useConsistentArrayType and useShorthandArrayType now ignore Array in the extends and implements clauses. Fix #3247. Contributed by @​Conaclos
  • Fixes #3066 by taking into account the dependencies declared in the package.json. Contributed by @​ematipico
  • The code action of the useArrowFunction rule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #3292. Contributed by @​Sec-ant

Enhancements

  • Enhance tailwind sorting lint rule #1274 with variant support.

    Every preconfigured variant is assigned a weight that concurs on establishing the output sorting order. Since nesting variants on the same utility class is possible, the resulting weight is the Bitwise XOR of all the variants weight for that class. Dynamic variants (e.g. has-[.custom-class], group-[:checked]) are also supported and they take the weight of their base variant name the custom value attached (e.g. has-[.custom-class] takes has weight). Arbitrary variants (e.g. [&nth-child(2)]) don't have a weight assigned and they are placed after every known variant. Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last. Screen variants (e.g. sm:, max-md:, min-lg:) are not supported yet.

    Contributed by @​lutaok

v1.8.2 (2024-06-20)

... (truncated)

Commits


Updates cypress from 13.7.3 to 13.12.0

Release notes

Sourced from cypress's releases.

v13.12.0

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

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


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

Release notes

Sourced from tsx's releases.

v4.15.8

4.15.8 (2024-06-28)

Bug Fixes

  • cjs: implicit resolution to correctly try extensions (b94482d)
  • cjs: leaking implicit extension resolver (ae2a1bc)

This release is also available on:

v4.15.7

4.15.7 (2024-06-21)

Bug Fixes


This release is also available on:

v4.15.6

4.15.6 (2024-06-17)

Bug Fixes

  • minimum Node version in warning for module.register() (#592) (cb27d4d)

This release is also available on:

v4.15.5

4.15.5 (2024-06-15)

... (truncated)

Commits
  • ae2a1bc fix(cjs): leaking implicit extension resolver
  • b94482d fix(cjs): implicit resolution to correctly try extensions
  • d120d14 chore: improve issue template
  • 56eb82b refactor(esm): simplify resolve code
  • bcf96c7 test: assert extension resolution order in node_modules
  • fc41979 chore: correct contributing link in bug report template (#598)
  • 98d9f6d docs: fix favicon in vercel
  • 26d633c fix: nyc coverage compatibility (#54)
  • f714d74 docs: add logo as favicon
  • 3ee4c59 chore(deps): update dependency node to v20.15.0 (#595)
  • Additional commits viewable in compare view


Updates typescript from 5.4.5 to 5.5.2

Release notes

Sourced from typescript's releases.

TypeScript 5.5

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.5 RC

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

TypeScript 5.5 Beta

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

Commits
dependabot[bot] commented 2 months ago

Superseded by #986.