Skip to content
Source
Sign inSign up
TanStack/router

Bump eslint-utils from 1.3.1 to 1.4.3 #6

Closeddependabot[bot](GitHub profile, opens in a new tab)wants to merge 1 commit intonext fromrefs/pull/6/headopened

Bumps eslint-utils from 1.3.1 to 1.4.3.

Release notes

Sourced from eslint-utils's releases.

v1.4.3

🐛 Bug fixes

  • 8f9e481ecc1204c7a1331b697f97903f90c75154 fixed false positive of ReferenceTracker.

v1.4.2

🐛 Bug fixes

  • e4cb01498df6096b66edb0c78965ee6f47d3ac77 fixed a regression of the previous release.

v1.4.1

🐛 Bug fixes

  • c119e832952c8c653bd4f21e39eb9f7ce48e5947 fixed getStaticValue() function to handle null literal correctly even if runtimes don't support BigInt natively.
  • 587cca2f82c245f5fc4a8b9fb2cf6b35c0d02552 fixed getStringIfConstant() function to handle regular expression literals and BigInt literals even if runtimes don't support those.
  • 08158db1c98fd71cf0f32ddefbc147e2620e724c fixed GHSA-3gx7-xhv7-5mx3.

v1.4.0

✨ Enhancements

  • 66456c5356310fc4309b4fe2756995f27b907747 (and ebf5a8378d3f0a20a74adb158a7112cb616bce44, aac472e815551688d23cc8fd88f9044dbf276804) added isParenthesized() function that checks if a given node is parenthesized or not.
  • 4f8407dd6cd52274ba115b3a8558153ec6d799a7 (and cb518c70ee037722f802d808bbbe93da83f07fb3) added hasSideEffect() function that checks if a given node may have side-effects or not.
Commits

Dependabot compatibility score

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 ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

    1. dependabot[bot](GitHub profile, opens in a new tab) added labelsdependencies

    2. View your CI Pipeline Execution ↗ for commit 080dc81333f606fe948881558f0064f6a222aa91

      CommandStatusDurationResult
      nx affected --targets=test:eslint,test:unit,tes...❌ Failed17m 29sView ↗
      nx run-many --target=build --exclude=examples/*...✅ Succeeded1m 57sView ↗

      ☁️ Nx Cloud last updated this comment at 2026-06-01 22:27:40 UTC

    3. Important

      At least one additional CI pipeline execution has run since the conclusion below was written and it may no longer be applicable.

      Nx Cloud has identified a possible root cause for your failed CI:

      We investigated all 16 failing tasks and found no causal link to the eslint-utils bump. The type-check failures stem from a rollup version conflict (4.52.5 vs 4.61.0) in node_modules, the E2E failures show a consistent FormData regression across React, Solid, and Vue unrelated to an ESLint utility, and one test hit a port conflict — all pointing to pre-existing environment issues surfaced by the lockfile regeneration rather than the dependency change itself.

      No code changes were suggested for this issue.

      Trigger a rerun:

      Rerun CI

      Nx Cloud View detailed reasoning on Nx Cloud ↗


      🎓 Learn more about Self-Healing CI on [nx.dev](https://nx.dev/docs/features/ci-features/self-healing-ci?utm_source=pull-request&utm_medium=comment)

Sign in to join this conversation.