By Common Tooling I refer to all tooling features that can be shared and reused by UNREPL clients.
In slack @pesterhazy and I were discussing on the best way to accommodate for this. Current options on the table are:
- Mono repo: React style, they have
react, react-server, react-dom, ... all in the same REPL.
- Separate repo: each client would be responsible to consume this repo, either by including it as a jar file or as a submodule/subtree.
Currently we lean to the second option. This repo/library should be as thin as possible in term of dependencies.
Dependencies should be 'shaded' at build/release time with something like MrAnderson (see also Unrepl/unravel#64)
Clients may also have to shade their inclusion of this library.
By Common Tooling I refer to all tooling features that can be shared and reused by UNREPL clients.
In slack @pesterhazy and I were discussing on the best way to accommodate for this. Current options on the table are:
react,react-server,react-dom, ... all in the same REPL.Currently we lean to the second option. This repo/library should be as thin as possible in term of dependencies.
Dependencies should be 'shaded' at build/release time with something like MrAnderson (see also Unrepl/unravel#64)
Clients may also have to shade their inclusion of this library.