You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 7, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 7, 2021. It is now read-only.
Webpack compilation doesn't stop on syntactic errors in js/vue apps #1067
Currently CLI handles only Module not found errors (wrong require/import) in js/vue applications. This is due to the fact that Module not found errors are handled by webpack itself during the compilation.
The .js files inside js/vue applications are processed using raw-loader. It doesn't analyze the code, just copies the content of the file to bundle/vendor. However, using another loader (for example, eslint-loader) will resolve this problem as it'll analyze the code according the give options (.eslint file) and will report them to the webpack. That way, CLI will stop on syntax/semantic errors in js/vue apps.
Activity
Fatme commentedon Oct 22, 2019
Currently CLI handles only
Module not founderrors (wrong require/import) in js/vue applications. This is due to the fact thatModule not founderrors are handled by webpack itself during the compilation.The
.jsfiles insidejs/vueapplications are processed usingraw-loader. It doesn't analyze the code, just copies the content of the file to bundle/vendor. However, using another loader (for example, eslint-loader) will resolve this problem as it'll analyze the code according the give options (.eslint file) and will report them to the webpack. That way, CLI will stop on syntax/semantic errors in js/vue apps.