-
Notifications
You must be signed in to change notification settings - Fork 12k
viewEncapsulation is not defined #3264
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
Comments
I have the same issue with.. angular-cli: 1.0.0-beta.20-4 Any idea what happend in the last changes? Two weak ago everythinks works fine.. edit: npm link angular-cli in root dir was help me.. now works good |
I am also getting this when trying to generate a component. It started on beta.20-4 for me. angular-cli: 1.0.0-beta.21 |
I think it may have broken by this feature: #2822 You can kludge around it by adding
to the "defaults" section of your angular-cli.json. It's supposed to leave out those properties in the new component if the defaults aren't specified, but instead it crashes. |
angular-cli: 1.0.0-beta.21 I could not get the error in either a new or existing project. |
As of my last update of Angular CLI, I am also receiving this error when generating components.
|
i have same issue,
when i try to use '--skip-import', i'm also receive this error. then i try to use @teledemic advise angular-cli: 1.0.0-beta.21 |
angular-cli: 1.0.0-beta.22-1 thx @teledemic, your solution work for me. |
This seems to be working fine in master |
Also got this error. Tried several things already :)
dit the fix |
Closing this as fixed. |
Change .angular-cli.json like this, working on 1.0.0
|
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. |
OS?
Mac OSX el capitan
Versions.
angular-cli: 1.0.0-beta.21
node: 6.6.0
os: darwin x64
Repro steps.
Ran command
ng g component purchase-leads
The log given by the failure.
Mention any other details that might be useful.
The text was updated successfully, but these errors were encountered: