Cannot resolve module 'babel-runtime/*'

[scholtzm]

This is probably more of a question than a bug report.

Recently, out of nowhere, I started having issues with missing babel-runtime:

• Cannot resolve module 'babel-runtime/helpers/extends'
• Cannot resolve module 'babel-runtime/regenerator'

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?

[gaearon]

This is weird. Is it still reproducible? Can you provide exact instructions to reproduce it?

[scholtzm]

I'll test this out again in the next day or two.

[scholtzm]

@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.

🤔

[gaearon]

Sometimes it's healthier not to know.

[andreineculau]

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>

[gaearon]

Maybe some module (semantic-ui-react judging by first post's CI log) that depends on it forgets to declare a dependency. In this case whether the dependency exists or not depends on other project dependencies and is non-deterministic. Have you raised an issue with the library causing this, like semantic-ui-react?

[levithomason]

This is fixed in semantic-ui-react@0.64.8.

[gaearon]

Awesome, thanks for reporting back.