-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong css dependency files folder location #18
Comments
I was trying to find some time to fix this by rewriting the css into inline styles, making it completely componentized. I'll eventually get around to doing this, I just haven't found opportunity for it. I'll just fix the documentation for now, and keep this issue open for sake of remembering it. Thanks @rfviolato |
Awesome! No problem ;) |
@JohnyDays Have you looked in to "Aphrodite-CSS"? It's basically the best Inline-styles/react paradigm way to style your components. I would love to help you get this started if you'd like. |
I've looked at aphrodite and glamor, and I seem to like glamor's approach more, but Aphrodite does seem more simple and straightforward to distribute for libs |
@JohnyDays I'll have to look into Glamor this is the first I have heard of it. I do like Aphrodite for those same reasons. Also you can gain specificity preference really easily being that it injects a component specific style sheet per component. This is HUGE in that you're not actually writing inline styles, the styles simply get injected in the "Head" of the document as the component is mounted. That is brilliant IMO. But I'll look into glamor. I do agree though, this component would be +100 if we could non-trivially add our own styles independently. For now, I'm just tweaking the given styles as I've added them to my global stylesheet. |
Hi! First of all, really nice component 👍
I just npm installed it and the two mentioned css dependency files are not located inside
build/
folder as stated on README.md, but i could import them anyway because they are located atsource/
folder.I guess that is not correct, because
source/
folder contain uncompressed files.The text was updated successfully, but these errors were encountered: