Skip to content
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

[core] Fix missing type peer deps #17211

Merged
merged 1 commit into from
Jan 5, 2020
Merged

Conversation

eps1lon
Copy link
Member

@eps1lon eps1lon commented Aug 28, 2019

Only merge if either node 8 has reached end of life (end of 2019) or npm was bumped in node 8 to 6.11

Closes #17121

peerDependenciesMeta is implemented in yarn@1.13, npm@6.11 and pnpm@?.

Rule of thumb: If a type package has side effects it is a peer that has to be installed at app level. Otherwise you get type mismatches if different versions are installed. A side-effect is module augmentation which is most often used to make a type globally available (in react this happens by adding the JSX namespace). Packages without side-effects are usually safe to list as direct dependencies since multiple versions don't necessarily create clashes (here @types/react-transition-group).

@eps1lon eps1lon added bug 🐛 Something doesn't work on hold There is a blocker, we need to wait typescript labels Aug 28, 2019
@mui-pr-bot
Copy link

mui-pr-bot commented Aug 28, 2019

No bundle size changes comparing 3578ce2...c5a82a3

Generated by 🚫 dangerJS against c5a82a3

@eps1lon
Copy link
Member Author

eps1lon commented Jan 5, 2020

Node 8 has reached its end of life.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Something doesn't work typescript
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Missing "@types/react" dependency
3 participants