Build step for monorepo package
Hello,
i got a question regarding private packages in monorepos.
When should private packages have a build step VS using ts path alias eg
i am currently having a build step, and i am thinking of removing it.
then i would have to some changes to our tailwind config, so that the tailwind classes are getting bundled correctly.
are their any trade offs or other experiences?
our current setup:
- 4 apps (api, website, customer ,admin)
- 2 packages (ui, lib)
- lib containing shared TS and config stuff for bussiness logik so it can be used for all websites
- ui classic shared UI components (useing tailwind, want to also add shadcn/ui stuff)
i got a question regarding private packages in monorepos.
When should private packages have a build step VS using ts path alias eg
@ui/**: ../../packages/ui/**i am currently having a build step, and i am thinking of removing it.
then i would have to some changes to our tailwind config, so that the tailwind classes are getting bundled correctly.
are their any trade offs or other experiences?
our current setup:
- 4 apps (api, website, customer ,admin)
- 2 packages (ui, lib)
- lib containing shared TS and config stuff for bussiness logik so it can be used for all websites
- ui classic shared UI components (useing tailwind, want to also add shadcn/ui stuff)
