-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Cannot resolve module 'babel-runtime/*' #1421
Comments
This is weird. Is it still reproducible? Can you provide exact instructions to reproduce it? |
I'll test this out again in the next day or two. |
@gaearon I just removed babel-runtime and it builds now without it. Not sure what exactly was the issue but I guess we can close this now. 🤔 |
Sometimes it's healthier not to know. |
I'm seeing this issue in a different setup.
Since npm install is not deterministic, I'm thinking that babel-runtime
ends up differently in the node_modules hierarchy and surfaces a problem
with a dependency's package.json.
…On Thu, Feb 9, 2017 at 10:39 PM, Dan Abramov ***@***.***> wrote:
Sometimes it's healthier not to know.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1421 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AArOQalhvj86b56Qzd8poNBOMheAXCH5ks5ra4elgaJpZM4LpS0K>
.
--
andreineculau.com <http://www.andreineculau.com>
|
Maybe some module ( |
This is fixed in |
Awesome, thanks for reporting back. |
This is probably more of a question than a bug report.
Recently, out of nowhere, I started having issues with missing
babel-runtime
:So I checked the last commit (which was a while ago) and it passed all commit checks:
Now, if I do clean setup, clone the repo and try to build it, it fails. The only thing that might have changed during this time are dependencies (semantic updates).
Adding
babel-runtime
to my dependencies fixes this issue but I'm not sure if this is the right way to go about it?The text was updated successfully, but these errors were encountered: