One answer is that we are all using military technology. The internet was first called ARPAnet, developed by DARPA as a military system. As many other technologies before. Then people found an everyday life application. Like the one we are on now. My guess is that is why. They see the application

Hi! 😀

Hi! 😀

🤣 And did you ever use it in a Next.js and unit tested while importing ANOTHER app from your mono - an ESM/CJS UI library built with `tsc`?

THAT is a lot of fun to configure with Jest! 😀

Hi! 😀

Hi! 😀

--no-verify?? 🤣

Our experience? We don't overthink it. Both options are good. We choose one approach, keep an eye on it early-days so if it appears the other option suits our codebase better we can switch quick and we don't need to move around too many things 🤣

For types to export no-brainer. For types internal to a package... the way we do it is look at 2 options:

* keep it in the file where it is needed first and then from other files do import { HomeVideoReview } from "components/HomeVideoReview"
* keep it in "/types" if it is reused A LOT 😀

For our UI libraries in our mono? We declare Typescript interfaces in each file. We export the ones we need on other packages and build at build time

That way for the other packages - say a Next.js frontend - we just import { Carousel } from "@bluframe/site-ui" and we have our type available for us