-
Notifications
You must be signed in to change notification settings - Fork 4.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
Error related to themes not being imported properly on version 18.0.0 #17059
Comments
Interesting! Could you please attach a sample project link for us to replicate? |
More information is needed to find a solution. A runnable StackBlitz example and additional details would be helpful. |
I am getting similar error with nx 20, ng 19 and primeng 19.0.0-rc.1. Project is buildable, everything is working but eslint is throwing errors
I created repo for reproduction, but everything worked there 😆. After careful examination I found out that the problem is with |
Thanks a lot, @MarKayS ;) |
that didnt fix it for me, i dont think i even have eslint-import-resolver-alias... this is a module import error |
Describe the bug
./apps/ui/src/main.ts:18:39-70 - Error: Module not found: Error: Package path ./aura is not exported from package /Users//Desktop//node_modules/@primeng/themes (see exports field in /Users//Desktop//node_modules/@primeng/themes/package.json)
I am using nx for my project and I recently migrated to the primeng version 18.0.0. I followed the documentation and removed the styles from the styles.scss and imported the Aura theme in my main.ts file using the providePrimeNG. When i check my nodemodules I see the themes.
Perhaps this is an issue with NX..
Environment
I am running my nx project locally on my mac. Im using nx version 17, primeng verison 18 and angular version 18
Reproducer
No response
Angular version
18.0.1
PrimeNG version
18.0.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.9.0
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: