Module build failed: ReferenceError: Promise is not defined

[aditaa]

im getting errors wile running
npm run build

it still seams to build the files but they do not work .... is it mabe a version issue .....

i want to try to build the git version and not the release version as i want the new feature from #147

any help would be great

error log
http://pastebin.com/GUGn36Qc

[Lothiraldan]

Did you ran npm install first?

[aditaa]

yes npm install and ./node_modules/bower/bin/bower install ran without errors

[aditaa]

if i try to load that dist this is the error in the browser console

vendors.js:1 Uncaught SyntaxError: Unexpected token <
app.js:1 Uncaught SyntaxError: Unexpected token <

[Lothiraldan]

I will try with an empty node_modules and tries to reproduce the error

[MisterTK]

For what it's worth...using a Windows system to setup the npm environment fails every time with a "Promise is not defined" error. Setting up the npm environment completes successfully, and all appears to be healthy. npm run build doesn't work. Even when running "npm start" the page will launch, and it will login, then bomb out with a promise not defined error. I beat my head against the wall, but couldn't get past it. I built a new ubuntu vm, and everything worked flawlessly. Not sure if this is applicable, but that's my two cents.

[Lothiraldan]

Which node version do you use? According to webpack-contrib/css-loader#144, you may have a too old node version

[aditaa]

i will try that and let you know

[aditaa]

ok so i updated node js to latest stable version and i no longer get the errors running npm run build but the end result is still the same

[aditaa]

it appears #147 has it look for the files in ./static/ cp'ing the files there worked to fix the issue

[Lothiraldan]

Right, I forget to specify it in the changelog, sorry, will fix it

[Lothiraldan]

It is fixed now