npm list --depth=0): [email protected]node -v): v6.11.3npm -v): 6.0.1MacOS 10.13.6This is a redux of #627, which is closed and I'm not sure if it's visible anymore.
File paths added to mix.scripts() that do not exist do not throw any errors, and the build does not fail.
mix.scripts() call to an existing laravel setup's webpack.mix.js.mix.scripts(['random/file/exists-not.js', 'another/non/entity.js'], 'public/assets/js/new.js'); .npm run dev'public/assets/js/new.js'.According to @JeffreyWay in June of last year, this was fixed in 1.0.0, but I'm still having the problem.
Can confirm this happens, in my case with mix.babel()
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Bump.
Hope this gets looked at. In big projects a small typo can go unnoticed, as I've already seen happen, unless the developer changes into production mode to use the compiled files which should be unnecessary as this should throw an error immediately during the build.
Lack of an error still blows my mind. It is otherwise a wonderful library that I am hella thankful for.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Yo. This is still bad Dev-X.
I continue to hope this gets solved. I hate having to triple check things when the library should be capable of at least give a warning.
@joaolisboa we are the only ones! 馃槶
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.