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

Yarn 2 (Berry) support #1311

Open
schickling opened this issue Jul 31, 2020 · 1 comment
Open

Yarn 2 (Berry) support #1311

schickling opened this issue Jul 31, 2020 · 1 comment
Labels
type/feat Add a new capability or enhance an existing one

Comments

@schickling
Copy link
Contributor

Perceived Problem

Currently nexus (aka Nexus Framework) can't be used with Yarn 2 ("Berry"). This is probably due to "assumptions" Nexus has about node_modules and where both generated artifacts and the Nexus CLI "binary" is expected to live.

Ideas / Proposed Solution(s)

Make Nexus work out-of-the-box with Yarn 2 🙃

@schickling schickling added the type/feat Add a new capability or enhance an existing one label Jul 31, 2020
@trulysinclair
Copy link

trulysinclair commented Aug 16, 2020

True, but there's a temporary workaround, yarn config set nodeLinker node_modules. I hope one day Nexus supports the yarn cache too, I'd recommend just putting everything into project-local directory, so that we also have workspaces support.

PS
While that does solve the node_modules yarn still throws everything into a <workspaceRoot>/node_modules which is why workspaces aren't supported. Prisma also suffers from this issue, because it creates a <workspaceRoot>/node_modules/.prisma/client rather than a project-local modules folder..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feat Add a new capability or enhance an existing one
Projects
None yet
Development

No branches or pull requests

2 participants