STUD-10494 Bump fsevents lockfile dependency#12
Merged
Conversation
Update the fork's locked fsevents dependency to the latest 1.x patch and refresh the npm lockfile metadata so installs are reproducible outside Dependabot. Co-authored-by: Cursor <cursoragent@cursor.com>
danerubado-wk
approved these changes
Jun 24, 2026
Author
|
QA +1 |
Author
|
@Workiva/release-management-p |
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.
Summary
fseventsdevelopment dependency from1.2.4to1.2.13.package-lock.jsonwith a current npm install so the lockfile is up to date outside Dependabot.fsevents1.x line because the current build toolchain resolves it throughchokidar@1.7.0, which declaresfsevents:^1.0.0.Why not fsevents 2.x here?
fsevents@2.3.3is the npmlatestrelease, but it is not a drop-in lockfile bump for this fork. The dependency path is:webpack@1.15.0->watchpack@0.2.9->chokidar@1.7.0->fsevents:^1.0.0Moving cleanly to
fsevents@2.xwould require modernizing the fork's legacy build/watch stack, especiallywebpack@1/watchpack@0/chokidar@1. That is larger than this patch and carries more build risk.Validation
npm cinpm install --package-lock-only --ignore-scriptsnpm cinpm run buildFollow-up
After this PR merges, update
oc-builder'spnpm-lock.yamlsogithub:Workiva/react-dnd-mouse-backendresolves to the merged fork commit.Made with Cursor