chore(deps): bump deslop-js to 0.0.14 - #605
Merged
Merged
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
|
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 Generated by React Doctor. Questions? Contact founders@million.dev. |
This was referenced May 30, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The published
react-doctorpackage pinneddeslop-jsto^0.0.13, while the internal@react-doctor/coreengine was already on^0.0.14. Because caret ranges lock the patch level for0.0.xversions,^0.0.13never auto-resolves to0.0.14— so the lockfile carried both copies and the published CLI shipped the older dead-code engine.deslop-jsis 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
deslop-js^0.0.13→^0.0.14inpackages/react-doctor/package.json.pnpm-lock.yaml: both workspace importers now resolve to0.0.14; the stale0.0.13resolution/snapshot is removed.patchchangeset forreact-doctor(it's in afixedgroup, soeslint-plugin-react-doctor/oxlint-plugin-react-doctorversion in lockstep).@react-doctor/corealready declared^0.0.14, so its manifest is untouched.Validation
coredead-code tests (the code path that invokesdeslop-js)react-doctordead-code integration test (afterpnpm build)pnpm typecheckpnpm format:checkRDE / 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-codepnpm build && pnpm --filter react-doctor exec vp test run dead-codepnpm typecheckpnpm format:checkResidual risk
deslop-js@0.0.14. The dead-code suites exercise theanalyze/defineConfigAPI end-to-end and pass on0.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-doctorCLI with@react-doctor/coreby bumpingdeslop-jsfrom^0.0.13to^0.0.14inpackages/react-doctor/package.json. Under0.0.xcaret rules, the older pin never picked up0.0.14, so the lockfile had two versions and the shipped CLI could run an older dead-code engine than core.pnpm-lock.yamlnow resolves a singledeslop-js@0.0.14(the0.0.13resolution is removed). A patch changeset records thereact-doctorrelease 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.