Working list of next steps

[jtoar]

This repo is mostly in a workable state in that you can run build, lint, and test. Here's a few more things we'd like to do:

• add some kind of integration or e2e test(s) on a redwood app fixture
• set up renovate
• do we have to be more strict about peerDeps? I.e. these packages work with these versions of redwood
• publishing needs to be set up

[thedavidprice]

I'm really missing yarn's support for package.json engines right now. But according the the docs for peerDeps, that could be a solution for version compatibility — how and when will yarn fail if peerDeps aren't met; is the output understandable and can we run a check at time of setup installation?

We also need to decide how to version this package:

• Do we start at 1.0? (we're going to run into conflicts if so when we get to v4 'cause we've already been publishing at v4)
• What if this package a) syncs it's semver major with Redwood version compatibiility and b) runs semver minor and patch independently? (downside is that we'll need to re-publish all stand-alone packages with each Redwood major)

I think we have to start at 1.0 and find a way to archive previous versions.