#cssmodules — Public Fediverse posts

shadcn-css: Bản port của shadcn/ui dùng CSS Modules thay vì Tailwind. Hỗ trợ đa số component và có CLI. Tạo ra bởi nhà dev muốn dùng shadcn/ui nhưng thích CSS hơn. Dự án được maintain tích cực. #shadcnui #cssmodules #react #ui #thietkelayout #frontend #javascript

https://www.reddit.com/r/SideProject/comments/1nwhw9c/css_modules_port_of_shadcnui/

#Development #Analyses
We keep reinventing CSS · But styling was never the problem https://ilo.im/1667em

_____
#CSS #TailwindCSS #CSSinJS #CssModules #BEM #React #Svelte #VueJS #Frontend #WebDev

#Development #Analyses
We keep reinventing CSS · But styling was never the problem https://ilo.im/1667em

_____
#CSS #TailwindCSS #CSSinJS #CssModules #BEM #React #Svelte #VueJS #Frontend #WebDev

#Development #Analyses
We keep reinventing CSS · But styling was never the problem https://ilo.im/1667em

_____
#CSS #TailwindCSS #CSSinJS #CssModules #BEM #React #Svelte #VueJS #Frontend #WebDev

#Development #Analyses
We keep reinventing CSS · But styling was never the problem https://ilo.im/1667em

_____
#CSS #TailwindCSS #CSSinJS #CssModules #BEM #React #Svelte #VueJS #Frontend #WebDev

I know I've said this before, but I really hate CSS Modules.

Seriously, can it please go die in a fire?

#webdev #CSS #CSSModules

I know I've said this before, but I really hate CSS Modules.

Seriously, can it please go die in a fire?

#webdev #CSS #CSSModules

I know I've said this before, but I really hate CSS Modules.

Seriously, can it please go die in a fire?

#webdev #CSS #CSSModules

I know I've said this before, but I really hate CSS Modules.

Seriously, can it please go die in a fire?

#webdev #CSS #CSSModules

I know I've said this before, but I really hate CSS Modules.

Seriously, can it please go die in a fire?

#webdev #CSS #CSSModules

@thomasreggi Whatever happens, just don't fall in the CSS-in-JS rabbit hole. Phooie, what nonsense even is that, I mean?

Now, in regards to #JSX and #components... As long as it's the same #CSS or, perhaps, CSS and non-over-the-top #CSSModules, the transition should not take much time. One serious benefit is maintaining component styling in one file with the layout and script bindings (most of the time, it results in less split brain logic than with separate files).

@thomasreggi Whatever happens, just don't fall in the CSS-in-JS rabbit hole. Phooie, what nonsense even is that, I mean?

Now, in regards to #JSX and #components... As long as it's the same #CSS or, perhaps, CSS and non-over-the-top #CSSModules, the transition should not take much time. One serious benefit is maintaining component styling in one file with the layout and script bindings (most of the time, it results in less split brain logic than with separate files).

@thomasreggi Whatever happens, just don't fall in the CSS-in-JS rabbit hole. Phooie, what nonsense even is that, I mean?

Now, in regards to #JSX and #components... As long as it's the same #CSS or, perhaps, CSS and non-over-the-top #CSSModules, the transition should not take much time. One serious benefit is maintaining component styling in one file with the layout and script bindings (most of the time, it results in less split brain logic than with separate files).

@thomasreggi Whatever happens, just don't fall in the CSS-in-JS rabbit hole. Phooie, what nonsense even is that, I mean?

Now, in regards to #JSX and #components... As long as it's the same #CSS or, perhaps, CSS and non-over-the-top #CSSModules, the transition should not take much time. One serious benefit is maintaining component styling in one file with the layout and script bindings (most of the time, it results in less split brain logic than with separate files).

@thomasreggi Whatever happens, just don't fall in the CSS-in-JS rabbit hole. Phooie, what nonsense even is that, I mean?

Now, in regards to #JSX and #components... As long as it's the same #CSS or, perhaps, CSS and non-over-the-top #CSSModules, the transition should not take much time. One serious benefit is maintaining component styling in one file with the layout and script bindings (most of the time, it results in less split brain logic than with separate files).

With CSS nesting and `@Scope` stuff well supported at this point I am struggling to see much of a reason to continue using CSS modules.

In Next.js you can now nest selectors in a module.css file, but the only way I can see to make it not the awkward obfuscated class names is to prefix all the nested items with `:global()`. which just is kinda ick.

#nextjs #css #webdev #cssModules

With CSS nesting and `@Scope` stuff well supported at this point I am struggling to see much of a reason to continue using CSS modules.

In Next.js you can now nest selectors in a module.css file, but the only way I can see to make it not the awkward obfuscated class names is to prefix all the nested items with `:global()`. which just is kinda ick.

#nextjs #css #webdev #cssModules

With CSS nesting and `@Scope` stuff well supported at this point I am struggling to see much of a reason to continue using CSS modules.

In Next.js you can now nest selectors in a module.css file, but the only way I can see to make it not the awkward obfuscated class names is to prefix all the nested items with `:global()`. which just is kinda ick.

#nextjs #css #webdev #cssModules

With CSS nesting and `@Scope` stuff well supported at this point I am struggling to see much of a reason to continue using CSS modules.

In Next.js you can now nest selectors in a module.css file, but the only way I can see to make it not the awkward obfuscated class names is to prefix all the nested items with `:global()`. which just is kinda ick.

#nextjs #css #webdev #cssModules

With CSS nesting and `@Scope` stuff well supported at this point I am struggling to see much of a reason to continue using CSS modules.

In Next.js you can now nest selectors in a module.css file, but the only way I can see to make it not the awkward obfuscated class names is to prefix all the nested items with `:global()`. which just is kinda ick.

#nextjs #css #webdev #cssModules

Past informs the present: Our approach to CSS · The evolution of CSS and its methodologies https://ilo.im/10bo7u · by @colepeters

_____
#development #approaches
#WebDevelopment #webdev #CSS #AtomicCSS #BEM #OOCSS #CSSinJS #CSSmodules #ShadowDOM #WebStandard

Past informs the present: Our approach to CSS · The evolution of CSS and its methodologies https://ilo.im/10bo7u · by @colepeters

_____
#development #approaches
#WebDevelopment #webdev #CSS #AtomicCSS #BEM #OOCSS #CSSinJS #CSSmodules #ShadowDOM #WebStandard

Past informs the present: Our approach to CSS · The evolution of CSS and its methodologies https://ilo.im/10bo7u · by @colepeters

_____
#development #approaches
#WebDevelopment #webdev #CSS #AtomicCSS #BEM #OOCSS #CSSinJS #CSSmodules #ShadowDOM #WebStandard

Past informs the present: Our approach to CSS · The evolution of CSS and its methodologies https://ilo.im/10bo7u · by @colepeters

_____
#development #approaches
#WebDevelopment #webdev #CSS #AtomicCSS #BEM #OOCSS #CSSinJS #CSSmodules #ShadowDOM #WebStandard

Senior Web Developer - Your day-to-day will involve bridging the gap between our UX designers and back-end devs so we... Shopify / Ottawa, Canada https://startup.jobs/senior-web-developer-at-shopify-4 #Dev fullstack #React #Typescript #CSSModules #Ruby #GraphQL by @[email protected]

Senior Web Developer - Your day-to-day will involve bridging the gap between our UX designers and back-end devs so we... Shopify / Ottawa, Canada https://startup.jobs/senior-web-developer-at-shopify-4 #Dev fullstack #React #Typescript #CSSModules #Ruby #GraphQL by @[email protected]