Skip to content
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

Open
AlexanderAvazkhodjayev opened this issue Dec 16, 2024 · 5 comments
Assignees
Labels
Status: Pending Review Issue or pull request is being reviewed by Core Team
Milestone

Comments

@AlexanderAvazkhodjayev
Copy link

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.
image

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

@AlexanderAvazkhodjayev AlexanderAvazkhodjayev added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Dec 16, 2024
@mertsincan
Copy link
Member

Interesting! Could you please attach a sample project link for us to replicate?

@mertsincan mertsincan added Resolution: Needs More Information More information about the issue is needed to find a correct solution and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Dec 16, 2024
@mertsincan mertsincan added this to the 19.x milestone Dec 16, 2024
@github-project-automation github-project-automation bot moved this to Review in PrimeNG Dec 16, 2024
Copy link

More information is needed to find a solution. A runnable StackBlitz example and additional details would be helpful.

@MarKayS
Copy link

MarKayS commented Dec 16, 2024

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

ESLint: Resolve error: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './aura' is not defined by "exports" in ... package.json

I created repo for reproduction, but everything worked there 😆.

After careful examination I found out that the problem is with eslint-import-resolver-alias. After disabling it, everything seems to work. Hope it helps if anybody has similar problem.

@mertsincan
Copy link
Member

Thanks a lot, @MarKayS ;)

@mertsincan mertsincan added Status: Pending Review Issue or pull request is being reviewed by Core Team and removed Resolution: Needs More Information More information about the issue is needed to find a correct solution labels Dec 16, 2024
@mertsincan mertsincan self-assigned this Dec 16, 2024
@AlexanderAvazkhodjayev
Copy link
Author

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

ESLint: Resolve error: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './aura' is not defined by "exports" in ... package.json

I created repo for reproduction, but everything worked there 😆.

After careful examination I found out that the problem is with eslint-import-resolver-alias. After disabling it, everything seems to work. Hope it helps if anybody has similar problem.

that didnt fix it for me, i dont think i even have eslint-import-resolver-alias... this is a module import error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pending Review Issue or pull request is being reviewed by Core Team
Projects
Status: Review
Development

No branches or pull requests

3 participants