Nice! A slightly alternative way that's worth looking, to help avoid problems (more than just syntax errors) with JS code before we attempt to productionize them by running through minifiers or concatenators is to run the project's JS files through some sort of linter first (jslint, jshint, eslint... whatever works for you). This way it not only points out the errors in detail in specific files and line numbers but also forces us to maintain consistent coding and follow some best practices for large codebases :)
Nice! A slightly alternative way that's worth looking, to help avoid problems (more than just syntax errors) with JS code before we attempt to productionize them by running through minifiers or concatenators is to run the project's JS files through some sort of linter first (jslint, jshint, eslint... whatever works for you). This way it not only points out the errors in detail in specific files and line numbers but also forces us to maintain consistent coding and follow some best practices for large codebases :)
I can't imagine writing without a linter.
It's probably about errors introduced by merges.