Closed kontrollanten closed 5 years ago
We have greenkeeper in place, but mdc explicitly ignored, because it is a huge effort to update them, that's why we:
a) do this manually b) don't do this for every update
2.0 will deliver the latest and greatest version of mdc
Yarn should handle the resolution correctly, so please consider that
Please let me know if that didn't solve the problem
yarn is no alternative because it crashes other parts. But I think I've got it working by changing package-lock
manually. Thanks for quick response.
This is more of a npm problem than webpack, that's why I always directly create projects with yarn
Also yarn import
may help you migrating without crashes (yarn is faster too)
Thanks for a great package!
What do you think about installing Renovate or something similar, to keep the MDC packages up to date?
I just upgrade webpack in my project and the Dialog got broken because webpack changed (fixed?) dependency resolving, so that @material/dialog got updated to latest release (with a new API). If we try to keep this package dependencies up to date, I guess it can help some people to track errors and get new features.