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

ng g c component-name command not working #11650

Closed
gchawla7 opened this issue Jul 25, 2018 · 4 comments
Closed

ng g c component-name command not working #11650

gchawla7 opened this issue Jul 25, 2018 · 4 comments
Labels
area: angular/cli needs: repro steps We cannot reproduce the issue with the information given

Comments

@gchawla7
Copy link

ng g c component-name command not working using the ngx-admin project
while the same command works if we have default Angular 2 application.

It is throwing the exception:

ng g c test-component
Error compiling schema, function code: var customRule0 = customRules[0];var customRule1 = customRules[1]; var validate = async function(data, dataPath, parentDa
.....
, message: 'should be object' } ]); } if (errors === 0) return data;
else throw new ValidationError(vErrors); }; return validate;
Unexpected token function

Thanks in advance!

@sujith2014
Copy link

sujith2014 commented Jul 25, 2018

the same issue happened to me. solved by upgrading npm

https://stackoverflow.com/questions/10075990/upgrading-node-js-to-latest-version

@filipesilva filipesilva added needs: repro steps We cannot reproduce the issue with the information given area: angular/cli labels Jul 25, 2018
@filipesilva
Copy link
Contributor

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?

You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

@alan-agius4
Copy link
Collaborator

Closing as no reproduction was provided.

If the problem persists, please open a new issue following our submission guidelines.

A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: angular/cli needs: repro steps We cannot reproduce the issue with the information given
Projects
None yet
Development

No branches or pull requests

4 participants