Publish components seperately

nostalgic-css / NES.css

NES-style CSS Framework | ファミコン風CSSフレームワーク

https://nostalgic-css.github.io/NES.css/

MIT License

20.56k stars 1.64k forks source link

Publish components seperately #346

Closed StefanNieuwenhuis closed 5 years ago

StefanNieuwenhuis commented 5 years ago

Describe the solution you'd like I want to create a components library with Web Components, that's based on NES.css, but now I have to load the complete library into every component, which is not optimal and results in bulky packages. I would like to see that all components are published as separate (scoped) packages.

Describe alternatives you've considered Include the complete NES.css library into every component I create.

BcRikko commented 5 years ago

I want to create a components library with Web Components, that's based on NES.css

Thanks 👍

We publish the two files. 📦

nes-core.css (nes-core.min.css)
- only component styles
- about 50KB
nes.css (nes.min.css)
- included pixel icons and pixel arts.
- about 280KB

If you use scss, you can import components like @import "~nes.css/scss/elements/buttons.scss";. 🤔

StefanNieuwenhuis commented 5 years ago

I'm gonna try it out! Thanks.

BcRikko commented 5 years ago

ref https://github.com/nostalgic-css/NES.css/issues/284#issuecomment-514523964