Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump the external-dependencies group with 10 updates #2436

Merged
merged 1 commit into from Feb 9, 2024
Merged

Bump the external-dependencies group with 10 updates #2436

merged 1 commit into from Feb 9, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 9, 2024

Bumps the external-dependencies group with 10 updates:

Package From To
dexie 3.2.4 3.2.5
i18next 23.7.16 23.8.2
tldts 6.1.2 6.1.10
web-ext 7.10.0 7.11.0
@fingerprintjs/fingerprintjs 4.2.1 4.2.2
@types/chrome 0.0.256 0.0.260
esbuild 0.19.11 0.20.0
jsdom 23.2.0 24.0.0
sass 1.69.7 1.70.0
mocha 10.2.0 10.3.0

Updates dexie from 3.2.4 to 3.2.5

Release notes

Sourced from dexie's releases.

Dexie v3.2.5

Bugfix

  • Fix issue with BigInt64Array (#1890) (and BigUint64Array) - cherry picked from 4.0.1-beta.8
Commits
  • 07454f5 Build output
  • 54f042d Merge remote-tracking branch 'origin/releases-3' into master-3
  • 0e4ef3e Releasing v3.2.5
  • 88b9e61 Replace 1n with BigInt(1) for tests on old browsers to run in release script
  • 820530e npm audit fix
  • d7f8d85 Removing a 4.0 test that happened to slip through to 3.x in a cherry-pick ope...
  • 7c2f083 Support BigUint64Array (not just BigInt64Array)
  • 188fbba Fix issue with BigInt64Array (#1892)
  • 5966dfd Added gh-actions for 3x (#1751)
  • 74891ca Workaround for UnknownError in Chrome (#543)
  • Additional commits viewable in compare view

Updates i18next from 23.7.16 to 23.8.2

Release notes

Sourced from i18next's releases.

v23.8.2

  • optimize addResources to address 2130

v23.8.1

  • types: support stricter typechecking for returnEmptyString and returnNull 2129

v23.8.0

  • improve performance by reducing array slices and RegExp recreation 2128

v23.7.20

  • optimize: consistent _zero special handling also for defaultValue_zero 2124
  • intl plural rule for dev is now en (consistent with v3 compatibility)

v23.7.19

  • fix: consistent _zero special handling also for defaultValue_zero 2124

v23.7.18

  • types: support readonly defaultNS 2123

v23.7.17

  • types: fix support for defaultNS as array (fixes 2118) 2121
  • types: fix typo in CustomInstanceExtensions 2122
Changelog

Sourced from i18next's changelog.

23.8.2

  • optimize addResources to address 2130

23.8.1

  • types: support stricter typechecking for returnEmptyString and returnNull 2129

23.8.0

  • improve performance by reducing array slices and RegExp recreation 2128

23.7.20

  • optimize: consistent _zero special handling also for defaultValue_zero 2124
  • intl plural rule for dev is now en (consistent with v3 compatibility)

23.7.19

  • fix: consistent _zero special handling also for defaultValue_zero 2124

23.7.18

  • types: support readonly defaultNS 2123

23.7.17

  • types: fix support for defaultNS as array (fixes 2118) 2121
  • types: fix typo in CustomInstanceExtensions 2122
Commits

Updates tldts from 6.1.2 to 6.1.10

Release notes

Sourced from tldts's releases.

v6.1.10

馃摐 Update Public Suffix List

馃敥 Dependencies

Authors: 2

v6.1.9

馃摐 Update Public Suffix List

Authors: 1

v6.1.8

馃摐 Update Public Suffix List

Authors: 1

v6.1.7

馃摐 Update Public Suffix List

馃敥 Dependencies

Authors: 2

... (truncated)

Changelog

Sourced from tldts's changelog.

v6.1.10 (Thu Feb 08 2024)

馃摐 Update Public Suffix List

馃敥 Dependencies

Authors: 2

v6.1.9 (Tue Feb 06 2024)

馃摐 Update Public Suffix List

Authors: 1

v6.1.8 (Sun Feb 04 2024)

馃摐 Update Public Suffix List

Authors: 1

v6.1.7 (Sat Feb 03 2024)

馃摐 Update Public Suffix List

  • tldts-experimental, tldts

... (truncated)

Commits
  • 5e784bf Bump version to: v6.1.10 [skip ci]
  • d88a61f Update CHANGELOG.md [skip ci]
  • 9aceb6b Update upstream public suffix list (#1952)
  • efe594d Bump @鈥媡ypescript-eslint/parser from 6.20.0 to 6.21.0 (#1948)
  • a49695e Bump @鈥媡ypescript-eslint/eslint-plugin from 6.20.0 to 6.21.0 (#1949)
  • a5d6229 Bump version to: v6.1.9 [skip ci]
  • d502fc1 Update CHANGELOG.md [skip ci]
  • 94eb5e4 Update upstream public suffix list (#1951)
  • 091e49b Bump version to: v6.1.8 [skip ci]
  • 08d438b Update CHANGELOG.md [skip ci]
  • Additional commits viewable in compare view

Updates web-ext from 7.10.0 to 7.11.0

Release notes

Sourced from web-ext's releases.

7.11.0

馃摚 We're finalizing web-ext v8 (the next major release), which will use a new AMO API to sign add-ons. Please try it out now by passing the --use-submission-api flag to the sign command in web-ext v7. More information at: https://extensionworkshop.com/documentation/develop/web-ext-command-reference/#use-submission-api

Features

  • web-ext lint: updated to use addons-linter to 6.21.0
  • web-ext run: remove READ_EXTERNAL_STORAGE permission requirement (backport #3018)

See all changes: mozilla/web-ext@7.10.0...7.11.0

Commits

Updates @fingerprintjs/fingerprintjs from 4.2.1 to 4.2.2

Release notes

Sourced from @鈥媐ingerprintjs/fingerprintjs's releases.

v4.2.2

  • fix: WebGL console warning in Chrome 121 and Safari 17.4 (#983)
Commits

Updates @types/chrome from 0.0.256 to 0.0.260

Commits

Updates esbuild from 0.19.11 to 0.20.0

Release notes

Sourced from esbuild's releases.

v0.20.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

  • Work around API deprecations in Deno 1.40.x (#3609, #3611)

    Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

    Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

  • Reorder implicit file extensions within node_modules (#3341, #3608)

    In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

    With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

    Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

v0.19.12

  • The "preserve" JSX mode now preserves JSX text verbatim (#3605)

    The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).

    Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:

    // Original code
let el =
  <a href={'/'} title='&apos;&quot;'> some text
    {foo}
      more text </a>
// Old output (with --loader=jsx --jsx=preserve)
let el = <a href="/" title={'&quot;}>
{" some text"}
{foo}
{"more text "}
</a>;
// New output (with --loader=jsx --jsx=preserve)
let el = <a href={"/"} title='&apos;&quot;'> some text
{foo}
more text </a>;

  • Allow JSX elements as JSX attribute values

    JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with {...}. It looks like this:

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.20.0

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.19.0 or ~0.19.0. See npm's documentation about semver for more information.

This time there is only one breaking change, and it only matters for people using Deno. Deno tests that use esbuild will now fail unless you make the change described below.

  • Work around API deprecations in Deno 1.40.x (#3609, #3611)

    Deno 1.40.0 was just released and introduced run-time warnings about certain APIs that esbuild uses. With this release, esbuild will work around these run-time warnings by using newer APIs if they are present and falling back to the original APIs otherwise. This should avoid the warnings without breaking compatibility with older versions of Deno.

    Unfortunately, doing this introduces a breaking change. The newer child process APIs lack a way to synchronously terminate esbuild's child process, so calling esbuild.stop() from within a Deno test is no longer sufficient to prevent Deno from failing a test that uses esbuild's API (Deno fails tests that create a child process without killing it before the test ends). To work around this, esbuild's stop() function has been changed to return a promise, and you now have to change esbuild.stop() to await esbuild.stop() in all of your Deno tests.

  • Reorder implicit file extensions within node_modules (#3341, #3608)

    In version 0.18.0, esbuild changed the behavior of implicit file extensions within node_modules directories (i.e. in published packages) to prefer .js over .ts even when the --resolve-extensions= order prefers .ts over .js (which it does by default). However, doing that also accidentally made esbuild prefer .css over .ts, which caused problems for people that published packages containing both TypeScript and CSS in files with the same name.

    With this release, esbuild will reorder TypeScript file extensions immediately after the last JavaScript file extensions in the implicit file extension order instead of putting them at the end of the order. Specifically the default implicit file extension order is .tsx,.ts,.jsx,.js,.css,.json which used to become .jsx,.js,.css,.json,.tsx,.ts in node_modules directories. With this release it will now become .jsx,.js,.tsx,.ts,.css,.json instead.

    Why even rewrite the implicit file extension order at all? One reason is because the .js file is more likely to behave correctly than the .ts file. The behavior of the .ts file may depend on tsconfig.json and the tsconfig.json file may not even be published, or may use extends to refer to a base tsconfig.json file that wasn't published. People can get into this situation when they forget to add all .ts files to their .npmignore file before publishing to npm. Picking .js over .ts helps make it more likely that resulting bundle will behave correctly.

0.19.12

  • The "preserve" JSX mode now preserves JSX text verbatim (#3605)

    The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).

    Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:

    // Original code
let el =
  <a href={'/'} title='&apos;&quot;'> some text
    {foo}
      more text </a>
// Old output (with --loader=jsx --jsx=preserve)
let el = <a href="/" title={'&quot;}>
{" some text"}
{foo}
{"more text "}
</a>;
// New output (with --loader=jsx --jsx=preserve)
let el = <a href={"/"} title='&apos;&quot;'> some text
{foo}
more text </a>;

  • Allow JSX elements as JSX attribute values

... (truncated)

Commits

Updates jsdom from 23.2.0 to 24.0.0

Release notes

Sourced from jsdom's releases.

Version 24.0.0

This release reverts our selector engine back to nwsapi. As discussed in #3659, the performance regressions from @asamuzakjp/dom-selector turned out to be higher than anticipated. In the future, we can revisit @asamuzakjp/dom-selector after it reaches nwsapi's performance on the two real-world benchmarks provided by the community.

Since reverting to nwsapi causes several functionality regressions, e.g. removing :has() support, we've decided to make this a major version.

Additionally:

  • Small fixes to edge-case behavior of the following properties: input.maxLength, input.minLength, input.size, progress.max, tableCell.colSpan, tableCell.rowSpan, tableCol.span, textArea.cols, textArea.maxLength, textArea.minLength, textArea.rows.
Changelog

Sourced from jsdom's changelog.

24.0.0

This release reverts our selector engine back to nwsapi. As discussed in #3659, the performance regressions from @asamuzakjp/dom-selector turned out to be higher than anticipated. In the future, we can revisit @asamuzakjp/dom-selector after it reaches nwsapi's performance on the two real-world benchmarks provided by the community.

Since reverting to nwsapi causes several functionality regressions, e.g. removing :has() support, we've decided to make this a major version.

Additionally:

  • Small fixes to edge-case behavior of the following properties: input.maxLength, input.minLength, input.size, progress.max, tableCell.colSpan, tableCell.rowSpan, tableCol.span, textArea.cols, textArea.maxLength, textArea.minLength, textArea.rows.
Commits

Updates sass from 1.69.7 to 1.70.0

Release notes

Sourced from sass's releases.

Dart Sass 1.70.0

To install Sass 1.70.0, download one of the packages below and add it to your PATH, or see the Sass website for full installation instructions.

Changes

JavaScript API

  • Add a sass.initCompiler() function that returns a sass.Compiler object which supports compile() and compileString() methods with the same API as the global Sass object. On the Node.js embedded host, each sass.Compiler object uses a single long-lived subprocess, making compiling multiple stylesheets much more efficient.

  • Add a sass.initAsyncCompiler() function that returns a sass.AsyncCompiler object which supports compileAsync() and compileStringAsync() methods with the same API as the global Sass object. On the Node.js embedded host, each sass.AsynCompiler object uses a single long-lived subprocess, making compiling multiple stylesheets much more efficient.

Embedded Sass

  • Support the CompileRequest.silent field. This allows compilations with no logging to avoid unnecessary request/response cycles.

  • The Dart Sass embedded compiler now reports its name as "dart-sass" rather than "Dart Sass", to match the JS API's info field.

See the full changelog for changes in earlier releases.

Changelog

Sourced from sass's changelog.

1.70.0

JavaScript API

  • Add a sass.initCompiler() function that returns a sass.Compiler object which supports compile() and compileString() methods with the same API as the global Sass object. On the Node.js embedded host, each sass.Compiler object uses a single long-lived subprocess, making compiling multiple stylesheets much more efficient.

  • Add a sass.initAsyncCompiler() function that returns a sass.AsyncCompiler object which supports compileAsync() and compileStringAsync() methods with the same API as the global Sass object. On the Node.js embedded host, each sass.AsynCompiler object uses a single long-lived subprocess, making compiling multiple stylesheets much more efficient.

Embedded Sass

  • Support the CompileRequest.silent field. This allows compilations with no logging to avoid unnecessary request/response cycles.

  • The Dart Sass embedded compiler now reports its name as "dart-sass" rather than "Dart Sass", to match the JS API's info field.

Commits

Updates mocha from 10.2.0 to 10.3.0

Release notes

Sourced from mocha's releases.

v10.3.0

This is a stable release equivalent to v10.3.0-preminor.0.

What's Changed

New Contributors

Full Changelog: mochajs/mocha@v10.2.0...v10.3.0

v10.3.0-preminor.0

A test release tagged with next on npm, to test that we can do releases at all. See #5081 for context.

What's Changed

... (truncated)

Changelog

Sourced from mocha's changelog.

10.3.0 / 2024-02-08

This is a stable release equivalent to 10.30.0-prerelease.

10.3.0-prerelease / 2024-01-18

This is a prerelease version to test our ability to release. Other than removing or updating dependencies, it contains no intended user-facing changes.

馃敥 Other

Commits
  • a886829 chore: fix link in pull request template (#5091)
  • 53a4baf chore: remove unnecessary canvas dependency (#5069)
  • 1ebff45 chore: inline nyan reporter's write function (#5056)
  • 8812413 fix: add alt text to Built with Netlify badge (#5068)
  • 645469e docs: touchups to labels and a template title post-revamp (#5050)
  • 9f99178 docs: overhaul contributing and maintenance docs for end-of-year 2023 (#5038)
  • eca4fec docs: fix return jsdoc type of titlePath (#4886)
  • 060f77d docs: use mocha.js instead of mocha in the example run (#4927)
  • 4b60c1a docs: fix fragment ID for yargs.js extends docs (#4918)
  • b41e985 chore: remove stale workflow (#5029)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by joshuakgoldberg, a new releaser for mocha since your current version.


Most Recent Ignore Conditions Applied to This Pull Request
Dependency Name Ignore Conditions
jsdom [>= 22.1.a, < 22.2]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> 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 <dependency name> 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 <dependency name> 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 <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Bump the external-dependencies group with 10 updates
904fd4c 
Bumps the external-dependencies group with 10 updates:

| Package | From | To |
| --- | --- | --- |
| [dexie](https://github.com/dfahlander/Dexie.js) | `3.2.4` | `3.2.5` |
| [i18next](https://github.com/i18next/i18next) | `23.7.16` | `23.8.2` |
| [tldts](https://github.com/remusao/tldts) | `6.1.2` | `6.1.10` |
| [web-ext](https://github.com/mozilla/web-ext) | `7.10.0` | `7.11.0` |
| [@fingerprintjs/fingerprintjs](https://github.com/fingerprintjs/fingerprintjs) | `4.2.1` | `4.2.2` |
| [@types/chrome](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/chrome) | `0.0.256` | `0.0.260` |
| [esbuild](https://github.com/evanw/esbuild) | `0.19.11` | `0.20.0` |
| [jsdom](https://github.com/jsdom/jsdom) | `23.2.0` | `24.0.0` |
| [sass](https://github.com/sass/dart-sass) | `1.69.7` | `1.70.0` |
| [mocha](https://github.com/mochajs/mocha) | `10.2.0` | `10.3.0` |


Updates `dexie` from 3.2.4 to 3.2.5
- [Release notes](https://github.com/dfahlander/Dexie.js/releases)
- [Commits](dexie/Dexie.js@v3.2.4...v3.2.5)

Updates `i18next` from 23.7.16 to 23.8.2
- [Release notes](https://github.com/i18next/i18next/releases)
- [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/i18next@v23.7.16...v23.8.2)

Updates `tldts` from 6.1.2 to 6.1.10
- [Release notes](https://github.com/remusao/tldts/releases)
- [Changelog](https://github.com/remusao/tldts/blob/master/CHANGELOG.md)
- [Commits](remusao/tldts@v6.1.2...v6.1.10)

Updates `web-ext` from 7.10.0 to 7.11.0
- [Release notes](https://github.com/mozilla/web-ext/releases)
- [Commits](mozilla/web-ext@7.10.0...7.11.0)

Updates `@fingerprintjs/fingerprintjs` from 4.2.1 to 4.2.2
- [Release notes](https://github.com/fingerprintjs/fingerprintjs/releases)
- [Commits](fingerprintjs/fingerprintjs@v4.2.1...v4.2.2)

Updates `@types/chrome` from 0.0.256 to 0.0.260
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/chrome)

Updates `esbuild` from 0.19.11 to 0.20.0
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md)
- [Commits](evanw/esbuild@v0.19.11...v0.20.0)

Updates `jsdom` from 23.2.0 to 24.0.0
- [Release notes](https://github.com/jsdom/jsdom/releases)
- [Changelog](https://github.com/jsdom/jsdom/blob/main/Changelog.md)
- [Commits](jsdom/jsdom@23.2.0...24.0.0)

Updates `sass` from 1.69.7 to 1.70.0
- [Release notes](https://github.com/sass/dart-sass/releases)
- [Changelog](https://github.com/sass/dart-sass/blob/main/CHANGELOG.md)
- [Commits](sass/dart-sass@1.69.7...1.70.0)

Updates `mocha` from 10.2.0 to 10.3.0
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md)
- [Commits](mochajs/mocha@v10.2.0...v10.3.0)

---
updated-dependencies:
- dependency-name: dexie
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: external-dependencies
- dependency-name: i18next
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: external-dependencies
- dependency-name: tldts
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: external-dependencies
- dependency-name: web-ext
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: external-dependencies
- dependency-name: "@fingerprintjs/fingerprintjs"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: external-dependencies
- dependency-name: "@types/chrome"
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: external-dependencies
- dependency-name: esbuild
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: external-dependencies
- dependency-name: jsdom
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: external-dependencies
- dependency-name: sass
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: external-dependencies
- dependency-name: mocha
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: external-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 9, 2024
@sammacbeth sammacbeth merged commit ea497d6 into main Feb 9, 2024
23 checks passed
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/main/external-dependencies-413e0df2d6 branch February 9, 2024 13:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@sammacbeth sammacbeth sammacbeth approved these changes

Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@sammacbeth