Foundation-sites: Failed to load external module @babel/register with cli

Created on 29 Dec 2017  路  6Comments  路  Source: foundation/foundation-sites

Help, I start the project with cli, and it gives me this error, in the end if it starts the server but it always gives me this error and I do not know if it's something very bad.

captura de pantalla 2017-12-29 13 21 26

won't fix

Most helpful comment

@ralts00 it's only an issue if you are deathly allergic to the color red. However, I've opened an issue at https://github.com/gulpjs/gulp-cli/issues/142 to consider changing the color.

All 6 comments

Hmm, interesting. I'm getting the same problem after a fresh install of Foundation CLI and then setting up a new foundation email project. Wasn't expecting this to be so easy to reproduce!

Considering babel has gone through some significant changes in the last year, it wouldn't surprise me if a package previously used in foundation emails isn't available anymore.

Found a similar issue here: https://github.com/gulpjs/gulp/issues/1631

Looks like babel/register is there as a fallback, in case babel-register fails to work (which is the default in this case). But that's just my hypothesis at this point. :)

So long as your project still works, I would consider this a warning and to not worry about it. Unless of course a more involved dev can confirm otherwise. Hope this helps.

Not an issue, as it states on the next line down, it required babel-core/register. Babel now suggests you use a module called babel-register so we try that first with the fallback. Please read your entire log before creating an issue.
-- @phated

but it is a issue, because an error appears in red, they should eliminate that error in red @ncoden

@ralts00 it's only an issue if you are deathly allergic to the color red. However, I've opened an issue at https://github.com/gulpjs/gulp-cli/issues/142 to consider changing the color.

@phated I thank you very much for taking the comments of the community :)

Was this page helpful?
0 / 5 - 0 ratings