`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
Yarn 2 introduce an error for this during `yarn install`: YN0002 - MISSING_PEER_DEPENDENCY
For details see https://dev.to/arcanis/implicit-transitive-peer-dependencies-ed0
TL;DR: If you write a package that depends on Foo, and if Foo has a peer dependency, then you must provide it in either of the dependencies or peerDependencies fields. You won't "implicitly inherit" the peer dependencies declared in Foo.
- `@types/webpack-env` must be defined as `dependencies` in packages that export a type/function using typings from `@types/webpack-env` (it is often `NodeModule`). In that case `/// <reference types="webpack-env" />` is present in some files of the `dist` folder of the lib. Example: `lib/client-api`.
- `@types/webpack-env` must be defined as `devDependencies` in packages that use its typings internally but does not expose anything related to it. Many addons need the type because they use `module.hot` function. Example: `addons/a11y`
- `webpack-env` should be removed from "compilerOptions.types" key of `tsconfig.json` of packages that don't need it.
I also bump `@types/webpack-env` to ^1.15.0 to have the same version all across the monorepo
