-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: [M3-8524] - Attempt to get dependencies in a more healthy state #11005
chore: [M3-8524] - Attempt to get dependencies in a more healthy state #11005
Conversation
@@ -112,7 +112,7 @@ export const UnifiedMigrationPanel = (props: Props) => { | |||
} | |||
status="help" | |||
tooltipPosition="right" | |||
width={[theme.breakpoints.up('sm')] ? 450 : 300} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We had a handful of things like this. We would get a type error saying [theme.breakpoints.up('sm')]
is always truthy so I just updated the code to just use 450
Coverage Report: ✅ |
@@ -208,7 +208,7 @@ | |||
"simple-git": "^3.19.0", | |||
"storybook": "^8.3.0", | |||
"storybook-dark-mode": "^4.0.1", | |||
"ts-node": "^10.9.2", | |||
"tsx": "^4.19.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ts-node
was causing our cypress helper scripts issues. I found tsx
. It fixes the issue and appears to be a better / more lightweight alternative to ts-node
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know we've also talked about using Bun for these scripts too -- iirc it's only a couple of the scripts in the scripts
dir that we use for the Jenkins pipeline that even rely on ts-node
, but lately I've been opting to keep that type of stuff in internal repos. I'd be up to move these out of Cloud altogether if it means we can drop the ts-node
/tsx
dependency
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the idea of moving scripts like this in internal repos. In the mean time (and because we don't have Bun readily available in CI) I'm totally cool with keeping tsx
around. It seems very minimal and useful for us even for things like scripts/package-versions/index.js
(if we were to make it .ts)
Eventually, I'd love Bun to be our go-to tool for running this stuff, but we should probably get that setup in CI and formalized before we commit to that
@@ -336,7 +336,6 @@ export const lightTheme: ThemeOptions = { | |||
svg: { | |||
color: Color.Neutrals[40], | |||
}, | |||
top: 'unset', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"serve": "^14.0.1", | ||
"simple-git": "^3.19.0", | ||
"storybook": "^8.3.0", | ||
"storybook-dark-mode": "^4.0.1", | ||
"ts-node": "^10.9.2", | ||
"storybook-dark-mode": "4.0.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I pinned this to 4.0.1
because of hipstersmoothie/storybook-dark-mode#282
This will fix the issue @dwiley-akamai caught with Storybook. We'll just need to keep an eye out for storybook-dark-mode
to provide a fix before we upgrade storybook-dark-mode next
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Storybook looks good now as well 🚀
Cloud Manager E2E Run #6585
Run Properties:
|
Project |
Cloud Manager E2E
|
Branch Review |
develop
|
Run status |
Passed #6585
|
Run duration | 24m 35s |
Commit |
f006ce89d4: chore: [M3-8524] - Attempt to get dependencies in a more healthy state (#11005)
|
Committer | Banks Nussman |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
0
|
Flaky |
3
|
Pending |
2
|
Skipped |
0
|
Passing |
408
|
View all changes introduced in this branch ↗︎ |
Description 📝
rm yarn.lock && yarn
to re-generate our lockfile 📄~version
“Approximately equivalent to version” and^version
“Compatible with version” updating 📦braces
@babel/traverse
minimist
yargs-parser
kind-of
ua-parser-js
immer
glob-parent
hosted-git-info
(upgradingconcurrently
allowed this one)word-wrap
tough-cookie
jackspeak
(we added this in refactor: [M3-7585] - Upgrade to React 18 #10169 as a hacky fix. Now it is no longer needed 🎉 )react-test-renderer
reselect-tools
eslint-plugin-ramda
(removed from api-v4 and validation'spackage.json
because they don't use ramda)@types/jsdom
(We do depend onjsdom
but we don't need the types for it because our TypeScript code never imports it)eslint-plugin-node
(this plugin is not referenced in our eslint config)eslint-plugin-storybook
(this plugin is not referenced in our eslint config)Side Effects
yarn.lock
was re-generated, causing our our TypeScript version to upgrade to the latest minor version. The latest version of TypeScript got smarter and caught a few things!ts-node
(used by our cypress pipeline) stopped working so I just replacedts-node
with a better alternative calledtsx
How to test 🧪
Prerequisites
yarn
for good measureThings to check
yarn why [package name here]
and verify the version reported by yarn is not vulnerable (verify the version is equal to or newer than what the resolution was) 📦yarn why [package name here]
and verify our repo uses version that is patched and not vulnerable (the depenedabot page will tell you what versions are acceptable)As an Author I have considered 🤔