-
Notifications
You must be signed in to change notification settings - Fork 3k
[BETA issue] npm init is not working as expected with github dependencies #20399
Description
I don't know if this is the right channel to give some BETA channel feedback, please let me know if there is a better place to put these sorts of comments.
I just tested something with the new npm init command that I expected to work based on previous conventions but maybe it's not on the spec for this new feature.
I'm trying to get the following command to work:
npx [email protected] init ember-app my-app
(real talk for a second: this is amazing that I can do this!! npx is so cool!!)
as it turns out there is some specific behaviour in create-ember-app that expects yarn to be installed. As this is open source we're talking about I forked it and removed the yarn specific command and then wanted to run this to test the new fork:
npx [email protected] init stonecircle/create-ember-app my-app
It seems to be trying to do the right thing but misses the mark by a tiny amount 😂 here is the output:
npx: installed 680 in 10.394s
npm ERR! Error while executing:
npm ERR! /usr/bin/git ls-remote -h -t ssh://[email protected]/create-stonecircle/create-ember-app.git
npm ERR!
npm ERR! ERROR: Repository not found.
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/mansona/.npm/_logs/2018-04-21T07_58_49_792Z-debug.log
Install for github:create-stonecircle/create-ember-app failed with code 1
I then tried npx [email protected] init github:stonecircle/create-ember-app my-app to see if the github: previx made a difference but then got this output:
➜ what npx [email protected] init github:stonecircle/create-ember-app my-app
npx: installed 680 in 13.275s
ENOENT: no such file or directory, stat 'create-github:stonecircle/create-ember-app'
Is this something that npm is likely wanting to support? I am reluctant to create a throw-away npm package just to test if my patch fixes the issue upstream
supporting information:
npm -vprints: N/A usingnpx [email protected]node -vprints: v8.11.1npm config get registryprints: https://registry.npmjs.org/- Windows, OS X/macOS, or Linux?: macOS
Is this a feature you're prepared to implement, with support from the npm CLI team?
Yes 😄 I would love to contribute 🎉 I think that the expected behaviour would need to be defined and then I would happily help out with a bit of guidance