MMM-Jast 2.9.2 doesn't install on newest MM version 2.26

soonerdm

Any thoughts on how to fix this error?
pi@raspberrypi:~/MagicMirror/modules/MMM-Jast $ npm install --only=production
npm WARN config only Use --omit=dev to omit dev dependencies from the install.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: mmm-jast@2.9.2
npm ERR! Found: @typescript-eslint/eslint-plugin@4.33.0
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR! dev @typescript-eslint/eslint-plugin@“^6.14.0” from the root project
npm ERR! @typescript-eslint/eslint-plugin@“^4.7.0” from eslint-config-airbnb-typescript-prettier@4.2.0
npm ERR! node_modules/eslint-config-airbnb-typescript-prettier
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! dev @typescript-eslint/eslint-plugin@“^6.14.0” from the root project
npm ERR!
npm ERR! Conflicting peer dependency: @typescript-eslint/parser@6.19.1
npm ERR! node_modules/@typescript-eslint/parser
npm ERR! peer @typescript-eslint/parser@“^6.0.0 || ^6.0.0-alpha” from @typescript-eslint/eslint-plugin@6.19.1
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR! dev @typescript-eslint/eslint-plugin@“^6.14.0” from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/pi/.npm/_logs/2024-01-23T15_27_25_863Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /home/pi/.npm/_logs/2024-01-23T15_27_25_863Z-debug-0.log

Jalibu

Thank you @KristjanESPERANTO for providing a fix for it.

sdetweil

@soonerdm sadly the --onit=dev STILL CHECKS all the dev dependencies even tho they will not be installed… dumb

so edit that package.json and add a 1 to the key
devdependencies (on phone so check spelling)

then it won’t be found during install

lmk. I’ve done this many times.

soonerdm

@sdetweil Not sure what you mean by add a 1 to the key.
Here is my package.json devDependancies block

 "devDependencies": {
                "@stylistic/eslint-plugin": "^1.5.1",
                "eslint-plugin-import": "^2.29.1",
                "eslint-plugin-jest": "^27.6.0",
                "eslint-plugin-jsdoc": "^46.9.1",
                "express-basic-auth": "^1.2.1",
                "husky": "^8.0.3",
                "jest": "^29.7.0",
                "jsdom": "^23.0.1",
                "lint-staged": "^15.2.0",
                "lodash": "^4.17.21",
                "playwright": "^1.40.1",
                "prettier": "^3.1.1",
                "sinon": "^17.0.1",
                "stylelint": "^16.1.0",
                "stylelint-config-standard": "^36.0.0",
                "stylelint-prettier": "^5.0.0",
                "suncalc": "^1.9.0"
        },

sdetweil

@soonerdm said in MMM-Jast 2.9.2 doesn't install on newest MM version 2.26:

“devDependencies”: {

JSON is ‘key’/‘value’ pairs

so the ‘key’ here is

"devDependencies"

so make it

"devDependencies1"

watch out for the curved quotes before I used the code block…

soonerdm

@sdetweil Gotcha. I thought the key needed a 1. Not that we were renaming it to skip. Thank you. I understand it now.

Jalibu

Thank you @KristjanESPERANTO for providing a fix for it.