-
Notifications
You must be signed in to change notification settings - Fork 873
Failed to load external module babel-register #1105
Comments
@kepes please do the following:
|
Thanks @colin-marshall that worked for me like a charm! |
@rescriba01 you're welcome. Those directions actually weren't supposed to solve a problem, but if they solved yours that's great! |
Im getting a similar babel/register error on running 'npm start' on a local dev instance, but everything seems to be working ok. Should I run the same steps you posted @colin-marshall?
|
@adambundy this has confused a lot of people because it's not really an error. Gulp tries one thing, it fails, and then it uses a fallback. As long as the fallback works (which in your case it does) there is nothing to worry about. See here: |
@kepes is this still an issue? |
Thanks @colin-marshall! |
I get that this is meant to be a warning, but then it also derails the script itself with the error
Are these related errors? |
I'm having the same error as @askdesigners. $ gulp d
[10:53:51] Failed to load external module @babel/register
[10:53:51] Requiring external module babel-register
/<REDACTED>/node_modules/gulp-git/node_modules/require-dir/index.js:93
if (!require.extensions.hasOwnProperty(ext)) {
^
TypeError: require.extensions.hasOwnProperty is not a function
at requireDir (/<REDACTED>/node_modules/gulp-git/node_modules/require-dir/index.js:93:37)
at Object.<anonymous> (/<REDACTED>/node_modules/gulp-git/index.js:4:18)
at Module._compile (module.js:653:30)
at Module._extensions..js (module.js:664:10)
at Object.require.extensions.(anonymous function) [as .js] (/<REDACTED>/node_modules/babel-register/lib/node.js:154:7)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)
at Function.Module._load (module.js:498:3)
at Module.require (module.js:597:17)
at require (internal/module.js:11:18) |
Going to chime in on this as well. I'm getting the exact same errors as the above two users:
Has anybody experienced anything similar, or encountered a fix for this? Adding the Running node JS v11.0.0 and npm v6.4.1. |
How can this bug be reproduced?
npm install
andnpm start
as desWhat did you expect to happen?
FoundationPress starts
What happened instead?
Please List the Following:
The text was updated successfully, but these errors were encountered: