-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Angular-cli installs but doesnt start new project: package install failed, see above #3906
Comments
@inddev thanks for creating the issue. It looks like this is a duplicate of #2344 , as it seems from your logs that the installation of
|
Thanks for the quick reply. I installed that package separately using the command-
Then I re-installed angular-cli and tried to initialize a new project. Didnt see an error in angular install but same error in ng new: The error is:
Thinking angular-cli reinstall must have fiddled something, I again installed node-pre-gyp and tried ng new again. Still getting the same error message in ng new command. |
If that doesn't clear it up it may be a permissions issue. Windows isn't 1:1 with the Unix permissions it's most tested under and |
I uninstalled global node-pre-gyp using the commands Then I executed the following commands to install the package locally and initialize the angular skeleton-
I still get the same error. If instead of 'ng init' I had done 'ng new' without installing pre-gyp, I would have still run into the same error. Am I installing node-pre-gyp in an incorrect manner? EDIT- LOG of ng init |
The dependency isn't in your project, but the CLI installations themselves. Did you use a standard or administrator console to install the CLI? |
@inddev It might be that your issue is related to Can you try to remove and reinstall |
@gelliott181 I used an admin console. Anything related to npm I always make sure it is an admin console. @beeman I searched online for issues related to node-gyp and it seems to be a sinkhole of issues, way too many people complaining of issues with node-gyp with no clear fix. It seems one way out of that mess is installing VisualCPP Build Tools, which is appx a 4GB install, besides several other smaller fixes. In my experience, there was no error related to node-gyp when node or even angular was installing, but I do realize that npm contains its own version of node-gyp and prefers to use that instead of that listed in another package's json. Let me figure this out and get back in a couple hours. EDIT/update- In the first install I did, yes node-gyp errors were there. As @beeman mentioned in his first comment. But those disappeared when I reinstalled everything. I will just give it a global reinstall (once I figure out how to do it) and report back EDIT2: I also realized that after I uninstall angular, npm and even node, the folder node-gyp persists in AppData/Roaming/Npm/node_modules folder. So before I reinstall everything I will manually remove this folder. |
If that folder was persisting after an install something about the permissions changed causing it to be unusable to NPM and node. I've yet to see an error about node-gyp under Windows that isn't related to some package mucking around with access rights. That was my reason for bumping node from v6.3 to v6.5 a few months back with a clean reinstall. |
Your problem does seem to be I can tell you that the CLI does not require You can try to use the |
@filipesilva I first manually removed modules in npm directory, also cleared the cache manually and then also using the command. Then I installed npm v4.1.1 using npm-windows-upgrade. Previously I had also followed the steps for node-gyp on their github page (https://github.com/nodejs/node-gyp). Installation of angular-cli didnt throw up errors this time. but creating a new project still leads to the same issue:
When I command ng serve, it says
(dependending really?) |
Just want to add, I have no issues whatsoever when I use the angular-seed project (quickstart). That involved git cloning the quickstart folder, running an npm install and its done. What breaks here in cli? |
Hello people. I'm also having the same issue here on a ubuntu 14.04 x64 installed in virtualbox. I installed the @angular/cli globally, had some problems with dependencies missing, but fixed i with the #2704 json.package . However "ng new" always hangs and then fails. any news on this issue? |
Fixed by #5282 |
Try Below one--- |
i getting error please resolve it |
npm ERR! Unexpected end of JSON input while parsing near '...lMYcrBG1gW4ZC4wzYHRd4' npm ERR! A complete log of this run can be found in: Facing This kind of issue to open new project. |
i have this problem too! |
First u have to install file again and must net speed
…On Thu 13 Dec, 2018, 4:53 PM sanjeevjh ***@***.*** wrote:
i have this problem too!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3906 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AqpgBYnLzMYGxtw8pwM5kPqaXtybD4l9ks5u4jizgaJpZM4Ld4Rj>
.
|
sudo apt-get --purge remove node-gyp |
I am also getting this msg.. npm ERR! Unexpected end of JSON input while parsing near '...rma-phantomjs-launche' npm ERR! A complete log of this run can be found in: |
babakhalid12 : It's working.. Thanks |
i also have problem too |
hello to all........... Thanks........ Shubh |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
BUILD:
Windows 10
angular-cli: 1.0.0-beta.24
node: 6.9.4
os: win32 x64
npm: 3.10.10
LOG for ng new command
LOG for npm install -g -f angular-cli
I cant start a new project in angular-cli, I get some errors while giving the command "ng new xyz-app"
FYI I uninstalled and re-installed angular-cli using the -f handle, after going through other threads describing a similar issue. That did not help. I also reinstalled node (was on npm 4.0.5 earlier, now on 3.10.10). Error on starting new project is:
If I anyway cd into the xyz directory and run npm serve, I get-
I just had a look at installation log, it is full of errors.
The text was updated successfully, but these errors were encountered: