-
Notifications
You must be signed in to change notification settings - Fork 199
Error during install: "websocket Appears to be a git repo or submodule" #929
Comments
I can reproduce this error by simply running the following command in an empty directory.
This is the same dependency that is causing the error. Running the command will create the This is npm's fault as far as I can tell. However, I believe that the package/repo would be able to mitigate this if it specified I am using node 11.15.0 and npm 6.9.0. |
Official comment by the web3.js maintainer on this situation: web3/web3.js#2863 (comment). |
I would not recommend |
Thanks @frangio, we will wait on web3 for the fix then |
The issue on web3 (web3/web3.js#2863 (comment)) was already closed, but obviously no new release was finished yet. It breaks circle-ci as well |
We have error on CI like this: "ganache-core-sc/node_modules/web3-providers-ws/node_modules/websocket: Appears to be a git repo or submodule." After some attempt of removing more ".git" file under node_modules still fails. Disable the use of cache first. - Failed CI: https://circleci.com/gh/omisego/plasma-contracts/2973 - related issue: OpenZeppelin/openzeppelin-sdk#929
We have error on CI like this: "ganache-core-sc/node_modules/web3-providers-ws/node_modules/websocket: Appears to be a git repo or submodule." After some attempt of removing more ".git" file under node_modules still fails. Disable the use of cache first. - Failed CI: https://circleci.com/gh/omisego/plasma-contracts/2973 - related issue: OpenZeppelin/openzeppelin-sdk#929
We have error on CI like this: "ganache-core-sc/node_modules/web3-providers-ws/node_modules/websocket: Appears to be a git repo or submodule." After some attempt of removing more ".git" file under node_modules still fails. Disable the use of cache first. - Failed CI: https://circleci.com/gh/omisego/plasma-contracts/2973 - related issue: OpenZeppelin/openzeppelin-sdk#929
Fixed as web3 was upgraded |
Creating a new issue based on @crazyrabbitLTC's #926.
I have not been able to reproduce this on a fresh install in node 10.16. Based on the message, it would seem like you already had something in your
node_modules
folder. Can you identify the steps you need to run on an empty folder to get to that error?By the way, it would seem like running justrm -rf node_modules/*/.git/
(see this comment) fixes the issue. It should be a faster workaround than clearing all ofnode_modules
.The text was updated successfully, but these errors were encountered: