Panda CSS: build time and type-safe CSS-in-JS

Re:Panda CSS: build time and type-safe CSS-in-JS by cjpearson on Tuesday February 06, 2024 @02:32AM (#39271805)

I don't disagree with the main point here, but the dev-dependencies won't be installed or run on your machine unless you're building Tailwind or Panda itself. They're not necessary for processing the CSS.

[ Parent | on HN ]

Re:Panda CSS: build time and type-safe CSS-in-JS by christophilus on Tuesday February 06, 2024 @07:53AM (#39273666)

I know, but there’s something about having many hundreds / thousands of dev dependencies that seems like a signal of mindset.

How much do they care about simplicity, bloat, efficiency, security? The number of dependencies is a signal. Maybe not an important one, though.

[ Parent | on HN ]

Re:Panda CSS: build time and type-safe CSS-in-JS by SeriousStorm on Tuesday February 06, 2024 @10:28AM (#39275262)

None of Tailwind's dependencies ship to your production app. Tailwind is a CSS build system (mostly) so when you build for prod, the only thing that ships to prod is a CSS file.

[ Parent | on HN ]

Re:Panda CSS: build time and type-safe CSS-in-JS by charrondev on Tuesday February 06, 2024 @10:35AM (#39275400)

Is there a way to install only your own dev dependencies?

As far as I can tell installing a package will also pull down all of its dev dependencies. This unfortunately leads to many typescript related annoyances such as jest typescript global types being pulled in despite not needing them.

[ Parent | on HN ]