Closed devarsh closed 8 years ago
Hi @devarsh!
It is quite annoying indeed that our plugin doesn't show exactly what is missing and where. However we are not planning to support it. At the moment we are getting your webpack config file just by running a standard require
, we are not parsing the file, then we can't do more than what node provides, in terms of error messages, and parsing the file would be too much work for little benefits.
I recommend you to use a linter like Eslint, it would show the missing comma in your editor, also if you use babel-register
, it should show an error as well.
Sorry for the inconvenience!
@adriantoine thanks, perhaps we can add it to troubleshooting
Had faced an issue when i forgot to put comma to seperate webpack alias, and every time i tried running the babel with babel-plugin-webpack-alias it failed with the following error.
error
webpack config