-
-
Notifications
You must be signed in to change notification settings - Fork 616
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
CI all green even if package.json is not in sync #1557
Comments
So this is the error message:
But for some reason that does not fail the CI job. The root cause is probably one of the dependabot updates that got merged. |
This is the cause: #1541 Chalk was updated to a new major version that only supports ESM now. |
I am reverting the chalk version now as a quick fix but there are still other todos here:
|
Yep. Your investigation is correct.
|
It's one of the things where I just hack around it too. I have a few projects with esm-only packages, so we can likely copy that configuration to make things work again. Feel free to pick that up if you want to, but otherwise I will get to it, before the year turns 2022. |
Would be great if you could take care of the rest of this issue. I just assigned myself for doing the quick fix. |
Yes! |
I don't think this is the case anymore. |
We noticed the master got out of sync somehow and here in my PR #1476, the package.json is not in sync but the CI is all green nevertheless. If I run the sync command, I get a change for the package.json file.
cc @SleeplessByte @tejasbubane
The text was updated successfully, but these errors were encountered: