-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
PrimeNG integration #411
Comments
there are two versions of Angular 2 installed. they need to update their angular2 dep or set as a peerDep |
Merged now, thank you. |
@cagataycivici thanks |
@bPopovska did you get it running? We have basics running but datepicker makes trouble :( |
@Sicaine Still running into issues. Can't get primeng to work when source maps are enabled. |
@bPopovska Are the widget styles issues you talk about related to the images urls of the style? i'm using sass-loader and as it just process the import statement as if that theme content were copied to the importing file, it breaks the images urls since now that content is in a different folder. |
I've done a fork to add PrimeNG for the UI; https://github.com/cagataycivici/angular2-webpack-starter |
@cagataycivici Does dialogs work in yours? the errors above i fixed using the url loader but now i have issues when using the Dialog and seems related to jquery. |
Yes, it works for me in my fork above. |
I don't use assets for Css I just do a require on node modules in app.ts Envoyé de mon iPhone
|
@cagataycivici Maybe my error is related to the way jquery is loaded due to me using the NgUpgrade package to try and update an Ng1 app? i'll take a deeper look at your starter and see what's the issue. 😄 |
Does anyone have experience with integrating the primeNG library in a webpack based project?
Trying to integrate it in this starter results in the following error:
Error: No Directive annotation found on Button at new BaseException (http://localhost:3000/main.bundle.js:1318:24) at DirectiveResolver.resolve (http://localhost:3000/main.bundle.js:11928:16) at RuntimeMetadataResolver.getDirectiveMetadata (http://localhost:3000/main.bundle.js:32492:52) at http://localhost:3000/main.bundle.js:32549:63 at Array.map (native)
The text was updated successfully, but these errors were encountered: