Skip to content

Conversation

@parostatkiem
Copy link

@parostatkiem parostatkiem commented Dec 11, 2025

Removed 'node_modules' from the ignore list for asset copying.

Current Behavior

Updating Nx to v22 breaks my app. Some projects use generated Prisma clients which, because of how Prisma binaries work, have to be generated to node_modules in order to work both locally and in Docker context.
With Nx v22 Prisma client is not copied when project is built using @nx/esbuild:esbuild (or any other executor supporting assets property) without any error or warning. It took mi couple of hours to pinpoint the exact line of code responsible for this. node_modules dir is hardcoded there without any possibility to be overridden.

Expected Behavior

Prisma client can be copied from node_modules to project output directory when building.
Ignoring node_modules is removed or can be overridden. I'm open to any solution which will let me update Nx in my repository.

Related Issue(s)

Fixes #

Removed 'node_modules' from the ignore list for asset copying.
@parostatkiem parostatkiem requested a review from a team as a code owner December 11, 2025 11:44
@netlify
Copy link

netlify bot commented Dec 11, 2025

👷 Deploy request for nx-docs pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit c11f438

@vercel
Copy link

vercel bot commented Dec 11, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
nx-dev Ready Ready Preview Dec 11, 2025 11:51am

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants