You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I've done:
*add some .js and .css files in the 'src' directory
*run 'npm start', develop a little bit, things are working
*kill server, go to sleep. Wake up, start server --> error: 'cannot find module cross-spawn'
I'm closing because this appears to be an issue with your npm setup, and we can't really fix it. Please try deleting node_modules and re-running npm install.
No. I had to delete my node module directory each time i stop the server as
well. which i dont mind
Dwayne Neckles
\Interactive Ad Designer, Front End Developer
Portfolio:dnecklesportfolio.comLinkedIn: https://www.linkedin.com/in/dnecklesfrontend
Mobile:917 607 5509
On Thu, Oct 6, 2016 9:50 PM, JonasMS notifications@github.com
wrote:
Running "npm i" didn't fix the issue? Make sure you're in the project directory.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
one thing i noticed that yesterday i didn't get devDeps installed on an
existing project, that was working fine (i just used same source and
moved to another folder). and that was due to `npm config get
production` which was set to true, which doesn't install devDeps. don't
know how this happened, because I never switched this setting. so I had
to type `npm config set production false` for install to work properly.
this was when migrating gitlab server. perhaps this is a node/gitlab issue?
Activity
gaearon commentedon Aug 12, 2016
This looks like something weird with your
npm
setup.Try running
npm install
in the project directory.gaearon commentedon Aug 14, 2016
I'm closing because this appears to be an issue with your npm setup, and we can't really fix it. Please try deleting node_modules and re-running npm install.
jonasms commentedon Aug 17, 2016
Sorry for the slow response!
Running 'npm install' again seems to have fixed it. . .
dnecklesportfolio commentedon Oct 7, 2016
Hi Jonas, its weird I have this same issue to but I'm going to look into reinstalling it. thx
jonasms commentedon Oct 7, 2016
Running "npm i" didn't fix the issue? Make sure you're in the project directory.
dnecklesportfolio commentedon Oct 7, 2016
No. I had to delete my node module directory each time i stop the server as
well. which i dont mind
Dwayne Neckles
\Interactive Ad Designer, Front End Developer
Portfolio:dnecklesportfolio.comLinkedIn:
https://www.linkedin.com/in/dnecklesfrontend
Mobile:917 607 5509
On Thu, Oct 6, 2016 9:50 PM, JonasMS notifications@github.com
wrote:
Running "npm i" didn't fix the issue? Make sure you're in the project directory.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
jonasms commentedon Oct 7, 2016
Odd. Post what fixes it on your end, even if just reinstalling does the trick.
themre commentedon Oct 7, 2016