-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
build: Extract typescript pkg into main package.json #4242
Conversation
size-limit report
|
0b0e109
to
eb2feba
Compare
"devDependencies": { | ||
"typescript": "3.7.5" | ||
}, | ||
"devDependencies": {}, |
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.
"devDependencies": {}, |
?
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.
Yeah this is because I just find and replaced the value. I can update.
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.
Actually I'm going to leave it like this. This makes makes the diff when adding new packages much cleaner (which in turn makes git blame easier to understand in the future)
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.
Isn't this change going to make it harder to work on single packages in isolation? (In particular because certain requirements become implicit/defined elsewhere).
One of the supposed advantages of having multiple packages is not being forced to upgrade everything in lock step. If we do this change, I imagine will be in a situation of all or nothing when trying to upgrade common dependencies including typescript version.
We use a common tsconfig for all of our packages, so having inconsistent typescript versions will lead to problems. In addition, certain packages having different versions than others can cause problems. Having a single source of truth (the main package.json) is easier maintence wise. typescript (because of the variety of issues it introduces), should for sure be an all or nothing change - a common dependency. Having these spread out just create potential for problems or inconsistencies.
No, because yarn workspaces should take care of everything being resolved correctly. |
eb2feba
to
7e1cf0f
Compare
As prep for unifying our package.json, let's move dependencies that every package uses into the root
package.json
.This patch does that for the
typescript
package.