Solito as DS/UI package for Microservices #523

[murilomattioli]

Context

I’m currently testing Solito + Tailwind in a setup with multiple microservices (Next.js and React Native).

Problem

While trying to extract the shared components/screens/providers into a standalone package, I ran into several issues:

• Dependency management: conflicts between Yarn Berry and Yarn Classic, inconsistent lockfiles, and .npmrc / .yarnrc misconfigurations.
• Package publishing: incorrect publishConfig, authentication issues with Verdaccio, and version conflicts across workspaces.
• Monorepo complexity: module resolution problems and TypeScript path configuration across multiple packages.

Discussion

Would it be possible (or supported) to use Solito’s shared components structure as a standalone library — published as an npm package — to be consumed by independent microservices built with React Native or Next.js?

The goal is to centralize UI, screens, and providers in a single shared package without depending on a monorepo setup.