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 5 updates #1012

Closed dependabot[bot] closed 3 weeks ago

dependabot[bot] commented 3 weeks ago

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

Package From To
cypress 13.13.2 13.13.3
esbuild 0.23.0 0.23.1
stylelint 16.8.1 16.8.2
tsx 4.16.5 4.17.0
vite 5.4.0 5.4.1

Updates cypress from 13.13.2 to 13.13.3

Release notes

Sourced from cypress's releases.

v13.13.3

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

Commits


Updates esbuild from 0.23.0 to 0.23.1

Release notes

Sourced from esbuild's releases.

v0.23.1

  • Allow using the node: import prefix with es* targets (#3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
import fs from 'node:fs'
fs.open

    // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
    
import fs from "fs";
    
fs.open;
    

    // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
    
import fs from "node:fs";
    
fs.open;

  • Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

    Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

  • Fix incorrect location of certain error messages (#3845)

    This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

  • Print comments before case clauses in switch statements (#3838)

    With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

  • Fix a memory leak with pluginData (#3825)

    With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Changelog

Sourced from esbuild's changelog.

0.23.1

  • Allow using the node: import prefix with es* targets (#3821)

    The node: prefix on imports is an alternate way to import built-in node modules. For example, import fs from "fs" can also be written import fs from "node:fs". This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with --target=node14 so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as --target=node18,es2022 removes the node: prefix because none of the es* targets are known to support this feature. This release adds the support for the node: flag to esbuild's internal compatibility table for es* to allow you to use compound targets like this:

    // Original code
import fs from 'node:fs'
fs.open

    // Old output (with --bundle --format=esm --platform=node --target=node18,es2022)
    
import fs from "fs";
    
fs.open;
    

    // New output (with --bundle --format=esm --platform=node --target=node18,es2022)
    
import fs from "node:fs";
    
fs.open;

  • Fix a panic when using the CLI with invalid build flags if --analyze is present (#3834)

    Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the --analyze flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how --analyze is implemented) to a null build object. The panic has been fixed in this release.

  • Fix incorrect location of certain error messages (#3845)

    This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild.

  • Print comments before case clauses in switch statements (#3838)

    With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification).

  • Fix a memory leak with pluginData (#3825)

    With this release, the build context's internal pluginData cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return pluginData objects from onResolve and/or onLoad callbacks.

Commits


Updates stylelint from 16.8.1 to 16.8.2

Release notes

Sourced from stylelint's releases.

16.8.2

Changelog

Sourced from stylelint's changelog.

16.8.2

Commits
  • 860acdc 16.8.2
  • 7f09106 Prepare 16.8.2 (#7902)
  • 2b13454 Fix keyframe-block-no-duplicate-selectors reported ranges (#7932)
  • c3829d5 Refactor to add isVarFunction utility and rename isIgnoredFunction to `is...
  • 197400e Fix selector-max-type reported ranges (#7916)
  • b4c61d7 Add details on keys used for --cache option in documentation (#7926)
  • 108af69 Bump ignore from 5.3.1 to 5.3.2 (#7930)
  • ac83f35 Bump lint-staged from 15.2.8 to 15.2.9 (#7929)
  • 47f0a0c Bump postcss-selector-parser from 6.1.1 to 6.1.2 in the postcss group (#7928)
  • f0992a5 Fix .cjs files clean up (#7922)
  • Additional commits viewable in compare view


Updates tsx from 4.16.5 to 4.17.0

Release notes

Sourced from tsx's releases.

v4.17.0

4.17.0 (2024-08-08)

Features

This release is also available on:

Commits


Updates vite from 5.4.0 to 5.4.1

Changelog

Sourced from vite's changelog.

5.4.1 (2024-08-15)

Commits
  • b44c20c release: v5.4.1
  • 391bb49 fix(worker): handle self reference url worker in dependency for build (#17846)
  • e686d74 fix(build): avoid re-define __vite_import_meta_env__ (#17876)
  • 9018255 chore: fix picocolors import for local dev (#17884)
  • 1bda847 fix: align CorsOptions.origin type with @​types/cors (#17836)
  • e16bf1f refactor: remove handleHotUpdate from watch-package-data plugin (#17865)
  • 6700594 fix: typings for vite:preloadError (#17868)
  • d11711c fix(deps): update all non-major dependencies (#17869)
  • 4e5ce3c fix(lightningcss): search for assets with correct base path (#17856)
  • e961b31 fix: build.modulePreload.resolveDependencies is optimizable (#16083)
  • Additional commits viewable in compare view


You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 3 weeks ago

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