Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
3.1.3 EISGIT error
See original GitHub issueInstalling version 3.1.3 is causing an EISGIT error. It looks like it’s being caused by a .git directory in the installed module.
I’ve hardcoded to version 3.1.2 to get around the error for now.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:11
- Comments:9
Top Results From Across the Web
Fixing the EISGIT npm appears to be a git repo or submodule ...
Fixing the EISGIT npm appears to be a git repo or submodule Error. This happened when i was deploying an app to heroku....
Read more >How to update npm modules, ignoring a git repo
npm checks all directories for the existance of a .git directory, and throws the EISGIT error if it exists, so there is no...
Read more >GitPython Tutorial — GitPython 3.1.29 documentation
The first step is to create a git.Repo object to represent your repository. from git import Repo # rorepo ...
Read more >React Native Notes 22: npm ERR! code EISGIT [Solution]
Just run this command, then npm i again and it will work. Simple but I recommend you to upgrade your RN version to...
Read more >Solving “Fatal: Not A Git Repository” (Or Any Of The Parent ...
How do Git repositories work? a. Stage the files b. Commit the changes c. Push the code; What are some common Git errors?...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Or if one uses npm, create a postinstall script and use rimraf to delete the git directory.
Of course that’s only a workaround
uninstall 3.1.3 then install 3.1.2 explicitly
npm i react-native-push-notification@3.1.2 -S