When create with --sass, npm build does work, main.js is missing.

[Cybermage83]

94% asset optimization
100%
mv: no such file or directory: .../build/static/main.js
Done: 9662.041ms

Couldn't parse bundle asset "...\build\static\main.js".
Analyzer will use module sizes from stats file.

Webpack Bundle Analyzer saved report to ...\build\static\report.html

Something is wrong when sass project is created..
Dev server and portal work just fine. @supnate Suggestions?

[supnate]

Thanks @Cybermage83 for reporting this. It's not an error but a case not well handled. Don't need to worry about it. I will remove the error msg in the next release.

[Cybermage83]

Just did true webpack build, got this error, which is probably why i am not generating the main.js

[./index.js] ./index.js 1.75 kB {0} [built]
+ 620 hidden modules

ERROR in multi babel-polyfill ./styles/index.scss ./index
Module not found: Error: Can't resolve 'less-loader' in '...\src'
@ multi babel-polyfill ./styles/index.scss ./index

Less loader??

[supnate]

There should be no less-loader in webpack-config.js. Could you check?

[Cybermage83]

there was one on scss rule, as a final fall back.
also, i got it work, but i had to create a new non functional webpack.config.js and then run webpack to generate main.js after that i could to npm build so that timestamp can be assigned.

I am on windows machine, I don;t know if it matters, but something is weird going for a sass build

[Cybermage83]

OKie it looks like i found the real culprit >>
loader: isDev ? 'style-loader!css-loader?sourceMap!sass-loader?sourceMap'
: 'style-loader!css-loader!less-loader'

Right here... definitely need a fix here heh

[supnate]

I did find an error in the generated sass project. In webapck-config.js there's a less-loader for scss files, it should be sass-loader:

{
test: /.scss$/,
loader: isDev ? 'style-loader!css-loader?sourceMap!sass-loader?sourceMap'
: 'style-loader!css-loader!sass-loader'
}

I've not found why it just works on my machine, will investigate.

[Cybermage83]

cool, glad we got that figured out. Thanks.

[supnate]

The bug was fixed in the latest 2.0.6 version.