Page MenuHomePhabricator

[yarn] Bump `flow-typed` to transitively bump `shelljs`
ClosedPublic

Authored by atul on May 16 2022, 5:23 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Dec 19, 10:47 AM
Unknown Object (File)
Sun, Dec 8, 4:08 AM
Unknown Object (File)
Nov 14 2024, 10:21 AM
Unknown Object (File)
Nov 9 2024, 11:40 AM
Unknown Object (File)
Nov 9 2024, 11:40 AM
Unknown Object (File)
Nov 9 2024, 11:40 AM
Unknown Object (File)
Nov 9 2024, 11:40 AM
Unknown Object (File)
Nov 9 2024, 11:40 AM

Details

Summary

There was a @dependabot PR that bumped shelljs from 0.84 -> 0.85: https://github.com/CommE2E/comm/pull/158 that failed for some reason.

Unfortunately the CI logs have long expired, but according to comment left by @ashoat the errors had something to do with flow.

I tried bumping shelljs this time by removing and re-adding the flow-typed dependency from each package.json and it seems to work fine?

Test Plan

CI

Diff Detail

Repository
rCOMM Comm
Branch
master
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

yarn.lock
15642

Here's the critical change.

atul requested review of this revision.May 16 2022, 5:44 AM
This revision is now accepted and ready to land.May 16 2022, 1:06 PM

Ugh, there were no eslint/prettier issues on buildkite CI/Ubuntu machine I SSH'd into.

Will see if there's a more "surgical" way to bump ShellJS without having all the transitive dependencies of flow-typed bumped as well.

I think if I explicitly add shelljs to the root package.json as 0.85, then run yarn-deduplicate, then remove shelljs from the root package.json things should work...

This revision is now accepted and ready to land.May 16 2022, 1:45 PM

I'm confused, what exactly went wrong?

I'm confused, what exactly went wrong?

Quite a few eslint/prettier issues when

yarn eslint --max-warnings=0

was run on Github CI machine: https://github.com/CommE2E/comm/runs/6459657382?check_suite_focus=true

Issues that did not surface on Buildkite CI or Ubuntu machine I SSH'd into:

a041.png (130×1 px, 27 KB)

"more surgical" approach to hopefully avoid the strange eslint/prettier issues

edit: does not fail yarn eslint --max-warnings=0 where it did previously (local machine)

atul requested review of this revision.May 16 2022, 1:54 PM
This revision is now accepted and ready to land.May 16 2022, 1:56 PM

Phew, that got past ESLint & Flow & Jest this time