Thanks - but I've done that already.
My webpack.mix.js does not contain the methods listed on that page, so they're not being disabled in that way.
This is my webpack file:
const mix = require('laravel-mix');
/*
|--------------------------------------------------------------------------
| Mix Asset Management
|--------------------------------------------------------------------------
|
| Mix provides a clean, fluent API for defining some Webpack build steps
| for your Laravel applications. By default, we are compiling the CSS
| file for the application as well as bundling up all the JS files.
|
*/
mix.scripts([
'assets/*.js'
],
'assets/dist/js/ascent-filter-bundle.js',
'assets/dist/js'
)
.styles([
'assets/*.css'
],
'assets/dist/css/ascent-filter-bundle.css',
'assets/dist/css'
);
- I do get an initial success notification, so disableNotifications() cannot be in use
- I don't get any error notifications, so disableSuccessNotifications() cannot be in use
Is there another location that these controls can be set?
Is it something OS-specific, rather than to do with mix?