npm start failing from "Module Not Found" error

[digracesion]

I checked that the dependencies node-gyp, gulp-cli, webpack, webpack-cli and mermaid were installed. I also ran npm audit fix --force to make sure the package-lock is updated after running npm install.

However, I'm still encountering the following error message when running npm start:

PS C:\Users\windows\coderepos\markdown\stackedit\stackedit> npm start

> [email protected] start
> node build/dev-server.js

node:internal/modules/cjs/loader:1042
  throw err;
  ^

Error: Cannot find module 'webpack/lib/RuleSet'
Require stack:
- C:\Users\windows\coderepos\markdown\stackedit\stackedit\node_modules\vue-loader\lib\plugin.js
- C:\Users\windows\coderepos\markdown\stackedit\stackedit\build\webpack.base.conf.js
- C:\Users\windows\coderepos\markdown\stackedit\stackedit\build\webpack.dev.conf.js
- C:\Users\windows\coderepos\markdown\stackedit\stackedit\build\dev-server.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1039:15)
    at Module._load (node:internal/modules/cjs/loader:885:27)
    at Module.require (node:internal/modules/cjs/loader:1105:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (C:\Users\windows\coderepos\markdown\stackedit\stackedit\node_modules\vue-loader\lib\plugin.js:2:17)
    at Module._compile (node:internal/modules/cjs/loader:1218:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1272:10)
    at Module.load (node:internal/modules/cjs/loader:1081:32)
    at Module._load (node:internal/modules/cjs/loader:922:12)
    at Module.require (node:internal/modules/cjs/loader:1105:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'C:\\Users\\windows\\coderepos\\markdown\\stackedit\\stackedit\\node_modules\\vue-loader\\lib\\plugin.js',
    'C:\\Users\\windows\\coderepos\\markdown\\stackedit\\stackedit\\build\\webpack.base.conf.js',
    'C:\\Users\\windows\\coderepos\\markdown\\stackedit\\stackedit\\build\\webpack.dev.conf.js',
    'C:\\Users\\windows\\coderepos\\markdown\\stackedit\\stackedit\\build\\dev-server.js'
  ]
}

Node.js v18.13.0

[knackstedt]

When I forked the repo, I encountered various build issues.

You can try downgrading to NodeJS 12, but it's a bit of a coin toss whether or not you'll be able to build the project on master.

[jansalleine]

Ran into the same issue. Solved it by installing node v12.22.12 via nvm ( nvm install 12 ) and not using npm audit fix. Even on node v12 npm audit fix breaks something.

[remarkablejames]

i have a problem cloning this repo. when i do npm install it fails saying many packages are not supported. any help ?

[KedarS14]

I am also facing the same issue for npm install , even i have tried peer legacy command , then also it is not starting , any way will it start , as i could see , its updates are from last 6 and 7 years

[knackstedt]

Yeah. This was why I ultimately forked it. My fork works, but has some bugs that I'm not bothering to address because there are parts of the codebase that I simply can't work around without a pretty serious fundamental overhaul. I've begun working on a completely ground-up markdown editor because of this reason.