Closed hadrien-toma closed 4 years ago
babel just published 7.10.4
.. yet not all packages are available on the npm registry.
maybe wait?
Yeap, I can wait. To avoid this impacting other developers, shouldn't we include a test of these "getting started" commands to validate a release? Or maybe this is due to a not enough deterministic versioning bug here?
In any case, I would be happy to help :slightly_smiling_face:
The new version of babel is now available, which makes the commands working :yum: . I still would be happy to help preventing this occurring in the future.
https://github.com/babel/babel/issues/11766 i suspect npm was at fault here
Thank you for the link to this issue, I assume we can close this one. Feel free to re-open if it reveals to not be on NPM side.
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
Current Behavior
The application is not created.
Expected Behavior
The creation of the application.
Steps to Reproduce
Failure Logs
Environment