-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm start failing from "Module Not Found" error #1821
Comments
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. |
Ran into the same issue. |
i have a problem cloning this repo. when i do |
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 runningnpm install.
However, I'm still encountering the following error message when running
npm start
:The text was updated successfully, but these errors were encountered: