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

Add missing dependencies or peerDependencies #9916

Merged
merged 3 commits into from
Feb 20, 2020
Merged

Add missing dependencies or peerDependencies #9916

merged 3 commits into from
Feb 20, 2020

Conversation

gaetanmaisse
Copy link
Member

What I did

As Yarn 2 is must stricter than Yarn 1 or NPM about missing dependencies or peerDependencies I used npx @yarnpkg/doctor (details here) to fix some of them.

There are still a lot more, I will fix them step by step.

--

Specific case of regenerator-runtime: as discussed with @ndelangen regenerator-runtime is used as polyfill to backport async/await and generator to old browser (like core-js). Any package that uses async/await or generator will require regenerator-runtime at runtime without any import in the source (it's added by babel during transpilation). To avoid any issue in the future regenerator-runtime is added to almost all packages, as it has been done for core-js

How to test

  • All check should be green

`regenerator-runtime` is used as polyfill to backport async/await and generator to old browser (like core-js).
Any package that use async/await or generator will require `regenerator-runtime` at runtime without any import in the source (it's added by babel during transpilation).
To avoid any issue in the future `regenerator-runtime` is added to almost all packages, as it has been done for `core-js`

What I did?
- Add it when it was missing
- Move it from peerDep to dep when needed
- Use the same, and latest, version for all packages
@gaetanmaisse gaetanmaisse added dependencies maintenance User-facing maintenance tasks and removed dependencies labels Feb 20, 2020
@JalilArfaoui
Copy link
Contributor

Then, why regenerator-runtime hasn’t been set as a regular dependencyinstead of apeerDependency` ?

@ndelangen
Copy link
Member

@JalilArfaoui Where do you see that dependency still specified as a peerDependency?

@JalilArfaoui
Copy link
Contributor

I’m sorry @ndelangen ! I had an out-of-date @storybook/api in my modules, and I felt upon this PR and thought it was still like this !

You can close this, sorry for the inconvenience

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance User-facing maintenance tasks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants