Philzen

It may be unrelated but worth mentioning that when i run `yarn redwood upgrade -t v1.0.0-rc.final.1` on an existing project (completely different project that was created successfully with yarn 1)...

> I saw it when I had yarn files in my home directory too. I added yarn files to my home directory because I was trying to change my version...

@jtoar So i deleted / renamed all `.yarn*` files and folders from my home dir, thus successfully went back to yarn 1.22.17 and used the above corepack command to go...

OK, turns out a `~/package.json` existed that was created when i ran `yarn set version stable` in my home dir last week :facepalm: Deleted it and ... tadaaa, running `yarn...

@Tobbe This is also something that has been nagging me every now and then as well. It's strange, b/c sometimes it works fine, sometimes CTRL-Click just makes VSCode jump to...

@jtoar would need some investigation on that. But ask yourself: Did you *ever* in your life have to go into the `.yarn`-folder and do anything in there in VSCode? This...

> My concern is that this sounds like it count as adding magic to the framework. IMHO the whole RedwoodJS stack is magic ;) But i do understand your point....

I finally got around to write the requested section. This actually required some deep-dive into how config inheritance and `files.exclude` vs. `search.exclude` vs. `files.watcherExclude` works. Learned along the way (by...

@Tobbe / @jtoar: - [x] change label to `release/docs`

### Suggestion Instead of committing the yarn executable code into the repository (twice!), why not use `git submodules` and link to the yarn executable directly, or alternatively have the CRA...