laravel-mix VS Laravel Mix

const path = require('path') const fs = require('fs-extra') const mix = require('laravel-mix') require('laravel-mix-versionhash') const tailwindcss = require('tailwindcss') // const { BundleAnalyzerPlugin } = require('webpack-bundle-analyzer') mix .js('resources/js/app.js', 'public/dist/js').vue() .sass('resources/sass/app.scss', 'public/dist/css') .options({ processCssUrls: false, postCss: [tailwindcss('./tailwind.config.js')] }) .disableNotifications() if (mix.inProduction()) { mix // .extract() // Disabled until resolved: https://github.com/JeffreyWay/laravel-mix/issues/1889 // .version() // Use `laravel-mix-versionhash` for the generating correct Laravel Mix manifest file. .versionHash() } else { mix.sourceMaps() } mix.webpackConfig({ plugins: [ // new BundleAnalyzerPlugin() ], resolve: { extensions: ['.js', '.json', '.vue'], alias: { '~': path.join(__dirname, './resources/js') } }, output: { chunkFilename: 'dist/js/[chunkhash].js', path: path.resolve(__dirname, mix.inProduction() ? './public/build' : './public') } }) mix.then(() => { if (mix.inProduction()) { process.nextTick(() => publishAseets()) } }) function publishAseets () { const publicDir = path.resolve(__dirname, './public') fs.removeSync(path.join(publicDir, 'dist')) fs.copySync(path.join(publicDir, 'build', 'dist'), path.join(publicDir, 'dist')) fs.removeSync(path.join(publicDir, 'build')) }

Yeah, I'm the guy who tells you: No one is forcing you to switch to Vite. Laravel Mix still works and will work for the forseeable future. Mix isn't even part of the Laravel GitHub organisation and noone from the core Laravel team has contributed to the package in the last few months.

"It is fixed." https://github.com/mikaelbr/node-notifier/issues/361 via https://github.com/laravel-mix/laravel-mix/issues/2937 via https://github.com/josephdyer/skeleventy/issues/32

A quick Google search led me to here. Which suggested that I add the following to my webpack.mix.js file:

I've found a workaround and raised an issue (https://github.com/JeffreyWay/laravel-mix/issues/3045)

Oh, have I got the thing for you. You can just use laravel-mix for the common usecases:

Try laravel-mix, makes it a lot easier.

Let's not forget the time webpack did this but only on Mondays to cut down on spam, causing builds to fail on Mondays

https://github.com/JeffreyWay/laravel-mix/issues/2550#issuecomment-752735914