Unfortunately, we don’t have any experience combining Polylith with Stuart Sierra’s Component framework, so what follows is pure conjecture on my part.
After reading the documentation for Component, I’m concerned that the two ideas might not play very nicely together. Component is very opinionated about the structure of your application’s code, but so is Polylith. The two structures are quite different, and are driven by two different goals.
If a reloaded workflow is your main goal, and you’re satisfied with the current structure of your architecture, then I’d recommend sticking with Component.
If Polylith’s simplicity, “pure” functional, and encapsulated components approach appeals to you, then I’d recommend to start using it without a reloaded workflow. We’ve built many systems that way, and haven’t become frustrated with our REPL-driven workflow in the slightest.
If you do switch to Polylith and figure out a new approach to combine it with a reloaded workflow (or how to successfully marry Polylith with Component), then we’d be very excited to hear about it!
Good luck with your project!