in my opinion, a small collection of core services is better than a monolith or a large collection of tiny services
Somtimes it makes sense to have multiple services live in a single "monorepo" for shared tooling and other resources. 1 repo, deployed to multiple places for different purposes.
My initial response to the team when I heard the proposal was that programming is an art form. There is a beauty how software is organized and orchestrated.
Given that the microservices do very different things, combining them together will do nothing but clutter a the code base. JS gives an excellent module system which allows for maximum code reuse. That should be emphasized. But combining 6 code bases together into a project that is planning to expand extensively over the next year makes little to no sense at least to me.