err occurs on npm install laravel 5.7

@cullobsidian7 there is no node-sass in my package.json, and i already tryed that.

@pt844931 Try upgrading to a newer version of laravel-mix like 6.x.

@Sinnbeck Okay it seems the installation worked. But now if im parsing an command like npm run dev it throws that error

> watch
> npm run development -- --watch


> development
> cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js "--watch"

[webpack-cli] Error: Unknown option '--hide-modules'
[webpack-cli] Run 'webpack --help' to see available commands and options

I changed now the Scripts in guessing that these are the problems i had these in other projects already. But now it throws command "mix" not found. do i need to do something else?

@Sinnbeck help me with my issue too please

@pt844931 Can you show what you have now in package.json? The command should just be

"development": "mix",

@Sinnbeck Scripts are like that

{
    "scripts": {
        "dev": "npm run development",
        "development": "mix",
        "watch": "mix watch",
        "watch-poll": "mix watch -- --watch-options-poll=1000",
        "hot": "mix watch --hot",
        "prod": "npm run production",
        "production": "mix --production"
    },

And the Dependencies

    "devDependencies": {
        "@fortawesome/fontawesome-free": "^5.4.2",
        "bootstrap": "~4.1.3",
        "cross-env": "~5.2.0",
        "jquery": "~3.3.1",
        "laravel-mix": "6.*",
        "lodash": "~4.17.11",
        "popper.js": "~1.14.4",
        "resolve-url-loader": "^5.0.0",
        "sass": "^1.49.9",
        "sass-loader": "^12.6.0"
    },

@pt844931 can you try renaming your package.lock to package.lock.old and remove node_modules. Then run npm install. And now try npm run dev

@Sinnbeck still the same error... maybe some compatibility problems with node npm versions?

if i run the command in the terminal of my vm it get stucked then i break the command and it throws another error

ERROR in ./resources/sass/app.scss
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
ValidationError: Invalid options object. Sass Loader has been initialized using an options object that does not match the API schema.
 - options has an unknown property 'uglify'. These properties are valid:
   object { implementation?, api?, sassOptions?, additionalData?, sourceMap?, webpackImporter?, warnRuleAsWarning? }
    at validate (/var/www/html/node_modules/webpack/node_modules/schema-utils/dist/validate.js:105:11)
    at Object.getOptions (/var/www/html/node_modules/webpack/lib/NormalModule.js:585:19)
    at Object.loader (/var/www/html/node_modules/sass-loader/dist/index.js:27:24)
    at processResult (/var/www/html/node_modules/webpack/lib/NormalModule.js:758:19)
    at /var/www/html/node_modules/webpack/lib/NormalModule.js:860:5
    at /var/www/html/node_modules/loader-runner/lib/LoaderRunner.js:399:11
    at /var/www/html/node_modules/loader-runner/lib/LoaderRunner.js:251:18

1 ERROR in child compilations (Use 'stats.children: true' resp. '--stats-children' for more details)
webpack compiled with 2 errors

@pt844931 It might be. Can you update to a newer version?

@Sinnbeck I updated now node to v16.14.2 and npm to v8.5.0 but still the error which i last parsed in.

Okay and now it crashed all again, seems that was not a good choice ^^

@pt844931 What error now? command mix not found?

@Sinnbeck Yeah a bit strange if i use it inside my phpstorm terminal it throws command 'mix' not found but in my terminal of the vm it throws -->

ERROR in ./resources/sass/app.scss
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
ValidationError: Invalid options object. Sass Loader has been initialized using an options object that does not match the API schema.
 - options has an unknown property 'uglify'. These properties are valid:
   object { implementation?, api?, sassOptions?, additionalData?, sourceMap?, webpackImporter?, warnRuleAsWarning? }
    at validate (/var/www/html/node_modules/webpack/node_modules/schema-utils/dist/validate.js:105:11)
    at Object.getOptions (/var/www/html/node_modules/webpack/lib/NormalModule.js:585:19)
    at Object.loader (/var/www/html/node_modules/sass-loader/dist/index.js:27:24)
    at processResult (/var/www/html/node_modules/webpack/lib/NormalModule.js:758:19)
    at /var/www/html/node_modules/webpack/lib/NormalModule.js:860:5
    at /var/www/html/node_modules/loader-runner/lib/LoaderRunner.js:399:11
    at /var/www/html/node_modules/loader-runner/lib/LoaderRunner.js:251:18

1 ERROR in child compilations (Use 'stats.children: true' resp. '--stats-children' for more details)
webpack compiled with 2 errors

@pt844931 Can you show your mix config file. That could the source of the problem if it uses some old syntax. I personally cleared mine, and wrote the configuration from scratch when I upgraded :)

@Sinnbeck Okay i see that, i never really watched over the webpack.mix file :D. That Raphael package is from the core developer implemented package which now is also not loading

const mix = require('laravel-mix');

/*
 |--------------------------------------------------------------------------
 | Mix Asset Management
 |--------------------------------------------------------------------------
 |
 | Mix provides a clean, fluent API for defining some Webpack build steps
 | for your Laravel application. By default, we are compiling the Sass
 | file for the application as well as bundling up all the JS files.
 |
 */

mix.autoload({ 'raphael': ['Raphael'] })
    .js('resources/js/app.js', 'public/js')
    .sass('resources/sass/app.scss', 'public/css', {
        purifyCss: true,
        uglify: {
            extractComments: 'all'
        }
    });

if (mix.inProduction()) {
    mix.version();
}

@pt844931 Not sure what that is. Did you try removing it from the config file and see if it works then?

const mix = require('laravel-mix');

/*
 |--------------------------------------------------------------------------
 | Mix Asset Management
 |--------------------------------------------------------------------------
 |
 | Mix provides a clean, fluent API for defining some Webpack build steps
 | for your Laravel application. By default, we are compiling the Sass
 | file for the application as well as bundling up all the JS files.
 |
 */

mix .js('resources/js/app.js', 'public/js')
    .sass('resources/sass/app.scss', 'public/css', {
        purifyCss: true,
        uglify: {
            extractComments: 'all'
        }
    });

if (mix.inProduction()) {
    mix.version();
}

@Sinnbeck Okay so i erased all the plugin options in the sass method, also there was a problem in my scss file there was an package was outdated i commented that out and now it seems to work. at least npm run dev is working in the terminal of vm, but the commands are not working in the integrated terminal of the IDE. And the npm run watch script loads one time but does not detect an change in the scss file. And also the command is working but there are no changes in the css file.

@pt844931 Ok this is getting kinda hard to debug without the code... I would ignore your IDE for now (until you are done) and just go with the terminal if that somewhat works.. So with npm run dev it now works completely or?

@Sinnbeck Yeah, npm run dev is working right now and i also saw that the css file is actual so it gets updates. So i can handle the Js and css over npm run dev script for now. I can maybe do an copy later of the repo and send to you then we can take a look over it again! :)

@pt844931 You are welcome to do that :)

@Sinnbeck Alright then i write later again. Right now i try to do some stuff, atleast we could make one script working :D But many thanks for the good help!!!

@pt844931 Happy to help. You should get laravel upgraded as well as that seems a bit overdue :)

@Sinnbeck Yeah, i thought about that but the administrator of the company is afraid that the tool could be destroyed, if we do that ^^. Its pretty important that this thing is working. ^^

@pt844931 ah that sucks. But if it ain't broken.. As long as it's not accessible from the outside and it does not need any updates on the laravel part

@Sinnbeck Hey again, if you have time i sended you invitation for the repo @github :).

@pt844931 Still having problems or was it just so I could have a look at the code?

@Sinnbeck For me its already working good enough, just for you if you want to take a look of the code. :)