You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all themes are shipped in one not-so-pico npm package: @picocss/pico at ~19Mb. This significantly slows down auto-completion/intellisense on CSS files and harms DX.
Suggestion
Distribute one npm package per theme, for example: @picocss/pico-slate, @picocss/pico-indigo, etc.
Advantages
Better DX
Better traceability, npm install >manual copy single file option
Easier plug & play than manual copy single file option
Faster/smaller builds
Horizontal scaling by theme addition might be easier to manage on your end
Better visibility as to which themes people prefer (Pareto here? 20% of the themes used 80% of the time?) helping you decide what you can discard in the future
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently, all themes are shipped in one not-so-pico npm package: @picocss/pico at ~19Mb. This significantly slows down auto-completion/intellisense on CSS files and harms DX.
Suggestion
@picocss/pico-slate
,@picocss/pico-indigo
, etc.Advantages
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions