bs-css

Statically typed DSL for writing css in reason.

Web Development Productivity

Explore on GitHub Read Hacker News discussions

3Distinct people

3Mentions

1Explicit recommenders

588GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

What it is

Statically typed DSL for writing css in reason.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

Hey, I recommend sticking to bs-css (https://github.com/reasonml-labs/bs-css). Not because I don't think styled-ppx is super cool or amazing, but because it's so cutting edge…

JasoonS used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2020-05-14 07:20:31 UTC to 2020-07-23 22:20:31 UTC. Weeks start Monday, UTC.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
May 11	2020-05-11 00:00:00 UTC	2020-05-18 00:00:00 UTC	1	1
May 18	2020-05-18 00:00:00 UTC	2020-05-25 00:00:00 UTC	0	0
May 25	2020-05-25 00:00:00 UTC	2020-06-01 00:00:00 UTC	0	0
Jun 1	2020-06-01 00:00:00 UTC	2020-06-08 00:00:00 UTC	0	0
Jun 8	2020-06-08 00:00:00 UTC	2020-06-15 00:00:00 UTC	0	0
Jun 15	2020-06-15 00:00:00 UTC	2020-06-22 00:00:00 UTC	0	0
Jun 22	2020-06-22 00:00:00 UTC	2020-06-29 00:00:00 UTC	0	0
Jun 29	2020-06-29 00:00:00 UTC	2020-07-06 00:00:00 UTC	0	0
Jul 6	2020-07-06 00:00:00 UTC	2020-07-13 00:00:00 UTC	0	0
Jul 13	2020-07-13 00:00:00 UTC	2020-07-20 00:00:00 UTC	0	0
Jul 20	2020-07-20 00:00:00 UTC	2020-07-27 00:00:00 UTC	2	2

What Hacker News says

3 sources

ronanyeah·Jul 23, 2020

Some help can be found with typed CSS: https://package.elm-lang.org/packages/rtfeldman/elm-css/late... https://github.com/reasonml-labs/bs-css Or even a typed alternative to/subset of CSS: https://package.elm-lang.org/packages/mdgriffith/elm-ui/late...

In Why is CSS the way it is?

hardwaregeek·Jul 23, 2020

I was trying to articulate why CSS is so unpleasant for me. I've learned enough tricks and techniques to tolerate it, but there's still plenty of times where I despise it. There's a few glaring issues: - No way to style according to siblings. This is a big mental model shift. Often times I want a div to be the same height as another div. Since CSS doesn't really allow sibling communication, I need to get the parent div to set the height and then tell the children to play along. Or manually set the height on both children. - Error handling is so so bad. It sucks to have your styles break silently due to an errant comma or space. Well typed styles like bs-css[^1] have made this somewhat tolerable. - The weird tug of war between positioning yourself versus positioning your child. I understand the reason for both but it's offputting having bo

Read the rest

th as an option. - Lack of z index positioning. Often I want to superimpose one element on another, say a caption on an image. Right now I need to resort to position absolute, then do the standard dance to center something by computing 50% + half the size of the overlayed element. Not fun. I'd love a flex-direction: into-page that does flexbox over the third dimension. It'd be a little tricky to understand but honestly not too bad. What's weird is that in some ways these issues have gotten worse with components. Since I can reuse a component, I now need to think of how its styles will work in every usecase. For instance I had forgotten to set my component's background to white, since it was already white by default. When I moved the component to a blue background, boom, it became garishly blue. Of course this is my bad, but it sucks that we have to carefully engineer our styles such that moving a component into a new context won't screw it up. [^1]: https://github.com/reasonml-labs/bs-css

In Why is CSS the way it is?

JasoonS·May 14, 2020Recommendation phrase

Hey, I recommend sticking to bs-css (https://github.com/reasonml-labs/bs-css). Not because I don't think styled-ppx is super cool or amazing, but because it's so cutting edge your 99% chance going to run into an edge case that isn't well accounted for yet (I had a number of issues when I tried it). bs-css is battle tested today, so if you're goal is stability, I recommend it first.

In Reason React 0.8