-
Notifications
You must be signed in to change notification settings - Fork 139
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
Repeatedly performing npm-install fails with EISGIT: Appears to be a git repo or submodule #13
Comments
seems that project owner needs to remove git repository from the package... |
+1 I am also having this issue. As @alexgvozden mentions, the package needs to be updated to remove the |
Any plans on this getting fixed? |
Bump 😅 |
@kkjdaniel 's solution got this work! |
i solved this problem by removing it before performing npm install again as it suggests. |
Having same issue |
Please fix it, I have the same issue |
Bump |
+1 |
Having same issue |
same issue, and have to manually remove .git directory inside the package |
+1 |
5 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
Is this project dead? |
|
Sorry! Not dead, just very very busy. This was merged & solved a while ago. Thanks for reporting! |
By the way could you also add these files to ignore in the They are useless for the user and it just makes your package heavier.
|
Will try to do it later, @VinceBT. Cool avatar BTW 😉 |
Thi should fix `EISGIT` errors during `npm install`. The error happened with npm v6.2.0 (probably other versions as well) when `npm i` was run multiple times in a repo (e.g. for package updates). It did not matter whether the FSPromise package was installed as a direct dependency of the repo or as a 2nd level dependency. A very similar problem was documented here: APSL/react-native-version-number#13
This^ worked for me since I had a custom module (not from) npm installed and it had a .git hidden folder tracking it. Thanks @kkjdaniel ! |
i did his coomand from my project root folder and i lost my .git file and the branches,make sure you dont use this command in wrong place |
Hey, I don't want to delete the .git folder in one of the npm packages, since I'm checking out the latest updates for this package from the repo. Thus, I'm not able to install other npm packages, since it keeps complaining, that this particular package has a git repo. How to proceed? Or: What's the reason of this behavior? |
@jo3ran refer this stackoverflow question How to update npm modules, ignoring a git repo some imes it might be helpfull |
Ubuntu 18.4 |
you can use |
Same problem while installing moment package. it say I've remove the |
add this to your package.json file in the scripts json part
|
remove any .git files present in the node_modules folder In your terminal, from your project folder: |
this works perfectly. thank you |
kkjdaniel worked for me. |
I don't care if this was 2+ years ago. This was the fix for me and I want to say that I love you. |
i also love @alexgvozden |
Try updating NPM to version 6.10. This is a known issue with NPM v6.9. https://npm.community/t/npm-6-9-1-is-broken-due-to-git-folder-in-published-tarball/8454/5 |
This worked like a charm for me |
I also use:
so that if Therefore I have:
|
Hi there, not sure if this is specific to the zsh console, but I had to adjust the command for it to work for me (two asterisks instead of one).
|
When repeatedly performing
npm install
with a dependency onreact-native-version-number
, npm fails with the error codeEISGIT
.I have declared a dependency on on
react-native-version-number
in my package.json like so:Performing
npm install
for the first time succeeds. Performingnpm install
immediately again will fail:When inspecting the installed
react-native-version-number
module innode_modules
, I found that the module contains a.git
file.Any help resolving this failure would be much appreciated. Thanks!
The text was updated successfully, but these errors were encountered: