DEV Community

loading...

Discussion on: The Breakpoint CSS-JS "Hack" - do not define breakpoints in JS

Collapse
pankajpatel profile image
Pankaj Patel

This is really a neat trick. Thanks for sharing.

There is possible rink to expose these MQ texts to user.

Though I would only suggest this approach if you are not using any bundler for your project and delivering JS project.

I would suggest to keep breakpoints in JS file and provide the breakpoints' value to CSS with PostCSS or SCSS during the transpiling process.

Collapse
activenode profile image
David Lorenz Author

Actually, since CSS is the SSOT for UI/Design it is recommended architecturally to keep it in SCSS.

Using a bundler however you can also do it the other way round and import ... scss values within JS .

Collapse
pankajpatel profile image
Pankaj Patel

I agree with SSOT being in CSS

But getting values is readable format from CSS to JS is hacky and that's why making JS as SSOT for Breakpoints seems like a sane approach which doesn't involve custom solutions to maintain SSOT.

When creating Design Systems, there are more values which you might wanna share between CSS and JS contexts and for that reason JS seems to be a better place for such values.

I am not sure about the ease or possibility of importing values from scss via import, maybe you can point me to such resource 🧐

Thread Thread
activenode profile image
David Lorenz Author

Thanks for pointing that out. Sure thing I can try to make a super quick post about that ASAP :) will get back to you