redwood: [FAQ] `yarn rw link` tracking issues and common problems for contributing
Creating this issue to highlight commonly faced issues, and suggested solutions, when trying to to contribute using yarn rwt link
If you find an issue, please comment here - and please include if you found a way around the problem as well. The purpose of this issue being a reference, so you can get on with contributing 🚀
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 3
- Comments: 15 (8 by maintainers)
Issue
Yarn install fails during rwt link with the error:
xxxcould be a handful of modules - but commonly@babel/cli.This does not happen in all projects, but can happen, typically after an upgrade.
Solution
This is a very painful bug within yarn, and something to do wth yarn’s resolution strategy 🤷. See here: https://github.com/yarnpkg/yarn/issues/7807
Step 1: Remove all node_modules
Step 2: Set yarn policy to 1.18
Step 3: Reinstall node_modules
Step 4: Undo the policy change
Step 5: Re run link
rwt linkfails due to type issueSolution
This happens when the prisma types go out of sync for some reason.
Steps to resolve:
git pull origin mainYou should be able to run
rwt linksuccessfully on your project again nowThe issue is resolved by running in both
redwoodjs/redwoodandmy-rr-appfolders thenyarnagainIt’s just that the paths we link to has changed. It won’t be an issue if your project is v0.34 or higher
Hey @LBrian, this is likely due to the structural changes we’re making to redwood at the moment. Steps to try and fix:
Assuming you’ve pulled main, and done a yarn install in the redwood folder:
eslint-redwood-pluginfolder in your packages/ folder (in the framework repo)Issue
node-gyp-build,yarn install --pure-lockfile --check-filesfailed:Solution
Install
node-gyp-buildglobally: