Skip to content

chore(deps): bump deslop-js to 0.0.14 - #605

Merged
rayhanadev merged 2 commits into
mainfrom
ray/c866308e
May 30, 2026
Merged

chore(deps): bump deslop-js to 0.0.14#605
rayhanadev merged 2 commits into
mainfrom
ray/c866308e

Conversation

@rayhanadev

@rayhanadev rayhanadev commented May 30, 2026

Copy link
Copy Markdown
Member

Why

The published react-doctor package pinned deslop-js to ^0.0.13, while the internal @react-doctor/core engine was already on ^0.0.14. Because caret ranges lock the patch level for 0.0.x versions, ^0.0.13 never auto-resolves to 0.0.14 — so the lockfile carried both copies and the published CLI shipped the older dead-code engine.

deslop-js is the engine behind react-doctor's unused-file / dead-code detection. This aligns the published CLI on the latest release (0.0.14) and removes the duplicate from the lockfile.

What changed

  • Bumped deslop-js ^0.0.13^0.0.14 in packages/react-doctor/package.json.
  • Regenerated pnpm-lock.yaml: both workspace importers now resolve to 0.0.14; the stale 0.0.13 resolution/snapshot is removed.
  • Added a patch changeset for react-doctor (it's in a fixed group, so eslint-plugin-react-doctor / oxlint-plugin-react-doctor version in lockstep).

@react-doctor/core already declared ^0.0.14, so its manifest is untouched.

Validation

Check Result
core dead-code tests (the code path that invokes deslop-js) 9 passed
react-doctor dead-code integration test (after pnpm build) 1 passed
pnpm typecheck 8/8 successful
pnpm format:check clean (1310 files)

RDE / OSS eval: not run — intentionally skipped. This is a dependency version alignment with no new/changed detection surface to evaluate.

Test plan

  • pnpm --filter @react-doctor/core exec vp test run dead-code
  • pnpm build && pnpm --filter react-doctor exec vp test run dead-code
  • pnpm typecheck
  • pnpm format:check

Residual risk

  • Low. No source changed; behavior delta is whatever ships in deslop-js@0.0.14. The dead-code suites exercise the analyze/defineConfig API end-to-end and pass on 0.0.14.

Made with Cursor


Note

Low Risk
Dependency-only alignment with no application source changes; any behavior change is limited to what ships in deslop-js@0.0.14, which existing dead-code tests already exercise.

Overview
Aligns the published react-doctor CLI with @react-doctor/core by bumping deslop-js from ^0.0.13 to ^0.0.14 in packages/react-doctor/package.json. Under 0.0.x caret rules, the older pin never picked up 0.0.14, so the lockfile had two versions and the shipped CLI could run an older dead-code engine than core.

pnpm-lock.yaml now resolves a single deslop-js@0.0.14 (the 0.0.13 resolution is removed). A patch changeset records the react-doctor release note for the engine update used for unused-file / dead-code detection.

Reviewed by Cursor Bugbot for commit c2ddff9. Bugbot is set up for automated code reviews on this repo. Configure here.

rayhanadev and others added 2 commits May 30, 2026 16:09
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Copilot AI review requested due to automatic review settings May 30, 2026 23:12
@github-actions

Copy link
Copy Markdown
Contributor

React Doctor

React Doctor found 3 files changed in this pull request, but none matched the files covered by its enabled checks.

Scope: 3 files changed on ray/c866308e vs. main.

View workflow run

Generated by React Doctor. Questions? Contact founders@million.dev.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@rayhanadev
rayhanadev merged commit 4861f37 into main May 30, 2026
15 of 16 checks passed
@rayhanadev
rayhanadev deleted the ray/c866308e branch May 30, 2026 23:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants