-
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
ng g c component-name command not working #11650
Comments
the same issue happened to me. solved by upgrading npm https://stackoverflow.com/questions/10075990/upgrading-node-js-to-latest-version |
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 |
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 |
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. |
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!
The text was updated successfully, but these errors were encountered: