Hi All,

I am still using web pack and try to keep my code up to date. Today when I did "nom outdated" I saw this:

@babel/core 7.29.7 7.29.7 8.0.1 node_modules/@babel/core application @babel/preset-env 7.29.7 7.29.7 8.0.2 node_modules/@babel/preset-env application

So I upgraded to 8.0.1.

However, after doing this I am now getting:

[webpack-cli] Error: Cannot find module '@babel/plugin-syntax-dynamic-import'

When I run "npm run dev" or "rpm run prod".

I have my own branch of laravel mix repo (as I made other small changes over time) and I was wondering if someone could tell me what to change/remove to get rid of this error so it will compile.

Thanks!

-Rob

I did this and it seems to work:

"laravel/framework": "^13.2.0@stable",

Hmm.. when I make that change it won't update as some other packages (like mailgun) require "dev".

Interesting:

"minimum-stability": "dev", "prefer-stable": true,

That's probably the issue, it's been like this for years from back to Laravel 6.

I have just never seen a dev branch come down before (maybe I never noticed).

Thanks, I will change to "stable".

Hi All,

I did my daily "composer update" today and something caught my eye:

Upgrading laravel/framework (v13.16.1 => 13.x-dev 2107d3d): Extracting archive

Usually it will go from a version to a [higher] version not some weird dev branch.

To my knowledge I have not changed anything in my environment that would cause me to grab a developer branch and was wondering what's up.

Is anyone else seeing this?

(I am going to refrain from deploying this)

Thanks!

-Rob

Hi All,

I am still using Laravel Mix and up until today it's been working. I updated to the latest today (I run "npm update" and "composer update" daily.

Today I am getting this error when I am running "npm run production".

Does anyone have any ideas what might be conflicting?

➜ application git:(main) npm run production

production cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --config=node_modules/laravel-mix/setup/webpack.config.js

[webpack-cli] Invalid options object. Progress Plugin has been initialized using an options object that does not match the API schema.

• options should be one of these: object { activeModules?, dependencies?, dependenciesCount?, entries?, handler?, modules?, modulesCount?, percentBy?, profile? } | function Details:
  • options has an unknown property 'name'. These properties are valid: object { activeModules?, dependencies?, dependenciesCount?, entries?, handler?, modules?, modulesCount?, percentBy?, profile? } -> Options object for the ProgressPlugin.
  • options has an unknown property 'color'. These properties are valid: object { activeModules?, dependencies?, dependenciesCount?, entries?, handler?, modules?, modulesCount?, percentBy?, profile? } -> Options object for the ProgressPlugin.
  • options has an unknown property 'reporters'. These properties are valid: object { activeModules?, dependencies?, dependenciesCount?, entries?, handler?, modules?, modulesCount?, percentBy?, profile? } -> Options object for the ProgressPlugin.
  • options has an unknown property 'reporter'. These properties are valid: object { activeModules?, dependencies?, dependenciesCount?, entries?, handler?, modules?, modulesCount?, percentBy?, profile? } -> Options object for the ProgressPlugin.