-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
6.0.0 breaks AoT: datatable.component.scss not found #459
Comments
+1 |
same issue |
Are you manually including that file? You shouldn't have to now. |
I never included that file manually. As a workaround I copied it to the components directory and now AoT works. I do not know why it ends up in the parent directory, it is correctly referenced to in the component with its relative path. |
+1 |
I'm working on a fix now |
Is this only breaking in AoT? I'm not hitting this but I'm almost not running AoT. |
Aot only |
If you need some test feedback on a PR, let us know! |
+1 |
Anyone have any ideas how to fix this? I converted it to the |
+1 |
I see this file getting built? Is that not it? -> https://github.com/swimlane/ngx-datatable/blob/master/release/components/datatable.component.scss.ngstyle.ts |
Fixed in 6.0.1 |
Unfortunately this doesn't fix the issue.
You can reproduce it by creating an sample angular-cli project and import the module. |
I can also confirm the issue is not fixed yet. I have even prepared a sample setup here https://github.com/smoke/ngx-datatable-aot-issue you can just execute Hope this helps fixing the issue sooner. ==== On a side note, you should correct the path in https://github.com/swimlane/ngx-datatable/blob/master/docs/introduction/themes.md
->
|
Thanks looking into this today! |
Please retest. I made a temp fix to move the scss for now. |
I confirm, the fix seems to be working. If anyone else wants to take a look, I have updated the repo https://github.com/smoke/ngx-datatable-aot-issue |
Im trying to build aot version 6.0.2 result: Im using webpack, In my project im using less, do I need also scss loader to use this library? |
Ya, thats the side effect of that hack. I thought that might happen. I'm still investigating the best way to do this without it being even more hacky... |
@amcdnl I am having the same issue with Angular 4.0.3 and version 2.3.0 typscript |
Is this issue fixed? I'm still having same problem on 6.3.0 release with angular 2.4.10. |
@sh977218 can you upgrade to latest and test? @xtianus79 can you post the error? |
I am having the same problem with 10.0.5 building AOT. Here is the error: Child node_modules@swimlane\ngx-datatable\release\components\datatable.component.css:
|
You are getting this in your project? |
@amcdnl post the error? |
Any update on this? ERROR in Child compilation failed: For AOT, webpack config for parsing is |
@kabilya do you have solved this problem? i met the same one too. |
I am also experiencing this issue using WebPack, scss and css excluding node_modules from loaders.. |
@we125182 @werts I abandoned this library last year due to its issue with AOT. I tried it again this year as it has currently have more features/functions than Material's MatTable.. I downloaded the entire source code from their repo and just included the entire ./src folder in my project. import { NgxDatatableModule } from './ngx-datatable/index'; It's building now with my Angular 4.x project both in dev and production. Hope this helps. |
In my case I resolved the issue by simply removing module import statement. |
Kinda same issue here, but it's actually JIT only, AOT works great (though, a while ago, it was the exact opposite 🙄).
(i tried many I end up with error at runtime : I fixed it using webpack :
Though, using angular-cli I did not find any way to fix it. There's many issues (opened or closed) about |
I'm submitting a ... (check one with "x")
Current behavior
AOT build using
angular-cli
beta 26 fails:ERROR in ENOENT: no such file or directory, open '/foo/frontend/node_modules/@swimlane/ngx-datatable/release/components/datatable.component.scss'
Expected behavior
Reproduction of the problem
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Table version: 0.7.x
6.0.0
Angular version: 2.0.x
2.4.5
Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.
n/a
Language: [all | TypeScript X.X | ES6/7 | ES5]
Typescript 2.1.4
The text was updated successfully, but these errors were encountered: