search

speniti / laravel-mix-workbox

Laravel Mix extension for Workbox
20 stars 5 forks source link

No mix v6.* support? #12

Open jakewhiteley opened 3 years ago

jakewhiteley commented 3 years ago

Describe the bug I cannot run production command using laravel-mix 6.*

To Reproduce Just try to run production script using the most recent laravel-mix (and webpack) package.

Desktop (please complete the following information):

Additional context

> mix --production

        Additional dependencies must be installed. This will only take a moment.

        Running: npm install workbox-webpack-plugin --save-dev --legacy-peer-deps

npm WARN deprecated @hapi/joi@16.1.8: Switch to 'npm install joi'
npm WARN deprecated @hapi/hoek@8.5.1: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/topo@3.1.6: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/address@2.1.4: Moved to 'npm install @sideway/address'
npm WARN deprecated @hapi/formula@1.2.0: Moved to 'npm install @sideway/formula'
npm WARN deprecated @hapi/pinpoint@1.0.2: Moved to 'npm install @sideway/pinpoint'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modules\@types\browser-sync\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"
os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"o
s":"win32","arch":"x64"})

        Finished. Please run Mix again.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! unseen@1.2.1 production: `mix --production`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the unseen@1.2.1 production script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\twent\AppData\Roaming\npm-cache\_logs\2021-06-13T13_26_34_112Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! unseen@1.2.1 prod: `npm run production`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the unseen@1.2.1 prod script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\twent\AppData\Roaming\npm-cache\_logs\2021-06-13T13_26_34_128Z-debug.log
mglaman commented 3 years ago

I'm on 6 and it's working fine. It looks like NPM just took the "rerun again" as a failure