Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Prisma2 packages causes Yarn install devDependencies on --prod
See original GitHub issueI don’t know which repo should this issue belong to, but apparently, prisma packages causes yarn --prod to install all devDependencies (not npm install --prod=true). Adding either @prisma/photon or nexus-prisma to dependencies cause the wrong yarn behavior, and it is fixed if I moved all prisma packages to devDependencies.
Please have a look into this Yarn issue I created as well. https://github.com/yarnpkg/yarn/issues/7801
Could anyone please explain this problem?
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (12 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Next step: verify that this works now
@divyenduz This issue does touch on the package size for a bit but the actual problem is different here which is yarn install all of our packages when we specify nexus-prisma as a dependency and prisma2 a devDependency in production mode. So I think we should keep this open for now.