Consider creating separate modules for library and CLI #48
Description
Even if a consuming library/project only uses this package programmatically (i.e. no CLI usage), all of the CLI-specific deps are still pulled in and added to the consumer's deps graph unnecessarily, adding significant installation and maintenance overhead.
Ideally, the programmatic API is implemented as a separate package and the CLI then uses that package for its needs and published separately. While this creates the relatively small overhead of managing two projects, it results in a massive improvement for the consuming experience.
For example, @comapeo/core only uses the programmatic API but anything that uses @comapeo/core will be pulling in deps that are related to the CLI functionality of styled-map-package, which is currently non-trivial: