chore: dedupe and update packages #4332
Conversation
|
The PR diff size of 15248 lines exceeds the maximum allowed for the inline comments feature. |
| @@ -15,7 +15,7 @@ | |||
| "@microsoft/fast-colors": "^5.0.12", | |||
| "@microsoft/fast-element": "latest", | |||
| "@microsoft/fast-foundation": "latest", | |||
| "lodash-es": "^4.17.15", | |||
| "lodash-es": "4.17.15", | |||
radium-v
Feb 4, 2021
Author
Contributor
It's due to this bug (lodash/lodash#5033) in 4.17.20. Pretty much everything breaks with that latest version.
An alternative to pinning could be setting a top-level resolution entry, but I don't know how that will affect nested dependencies.
| @@ -9,7 +9,7 @@ | |||
| "watch": "webpack --progress --watch --mode=production", | |||
| "prettier": "prettier --config ../../../.prettierrc --write \"**/*.{ts,tsx}\"", | |||
| "prettier:diff": "prettier --config ../../../.prettierrc \"**/*.{ts,tsx}\" --list-different", | |||
| "test": "yarn eslint && yarn build", | |||
| "test": "yarn eslint", | |||
nicholasrice
Feb 4, 2021
•
Member
What's the rational for not building as part of the test pass? (question goes for all packages you've done this)
radium-v
Feb 4, 2021
Author
Contributor
Building after testing is redundant in more situations than not. I'll move these specific changes to a different PR with more details.
|
The PR diff size of 15226 lines exceeds the maximum allowed for the inline comments feature. |
|
The PR diff size of 15216 lines exceeds the maximum allowed for the inline comments feature. |
|
I'm super excited for this! |
|
The PR diff size of 15216 lines exceeds the maximum allowed for the inline comments feature. |
|
Code Climate has analyzed commit db9b217 and detected 0 issues on this pull request. View more on Code Climate. |
Description
lodash-es,@babel/*, andtypescriptdocusaurusandstorybookaddonsapi-extractor@7.8.1,lodash-es@4.7.15buildwhen runningtestTo test it locally, make sure to do a full clean with
yarn lerna cleanandgit cleanbefore runningyarn install.Motivation & context
Cuts dependencies down from >1GB to ~634MB.
Issue type checklist
Is this a breaking change?
Adding or modifying component(s) in
@microsoft/fast-componentschecklistProcess & policy checklist