-
Notifications
You must be signed in to change notification settings - Fork 39
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
"premature close" error during npm install from git url #1
Comments
Same Problem |
I feel the need to comment this out for anyone who finds this into the future and arrives here confused like me; I could tell you to use yarn or to just clone the repo, it doesn't seem like anything will happen anytime to it soon tbh, or just wait and see for a pull merge |
THANKS A LOT!!! |
Any updates |
This happened for me when my package was missing a package.json |
see Pull Request #2 |
I got this when the git repo I was pulling in had an extra comma within it's packages.json. i.e. I was pulling in diff --git a/package.json b/package.json
index 0857fae..8df9c04 100644
--- a/package.json
+++ b/package.json
@@ -35,7 +35,7 @@
"data-spreadsheet"
],
"dependencies": {
- "jsuites": "github:deftdawg/jsuites",
+ "jsuites": "github:deftdawg/jsuites"
},
"main": "dist/jexcel.js",
"version": "4.3.0", |
@deftdawg Thanks a lot! You saved me so much time! "premature close" certainly is a very detailed error message... 😒 |
Also remember to have correct repository link in repository section of package.json |
Sure thing, |
I know/see, that this repo doesn't have
package.json
, and I doAlso tried ssh. Same result.
I'm from MacOS
v10.13.4
have nodev10.1.0
and npmv6.0.1
and it throws me an error:As I understand it's either npm issue with package with no package.json or smth else.
I found similar issues in npm, but looks like ti was solved in node v8:
@coryetzkorn as a suggestion, I would recommend you to add
package.json
and publish this module. I'm using it for my work related project, and recently I moved stateface from Bower (https://github.com/propublica/stateface) to NPM, but, in fact I found that SVG files are using from this repository. I still working on my task, and maybe I will get rid of using files from your repo and reuse dmn-stateface module (https://github.com/DallasMorningNews/stateface which is fork from probulica repo but published as npm module)PS. Here is log from Node 6.x and npm 3.x on Windows 7, and it's about another error
EISDIR
:The text was updated successfully, but these errors were encountered: