Shipping dist is obviously super undesirable; it is what's recommended for GitHub-based deploys and other packages, somehow, also ship dist (looking at you, Markdoc).
What we actually want, since these components are only ever used in Next.js deploys, is to incorporate building them as part of the Webpack builds of those websites, and ship source-only. This goes against the package being generalised, but it makes for a far better workflow at the cost of some setup for new sites (we could just start shipping next.js configs, though).
Shipping
distis obviously super undesirable; it is what's recommended for GitHub-based deploys and other packages, somehow, also shipdist(looking at you, Markdoc).What we actually want, since these components are only ever used in Next.js deploys, is to incorporate building them as part of the Webpack builds of those websites, and ship source-only. This goes against the package being generalised, but it makes for a far better workflow at the cost of some setup for new sites (we could just start shipping next.js configs, though).