AscentCreative's avatar

npx mix watch - only shows first OS Notification

I'm on macOS Monterey, and running npx mix watch gives an initial 'Build Successful' when it first compiles the JS/CSS assets.

If I change the code files, they do recompile successfully, which is fine, but I don't get any more OS notifications. I can't work out why.

I've tried running mix in a standalone terminal window as well as within VS Code, but I get the same issues.

It means I don't also get failure messages without checking the compile window.

Any thoughts on what the problem might be?

0 likes
3 replies
AscentCreative's avatar

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?

AscentCreative's avatar

@Sinnbeck Thanks - yeah, I've tried that too... no joy.

Should the terminal display update on each compile too? for example, the file sizes and compile time don't change.

If it detects an error, the terminal process crashes fully with a stack trace dump - and it needs restarting to watch for future changes to the file.

Is that normal operation? Or should it report an error and keep running?

Please or to participate in this conversation.