Closed MichalBryxi closed 1 year ago
I think it's worth a separate tailwind implementation, maybe called tailwind-webpack
.
I think there is still a lot of value in using the simpler tailwind-CLI approach because it can survive packager-changes (webpack vs vite vs broccoli, etc).
Just noticed that Tailwind has official documentation for EmberJS. Would it make sense to update the script for tailwind here to match?
One thing that I noticed is that it somehow hooks things together so it's not necessary to spawn the
pnpm run tailwind:watch
in separate terminal. Which is nice.