try to fix HAL-editor mic asked if icould load npm7.x and try again npm version 7.24.2 is last of 7.x series so... tomp@dbn9sda1:~$ sudo npm install -g npm@7.24.2 [sudo] password for tomp: removed 6 packages, changed 25 packages, and audited 259 packages in 8s 11 packages are looking for funding run `npm fund` for details 3 moderate severity vulnerabilities To address all issues, run: npm audit fix Run `npm audit` for details. tomp@dbn9sda1:~$ ****************************************************************************** looks pretty good so far apply the suggested fix ****************************************************************************** tomp@dbn9sda1:~$ sudo npm audit fix npm ERR! code ENOLOCK npm ERR! audit This command requires an existing lockfile. npm ERR! audit Try creating one first with: npm i --package-lock-only npm ERR! audit Original error: loadVirtual requires existing shrinkwrap file npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2021-11-17T04_47_59_753Z-debug.log ****************************************************************************** ok create the lockfile ****************************************************************************** tomp@dbn9sda1:~$ npm i --package-lock-only npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm ERR! code ENOENT npm ERR! syscall open npm ERR! path /home/tomp/package.json npm ERR! errno -2 npm ERR! enoent ENOENT: no such file or directory, open '/home/tomp/package.json' npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent npm ERR! A complete log of this run can be found in: npm ERR! /home/tomp/.npm/_logs/2021-11-17T04_49_05_348Z-debug.log tomp@dbn9sda1:~$ ****************************************************************************** ok rerun prev cmd ****************************************************************************** tomp@dbn9sda1:~$ sudo npm audit fix removed 78 packages, and audited 1 package in 808ms found 0 vulnerabilities ****************************************************************************** wow never saw npm ever do anything with so few warnings/errors now the suggestion "s it possible to install npm v 7.x and test again?" what does test again entail??? cd to dir with HAL-editor npm install ********************************************************************** tomp@dbn9sda1:/media/tomp/toms4T/2021/cadcamctl/ctl/emc/Hal-Editor-webbased/HAL-Editor-master$ npm install up to date, audited 669 packages in 7s 64 packages are looking for funding run `npm fund` for details 6 vulnerabilities (4 low, 1 high, 1 critical) To address issues that do not require attention, run: npm audit fix Some issues need review, and may require choosing a different dependency. Run `npm audit` for details. tomp@dbn9sda1:/media/tomp/toms4T/2021/cadcamctl/ctl/emc/Hal-Editor-webbased/HAL-Editor-master$ ********************************************************************** ok npm audit to see whats detected low/high/crtical and what does critical mean? bad security, blows up ?? ********************************************************************** tomp@dbn9sda1:/media/tomp/toms4T/2021/cadcamctl/ctl/emc/Hal-Editor-webbased/HAL-Editor-master$ npm audit # npm audit report lodash <=4.17.20 Severity: critical Command Injection in lodash - https://github.com/advisories/GHSA-35jh-r3h4-6jhm Prototype Pollution in lodash - https://github.com/advisories/GHSA-p6mc-m468-83gw Prototype Pollution in lodash - https://github.com/advisories/GHSA-jf85-cpcp-j695 Prototype pollution in lodash - https://github.com/advisories/GHSA-x5rq-j2xg-h7qm Prototype Pollution in lodash - https://github.com/advisories/GHSA-fvqr-27wr-82fm No fix available node_modules/node-shell-parser/node_modules/lodash node-shell-parser * Depends on vulnerable versions of lodash node_modules/node-shell-parser node-fetch <2.6.1 The `size` option isn't honored after following a redirect in node-fetch - https://github.com/advisories/GHSA-w7rc-rwvf-8q5r fix available via `npm audit fix` node_modules/node-fetch isomorphic-fetch 2.0.0 - 2.2.1 Depends on vulnerable versions of node-fetch node_modules/isomorphic-fetch fbjs 0.7.0 - 1.0.0 Depends on vulnerable versions of isomorphic-fetch node_modules/fbjs react-addons-create-fragment >=15.4.2 Depends on vulnerable versions of fbjs node_modules/react-addons-create-fragment 6 vulnerabilities (4 low, 1 high, 1 critical) To address issues that do not require attention, run: npm audit fix Some issues need review, and may require choosing a different dependency. tomp@dbn9sda1:/media/tomp/toms4T/2021/cadcamctl/ctl/emc/Hal-Editor-webbased/HAL-Editor-master$ tomp@dbn9sda1:/media/tomp/toms4T/2021/cadcamctl/ctl/emc/Hal-Editor-webbased/HAL-Editor-master$ npm audit # npm audit report lodash <=4.17.20 Severity: critical Command Injection in lodash - https://github.com/advisories/GHSA-35jh-r3h4-6jhm Prototype Pollution in lodash - https://github.com/advisories/GHSA-p6mc-m468-83gw Prototype Pollution in lodash - https://github.com/advisories/GHSA-jf85-cpcp-j695 Prototype pollution in lodash - https://github.com/advisories/GHSA-x5rq-j2xg-h7qm Prototype Pollution in lodash - https://github.com/advisories/GHSA-fvqr-27wr-82fm No fix available node_modules/node-shell-parser/node_modules/lodash node-shell-parser * Depends on vulnerable versions of lodash node_modules/node-shell-parser node-fetch <2.6.1 The `size` option isn't honored after following a redirect in node-fetch - https://github.com/advisories/GHSA-w7rc-rwvf-8q5r fix available via `npm audit fix` node_modules/node-fetch isomorphic-fetch 2.0.0 - 2.2.1 Depends on vulnerable versions of node-fetch node_modules/isomorphic-fetch fbjs 0.7.0 - 1.0.0 Depends on vulnerable versions of isomorphic-fetch node_modules/fbjs react-addons-create-fragment >=15.4.2 Depends on vulnerable versions of fbjs node_modules/react-addons-create-fragment 6 vulnerabilities (4 low, 1 high, 1 critical) To address issues that do not require attention, run: npm audit fix Some issues need review, and may require choosing a different dependency. tomp@dbn9sda1:/media/tomp/toms4T/2021/cadcamctl/ctl/emc/Hal-Editor-webbased/HAL-Editor-master$ ********************************************************************** for lodash No fix available for node-fetch <2.6.1 npm audit fix th rest depend on vulnerab;le versions so i decide dont bother ********************************************************************** tomp@dbn9sda1:/media/tomp/toms4T/2021/cadcamctl/ctl/emc/Hal-Editor-webbased/HAL-Editor-master$ npm audit fix npm ERR! code ERESOLVE npm ERR! ERESOLVE could not resolve npm ERR! npm ERR! While resolving: material-ui@0.15.0 npm ERR! Found: react@17.0.2 npm ERR! node_modules/react npm ERR! react@"^17.0.2" from the root project npm ERR! peer react@">=16.8.0" from @emotion/react@11.4.0 npm ERR! node_modules/@emotion/react npm ERR! @emotion/react@"^11.4.0" from the root project npm ERR! peer @emotion/react@"^11.0.0-rc.0" from @emotion/styled@11.3.0 npm ERR! node_modules/@emotion/styled npm ERR! @emotion/styled@"^11.3.0" from the root project npm ERR! 1 more (@projectstorm/react-diagrams-defaults) npm ERR! 1 more (@projectstorm/react-diagrams-defaults) npm ERR! 14 more (@emotion/styled, @material-ui/core, ...) npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"^15.0.0" from material-ui@0.15.0 npm ERR! node_modules/material-ui npm ERR! material-ui@"^0.15.0" from the root project npm ERR! npm ERR! Conflicting peer dependency: react@15.7.0 npm ERR! node_modules/react npm ERR! peer react@"^15.0.0" from material-ui@0.15.0 npm ERR! node_modules/material-ui npm ERR! material-ui@"^0.15.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! See /home/tomp/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /home/tomp/.npm/_logs/2021-11-17T05_06_47_381Z-debug.log tomp@dbn9sda1:/media/tomp/toms4T/2021/cadcamctl/ctl/emc/Hal-Editor-webbased/HAL-Editor-master$ tomp@dbn9sda1:/media/tomp/toms4T/2021/cadcamctl/ctl/emc/Hal-Editor-webbased/HAL-Editor-master$ npm audit fix npm ERR! code ERESOLVE npm ERR! ERESOLVE could not resolve npm ERR! npm ERR! While resolving: material-ui@0.15.0 npm ERR! Found: react@17.0.2 npm ERR! node_modules/react npm ERR! react@"^17.0.2" from the root project npm ERR! peer react@">=16.8.0" from @emotion/react@11.4.0 npm ERR! node_modules/@emotion/react npm ERR! @emotion/react@"^11.4.0" from the root project npm ERR! peer @emotion/react@"^11.0.0-rc.0" from @emotion/styled@11.3.0 npm ERR! node_modules/@emotion/styled npm ERR! @emotion/styled@"^11.3.0" from the root project npm ERR! 1 more (@projectstorm/react-diagrams-defaults) npm ERR! 1 more (@projectstorm/react-diagrams-defaults) npm ERR! 14 more (@emotion/styled, @material-ui/core, ...) npm ERR! npm ERR! Could not resolve dependency: npm ERR! peer react@"^15.0.0" from material-ui@0.15.0 npm ERR! node_modules/material-ui npm ERR! material-ui@"^0.15.0" from the root project npm ERR! npm ERR! Conflicting peer dependency: react@15.7.0 npm ERR! node_modules/react npm ERR! peer react@"^15.0.0" from material-ui@0.15.0 npm ERR! node_modules/material-ui npm ERR! material-ui@"^0.15.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! See /home/tomp/.npm/eresolve-report.txt for a full report. npm ERR! A complete log of this run can be found in: npm ERR! /home/tomp/.npm/_logs/2021-11-17T05_06_47_381Z-debug.log tomp@dbn9sda1:/media/tomp/toms4T/2021/cadcamctl/ctl/emc/Hal-Editor-webbased/HAL-Editor-master$ ********************************************************************** the more i try audit fix, the worse it gets dont try anymore audit fix try to run ********************************************************************** tomp@dbn9sda1:/media/tomp/toms4T/2021/cadcamctl/ctl/emc/Hal-Editor-webbased/HAL-Editor-master$ npm start > linuxcnc_halbuilder@0.0.1 start > ./node_modules/.bin/webpack serve --open [webpack-cli] Invalid options object. Dev Server has been initialized using an options object that does not match the API schema. - options has an unknown property 'overlay'. These properties are valid: object { allowedHosts?, bonjour?, client?, compress?, devMiddleware?, headers?, historyApiFallback?, host?, hot?, http2?, https?, ipc?, liveReload?, magicHtml?, onAfterSetupMiddleware?, onBeforeSetupMiddleware?, onListening?, open?, port?, proxy?, server?, setupExitSignals?, static?, watchFiles?, webSocketServer? } ********************************************************************** same old same old stop 17nov2021 12:11 log shows errs beginning with an ERESOLVE i dont know enough to work thru the interdependancies, and the fancy python auto-tools cant either