Open vamp opened 8 years ago
I'm having the same issue. There were some major changes to babel recently.
@MarkDeVerno what was your fix?
Anybody find a solution for this? Spent several hours setting this up only to hit issue #24 (which would be good to resolve). Trying to workaround by compiling via Gulp but breaks here.
@chrconlo @sdluxeon I gave up on a fix and just rolled back to a previous version.
Yes, I went back to Nov 2014 commit and used npm link from local copy and all works well now. Thanks
chrconlo is right. Rolling back to d88af3ad72d72e907c5d681e38ab6c7ebf06acd6 is the answer.
Hey guys, there is a fix to this I found on SO. Well... there is a fix to getting the Gulp build to work anyway. Its a pretty simple fix and relates to how slashes are handled between windows and OSX.
At the top of gulpfile.js you need to add the following variable to the gulp and plugins variables: slash = require('slash');
Then at the bottom of the file edit the babelTranspile function. Add a new line at the top of the function and paste the following: pathname = slash(pathname);
This will allow the build to execute and the application will load from the dist folder. I have no idea how steve is running from the src folder in the demo however. No browsers support ES6 so the imports declarations in the startup file in my mind will never work, they would have to be updated to ES5 require statements.
Original answer to the gulp problem found here:
@Kevinio04 I spend almost day to resolve same issue. Thanks for your solution, its works :) 👍
if (!babelCore.canCompile(pathname)) return callback();
returns error: