-
-
Notifications
You must be signed in to change notification settings - Fork 54
Issue with Angular 5.x #31
Comments
The workaround is similar to the one mentioned here: angular/angular#20091 (comment) I managed to temporarily fix this issue by adding this to the
|
I'm trying what you mentioned and still getting the same error! |
Hm. What does the error message say? Does it mention which file is 'is not part of the compilation output'? |
Update
and it seems to work ========================== Hi! I have almost same error. I have added to
In and error is:
Thanks! |
The file it says the problem with is just a node_modules npm pckg that consists of a very simple component .ts file along with some assets ( images and css ) |
Apparently you cannot delvier non-compiled libraries with migration to Angular 5.x & CLI 1.5.0. See angular/angular-cli#8284 The ngx-quill-editor library will need to pre-compile its delivery. |
Any ETA on the fix? |
It would be great to have this problem fixed |
The same thing happen to me. It is working when I build the project with AOT but when I try to compile it same error popup like @alan345 Is there any solution? |
While you wait on this, for anyone else that runs into this problem, just grab the files and add to your own build directly like in the screenshot. I know it is not ideal... But deadlines have to be met. :) And as you can see from my screenshot, there are quite a few plugins i use that are yet to be updated and give the same exact error. Hope this helps someone. |
Hi Guys, |
@DanushkaAmith Thanks for the tip! Sorry for the beginner question, but what is the best way to link to that repo using npm? I haven't quite understood how you can "make build install" an npm package directly off a git repo. |
A github repo is located at
|
I've decided to migrate to https://github.com/Ledzz/angular2-tinymce |
I works for me was facing issue for index.ts. All set using this. Thanks alot |
install those package ```
|
After upgrading my project to Angular 5, I now get this error when running
ng serve
:There's a workaround for this, but it would be good if this issue is fixed.
The text was updated successfully, but these errors were encountered: