Awesome!

Should we keep using yarn link for middleware packages ? That seems easier since we don't have to bother about watching and publishing.

Agree with that.

I tried to centralize the config so that the parcel dev dep is only in the workspace dev dependencies. This works fine. The only thing I didn't manage to get working for some reason is to use nx watch, to watch the whole workspace for file modifiactions. It just wouldn't trigger on file changes. Nodemon is fine though and I can set that up. Since the frontend root build script uses nx now, this will only rebuilt changed packages.

Also, I removed the yalc:publish since this will not be necessary, when yalc is called after each build or branch change, or did I oversee something?

Will add the git hook later tonight.

Great, thank you !

The only thing I didn't manage to get working for some reason is to use nx watch, to watch the whole workspace for file modifiactions.

Too bad. But from my experience, it's pretty rare I need to watch all frontend packages at the same time. Usually one or two is enough.

Also, I removed the yalc:publish since this will not be necessary, when yalc is called after each build or branch change, or did I oversee something?

The case I could see is on a fresh git clone: you don't need to do the build (packages are already built), but you need the yalc publish. However if this can be automated with the git hooks, it probably won't be needed.

The case I could see is on a fresh git clone: you don't need to do the build (packages are already built), but you need the yalc publish. However if this can be automated with the git hooks, it probably won't be needed.

My bad, that's the scenario that'd be useful to have the script for, I suppose :D

Thanks, the git hooks are working great !
I'm merging this now, I've also updated the docs on ActivityPods here: activitypods/activitypods@ff91a81 (this can be copy-pasted on any other repo)