Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

npm and gulp not working #16283

Closed
11 tasks
pyasskin opened this issue Apr 7, 2017 · 1 comment
Closed
11 tasks

npm and gulp not working #16283

pyasskin opened this issue Apr 7, 2017 · 1 comment

Comments

@pyasskin
Copy link

pyasskin commented Apr 7, 2017

I'm opening this issue because:

  • [x ] npm is crashing.
  • npm is producing an incorrect install.
  • x[ ] npm is doing something I don't understand.
  • Other (see below for feature requests):

What's going wrong?

Because of previous problems, I was told the node-modules should not be saved with the repository since it is different on Win/Mac/Linux. So I added node_modules/ to .gitignore. Then gulp stopped working and npm would not reinstall gulp. I tried reinstalling node.js. No change. it says
Error: Cannot find module 'browser-sync'
I tried several thinks shown in attachment.
How do I get thinks working again?
Thanks

How can the CLI team reproduce the problem?

supporting information:

  • npm -v prints:

  • node -v prints:

  • npm config get registry prints:

  • Windows,
    gitnpmgulperror.txt
    npm-debug.pdf

  • Network issues:

    • Geographic location where npm was run:
    • I use a proxy to connect to the npm registry.
    • I use a proxy to connect to the web.
    • I use a proxy when downloading Git repos.
    • I access the npm registry via a VPN
    • I don't use a proxy, but have limited or unreliable internet access.
  • Container:

    • I develop using Vagrant on Windows.
    • I develop using Vagrant on OS X or Linux.
    • I develop / deploy using Docker.
    • I deploy to a PaaS (Triton, Heroku).
@npm-robot
Copy link

We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants