Skip to content
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

Changed AngularCLI Global preferences and CLI setting in Angular Proj… #110

Merged
merged 1 commit into from
Sep 14, 2017
Merged

Conversation

probert94
Copy link
Contributor

…ect-Wizard

See #107 and #94

In the global preferences, only the value "use global cli" is now validated.
The custom values won't be validated, since you often install only a project-private cli.

In the Angular Project-Wizard you can now choose to use global cli preferences, instead of a globally installed cli.

…ect-Wizard

See #107 and #94

- The global preference page now only validates the "global cli".
- The Angular Project-Wizard has now the option to use global preferences instead of global CLI.
@angelozerr angelozerr added this to the 1.4.0 milestone Sep 14, 2017
@angelozerr angelozerr merged commit 73b8245 into angelozerr:master Sep 14, 2017
@angelozerr
Copy link
Owner

Thanks @Springrbua !

@wuzhen0808
Copy link

With Windows7 OS , In new project wizard,
If "Use global",then error:"The 'C:/Users/wu/AppData/Roaming/npm/ng.cmd' is not a ng file".
If check "Install", it can create the project and install the Angular CLI.
Later, each time if you open the Typescript/Angular/CLI, it will popup a message saying "C:/projectpath/node_modules/.bin/ng.cmd' is not a valid ng file"

Is that caused by the invalid path separator :"/" ? Since the ng.cmd is there, it exists.

@probert94
Copy link
Contributor Author

@x2361 I just checked it and it seems like when you use browse button, it inserts path with \, so the problem will probably be the /.

@angelozerr
Copy link
Owner

@Springrbua is there any change to have a fix?

@probert94
Copy link
Contributor Author

@angelozerr I don't think this is a bug. You just need to correct the pathname to use windows-style separators.

@garymazz
Copy link

I'm still having the problem on windows 10.

I use windows style separators and they seems to be replaced in java path. Normally java auto corrects for platform path separators.

This is a bug under windows 10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants