search

Dhruv-Techapps / auto-clicker-auto-fill

Auto click, fill, submit with AutoClicker
https://getautoclicker.com/
MIT License
0 stars 0 forks source link

Bump the other-dependencies group with 11 updates #479

Closed dependabot[bot] closed 1 week ago

dependabot[bot] commented 1 week ago

Bumps the other-dependencies group with 11 updates:

Package From To
algoliasearch 5.12.0 5.13.0
i18next 23.16.4 23.16.5
puppeteer-core 23.7.0 23.7.1
react-i18next 15.1.0 15.1.1
react-router-dom 6.27.0 6.28.0
@swc/core 1.8.0 1.9.2
@swc/helpers 0.5.13 0.5.15
@typescript-eslint/eslint-plugin 8.13.0 8.14.0
@typescript-eslint/parser 8.13.0 8.14.0
esbuild 0.19.12 0.24.0
nx 20.0.8 20.1.0

Updates algoliasearch from 5.12.0 to 5.13.0

Release notes

Sourced from algoliasearch's releases.

5.13.0

New version released!

What's Changed

Full Changelog: https://github.com/algolia/algoliasearch-client-javascript/compare/5.12.0...5.13.0

→ Browse the Algolia documentation

Changelog

Sourced from algoliasearch's changelog.

5.13.0

Commits
  • b50469b chore: release 5.13.0
  • 61a0077 feat(specs): add composition API (generated)
  • 76b5b03 feat(scripts): compute eligibility dates (generated)
  • b0ca845 fix(clients): update browse iterator (generated)
  • 2fe37ea fix(specs): add secrets payload for updates (generated)
  • 38ecf7a fix(javascript): allow import from dist (generated)
  • See full diff in compare view


Updates i18next from 23.16.4 to 23.16.5

Release notes

Sourced from i18next's releases.

v23.16.5

  • fix extractFromKey for use cases like this
Changelog

Sourced from i18next's changelog.

23.16.5

  • fix extractFromKey for use cases like this
Commits


Updates puppeteer-core from 23.7.0 to 23.7.1

Release notes

Sourced from puppeteer-core's releases.

puppeteer-core: v23.7.1

23.7.1 (2024-11-07)

Bug Fixes

Commits


Updates react-i18next from 15.1.0 to 15.1.1

Changelog

Sourced from react-i18next's changelog.

15.1.1

  • fix: Not all namespaces are loaded when passing the lng option to useTranslate 1809
Commits
  • 20b820e 15.1.1
  • 0d8153e fix: Not all namespaces are loaded when passing the lng option to useTranslat...
  • See full diff in compare view


Updates react-router-dom from 6.27.0 to 6.28.0

Release notes

Sourced from react-router-dom's releases.

react-router-dom-v5-compat@6.4.0-pre.15

Patch Changes

  • Updated dependencies
    • react-router@6.4.0-pre.15
    • react-router-dom@6.4.0-pre.15

react-router-dom-v5-compat@6.4.0-pre.11

Patch Changes

  • Updated dependencies
    • react-router@6.4.0-pre.11
    • react-router-dom@6.4.0-pre.11

react-router-dom-v5-compat@6.4.0-pre.10

Patch Changes

  • Updated dependencies
    • react-router@6.4.0-pre.10
    • react-router-dom@6.4.0-pre.10

react-router-dom-v5-compat@6.4.0-pre.9

Patch Changes

  • Updated dependencies
    • react-router@6.4.0-pre.9
    • react-router-dom@6.4.0-pre.9

react-router-dom-v5-compat@6.4.0-pre.8

Patch Changes

  • Updated dependencies
    • react-router@6.4.0-pre.8
    • react-router-dom@6.4.0-pre.8

react-router-dom-v5-compat@6.4.0-pre.7

Patch Changes

  • Updated dependencies
    • react-router@6.4.0-pre.7
    • react-router-dom@6.4.0-pre.7

react-router-dom-v5-compat@6.4.0-pre.6

Patch Changes

  • 44bce3c6: Fix react-router-dom peer dependency version
    • react-router@6.4.0-pre.6
    • react-router-dom@6.4.0-pre.6

react-router-dom-v5-compat@6.4.0-pre.5

... (truncated)

Changelog

Sourced from react-router-dom's changelog.

6.28.0

Minor Changes

    • Log deprecation warnings for v7 flags (#11750)
    • Add deprecation warnings to json/defer in favor of returning raw objects
      • These methods will be removed in React Router v7

Patch Changes

  • Update JSDoc URLs for new website structure (add /v6/ segment) (#12141)
  • Updated dependencies:
    • react-router@6.28.0
    • @remix-run/router@1.21.0
Commits


Updates @swc/core from 1.8.0 to 1.9.2

Changelog

Sourced from @​swc/core's changelog.

[1.9.2] - 2024-11-11

Bug Fixes

Features

  • (es/codegen) Implement proper inline_script support (#9729) (e732a36)

[1.9.1] - 2024-11-06

Bug Fixes

[1.9.0] - 2024-11-06

Bug Fixes

Features

  • (typescript) Port deno isolatedDeclarations updates (#9712) (6194044)

Miscellaneous Tasks

  • (deps) Update rust crate is-macro to v0.3.7 (#9713) (d48e6e8)
Commits
  • 669d275 chore: Publish 1.9.2 with swc_core v5.0.3
  • 47c6d38 chore: Update changelog
  • f2be61f chore: Publish 1.9.2-nightly-20241111.1 with swc_core v5.0.3
  • 9aae07a chore: Publish crates with swc_core v5.0.3
  • e732a36 feat(es/codegen): Implement proper inline_script support (#9729)
  • 9dfa3f5 chore: Publish @swc/helpers@0.5.15
  • 1606d08 chore: Publish crates with swc_core v5.0.2
  • aff9de5 fix(es): Fix typo in feature name (#9721)
  • 7c396a1 chore: Update changelog
  • 3d87fe0 chore: Publish 1.9.1 with swc_core v5.0.1
  • Additional commits viewable in compare view


Updates @swc/helpers from 0.5.13 to 0.5.15

Commits


Updates @typescript-eslint/eslint-plugin from 8.13.0 to 8.14.0

Release notes

Sourced from @​typescript-eslint/eslint-plugin's releases.

v8.14.0

8.14.0 (2024-11-11)

🚀 Features

  • eslint-plugin: [no-confusing-void-expression] add an option to ignore voidvoid (#10067)
  • eslint-plugin: [await-thenable] report unnecessary await using statements (#10209)

🩹 Fixes

  • deps: update dependency eslint to v9.14.0 (#10309)
  • deps: update docusaurus monorepo to v3.6.0 (#10319)
  • eslint-plugin: [no-unnecessary-condition] improve error message for literal comparisons (#10194)
  • eslint-plugin: [no-misused-promises] improve report loc for methods (#10216)
  • scope-manager: fix asserted increments not being marked as write references (#10271)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from @​typescript-eslint/eslint-plugin's changelog.

8.14.0 (2024-11-11)

🚀 Features

  • eslint-plugin: [await-thenable] report unnecessary await using statements (#10209)
  • eslint-plugin: [no-confusing-void-expression] add an option to ignore voidvoid (#10067)

🩹 Fixes

  • scope-manager: fix asserted increments not being marked as write references (#10271)
  • eslint-plugin: [no-misused-promises] improve report loc for methods (#10216)
  • eslint-plugin: [no-unnecessary-condition] improve error message for literal comparisons (#10194)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

Commits
  • 16fba0a chore(release): publish 8.14.0
  • 42d275c fix(scope-manager): fix asserted increments not being marked as write referen...
  • d27a9ac fix(eslint-plugin): [no-misused-promises] improve report loc for methods (#10...
  • c13b6b4 chore: fix lint and build website errors (#10288)
  • 5b2ebcd feat(eslint-plugin): [await-thenable] report unnecessary await using statem...
  • 22f7f25 fix(eslint-plugin): [no-unnecessary-condition] improve error message for lite...
  • e2e9ffc feat(eslint-plugin): [no-confusing-void-expression] add an option to ignore v...
  • See full diff in compare view


Updates @typescript-eslint/parser from 8.13.0 to 8.14.0

Release notes

Sourced from @​typescript-eslint/parser's releases.

v8.14.0

8.14.0 (2024-11-11)

🚀 Features

  • eslint-plugin: [no-confusing-void-expression] add an option to ignore voidvoid (#10067)
  • eslint-plugin: [await-thenable] report unnecessary await using statements (#10209)

🩹 Fixes

  • deps: update dependency eslint to v9.14.0 (#10309)
  • deps: update docusaurus monorepo to v3.6.0 (#10319)
  • eslint-plugin: [no-unnecessary-condition] improve error message for literal comparisons (#10194)
  • eslint-plugin: [no-misused-promises] improve report loc for methods (#10216)
  • scope-manager: fix asserted increments not being marked as write references (#10271)

❤️ Thank You

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from @​typescript-eslint/parser's changelog.

8.14.0 (2024-11-11)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

Commits


Updates esbuild from 0.19.12 to 0.24.0

Release notes

Sourced from esbuild's releases.

v0.24.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.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version

  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

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";

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.24.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.23.0 or ~0.23.0. See npm's documentation about semver for more information.

  • Drop support for older platforms (#3902)

    This release drops support for the following operating system:

    • macOS 10.15 Catalina

    This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later.

    Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this:

    git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version

  • Fix class field decorators in TypeScript if useDefineForClassFields is false (#3913)

    Setting the useDefineForClassFields flag to false in tsconfig.json means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release.

  • Avoid incorrect cycle warning with tsconfig.json multiple inheritance (#3898)

    TypeScript 5.0 introduced multiple inheritance for tsconfig.json files where extends can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, tsconfig.json files containing this edge case should work correctly without generating a warning.

  • Handle Yarn Plug'n'Play stack overflow with tsconfig.json (#3915)

    Previously a tsconfig.json file that extends another file in a package with an exports map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release.

  • Work around more issues with Deno 1.31+ (#3917)

    This version of Deno broke the stdin and stdout properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when import.meta.main is true). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release.

    This fix was contributed by @​Joshix-1.

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

... (truncated)

Commits


Updates nx from 20.0.8 to 20.1.0

Release notes

Sourced from nx's releases.

20.1.0 (2024-11-11)

🚀 Features

  • angular: add vitest option to angular (#27311)
  • bundling: add createNodesV2 for rollup plugin (#28090)
  • core: allow disabling of tsconfig path sorting in format:write and formatFiles() (#28517)
  • core: Update plugin generators so that they are formatted by default (#28593)
  • core: upgrade semver to 7.6.3 (#28716)
  • expo: build w/package.json overrides/resolutions (#28254)
  • expo: use createNodesV2 (#28005)
  • js: support esbuild and swc bundlers with the new ts solution config setup (#28409)
  • js: update the setup-build generator to support the new ts setup (#28446)
  • linter: add support eslint 9 --quiet param (#28743)
  • misc: remove handling of @​nrwl scope (#28589)
  • module-federation: use latest module-federation/enhanced (#28296)
  • module-federation: use module-federation runtime for dynamic federation (#28704)
  • nextjs: update createNodes to createNodesV2 and add deprecation message (#28527)
  • nextjs: add support for typescript Next.js config file (#28709)
  • nx-cloud: configure import paths for light client when running … (#28735)
  • nx-dev: add live stream notifier (#28260)
  • nx-dev: update home hero & livestream notifier (#28403)
  • nx-dev: add contact link on powerpack page (#28458)
  • nx-dev: add videos to CI docs (84aba19bec)
  • nx-dev: linkable resources page (46769b3c18)
  • nx-dev: add customer case studies (75a73ed0e7)
  • nx-dev: add video course page (#28736)
  • react: update eslint plugins to be compat with eslint v9 (#28559)
  • remix: generate remix vite application (#28555)
  • remix: ensure migrations point to latest remix verison (#28876)
  • rspack: add convert-webpack generator (#28167)
  • rspack: make target property optional (#28785)
  • rspack: move logic for withWeb to applyWebConfig and bring in line with webpack (#28803)
  • testing: add support for the ts solution config setup to the playwright plugin (#28636)
  • testing: split atomized outputs for Playwright and Cypress CI targets (#28682)
  • testing: add disableJestRuntime option to @​nx/jest/plugin to speed up target inference (#28522)
  • testing: add support for the ts solution config setup to the cypress plugin (#28637)

🩹 Fixes

  • add required minimizer setting to the generated Nest rspack conf… (#28629)
  • angular: ensure provideStore is provided before storeDevTools #28107 (#28428, #28107)
  • angular: add missing package version bump for zone.js (#28430)
  • angular: use vitest generator instead of vite config generator (#28696)
  • core: support NX_NO_CLOUD (#28366)
  • core: add busy handler for sqlite (#28390)
  • core: handle neverConnectToCloud property (#28452)
  • core: add migration to set useLegacyCache by default (#28454)
  • core: repair SIGINT signals on windows (#28496)
  • core: neverConnectToCloud should disable connecting to nxCloud (#28501)

... (truncated)

Commits
  • c21b039 fix(core): reduce time it takes to require nx commands (#28884)
  • 0fd3442 fix(core): cross-workspace implicitDependencies should be safely ignored (#28...
  • 258a256 fix(core): do not use unix dotfile locks (#28859)
  • d2c1067 fix(release): support workspace root as a subdirectory of git root (#28650)
  • 0d7f226 fix(core): shutdown plugin workers when disconnected (#28857)
  • 7f39dc1 fix(core): do not depend on ci info crate (#28850)
  • 158d343 fix(misc): update generators to use autocomplete instead of select when possi...
  • c50269a fix(core): create different dummy tasks for different targets (#28837)
  • bc1a6cf fix(core): ensure that the database connection is closed when nx exits (#28821)
  • a22a431 feat(nx-cloud): configure import paths for light client when running … (#28735)
  • Additional commits viewable in compare view


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 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
nx-cloud[bot] commented 1 week ago

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 4ea66b392ea933602433e5a9bfd4c6067438fd5b. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

✅ Successfully ran 2 targets - [`nx affected --target=test --parallel=3 --exclude=tag:puppeteer --ci --code-coverage`](https://cloud.nx.app/runs/dorgTFyJbd?utm_source=pull-request&utm_medium=comment) - [`nx affected --target=lint --parallel=3`](https://cloud.nx.app/runs/CqeUxL7qxc?utm_source=pull-request&utm_medium=comment)

Sent with 💌 from NxCloud.

codecov[bot] commented 1 week ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (main@a5d6689). Learn more about missing BASE report.

Additional details and impacted files [![Impacted file tree graph](https://app.codecov.io/gh/Dhruv-Techapps/auto-clicker-auto-fill/pull/479/graphs/tree.svg?width=650&height=150&src=pr&token=7DOJUS5L8I&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Dhruv-Techapps)](https://app.codecov.io/gh/Dhruv-Techapps/auto-clicker-auto-fill/pull/479?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Dhruv-Techapps) ```diff @@ Coverage Diff @@ ## main #479 +/- ## ======================================= Coverage ? 69.37% ======================================= Files ? 19 Lines ? 173 Branches ? 30 ======================================= Hits ? 120 Misses ? 50 Partials ? 3 ```
sonarcloud[bot] commented 1 week ago

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud