transpilePackages with tailwind
Answered
Narcissus Flycatcher posted this in #help-forum
Narcissus FlycatcherOP
Did someone had positive experiance with that?
I'm using a monorepo setup with
Currently Tailwind classes set up in the
I'm using a monorepo setup with
apps/app-a and packages/ui both using TailwindCSS in them. packages/ui is just a bunch of React Components. Currently Tailwind classes set up in the
ui package, does not have any effect on the Component appearance when it used in the app-a...Answered by Narcissus Flycatcher
I thought that
Anyways, looks like I found the problem I had. It was the paths in the
transpilePackages is needed exactly for using another local package in the next.js, without need to build the package and import already built esm modules in the app... So if I use say, lodash in ui package it gets transpiled with app-a 's next js. Anyways, looks like I found the problem I had. It was the paths in the
tailwing.config.js. Thanks anyway!!3 Replies
i thought you don't need transpilePackages because tailwind just generates CSS?
and you can customise the files that tailwind checks to get the classes used (with the content option)
@riský i thought you don't need transpilePackages because tailwind just generates CSS?
Narcissus FlycatcherOP
I thought that
Anyways, looks like I found the problem I had. It was the paths in the
transpilePackages is needed exactly for using another local package in the next.js, without need to build the package and import already built esm modules in the app... So if I use say, lodash in ui package it gets transpiled with app-a 's next js. Anyways, looks like I found the problem I had. It was the paths in the
tailwing.config.js. Thanks anyway!!Answer