No description provided.
CSS modules support for TypeScript
CSS modules shareable config for stylelint
TypeScript definitions for css-modules
Storybook CSS Modules preset
Creates .d.ts files from CSS Modules .css files
A require hook to compile CSS Modules on the fly
A loader-agnostic CSS Modules implementation, based on PostCSS
A CSS Modules transform to make local scope the default
Vite plugin for correct CSS Modules behavior
A CSS Modules transform to extract local aliases for inline imports
PostCSS plugin to use CSS Modules everywhere
TypeScript definitions for css-modules-require-hook
CSS Modules for ambitious applications
A CSS Modules transform to extract export statements from local-scope classes
Webpack loader to create TypeScript declarations for CSS Modules
Extended ruleset for stylelint on CSS modules
Creates .d.ts files from CSS Modules .css files
A broccoli plugin for compiling CSS modules
PostCSS plugin for CSS Modules to pass arbitrary values between your module files
The core of css-modules-kit
A [SWC](https://swc.rs) plugin to use [CSS Modules](https://github.com/css-modules/css-modules).
A esbuild plugin to bundle css modules into js(x)/ts(x), based on extremely fast [Lightning CSS](https://lightningcss.dev/)
@umijs/babel-plugin-auto-css-modules
CSS Modules with a macro for convenience.
Parser and CSS Modules intermediate extractor for Omena CSS analysis
Rust LSP server boundary and multi-editor runtime for Omena
Rust tsgo client boundary for Omena source-side type facts
Scoped CSS for rust projects
Cli tool for bundling stylance scoped CSS files.
CSS Modules with a macro for convenience.
CSS modules
Provides a css-module-like experience to Sass/SCSS, Rails views and JavaScript
Inspired by the css in js component, it provides functionality to allow the same component-by-component implementation of styles in rails' standard component, view_components.
"Attribute Modules (AM) is a technique for using HTML attributes and their values rather than classes for styling elements."
Module for ActionMailer to improve the rendering of HTML emails by using the 'premailer' gem, which inlines CSS and makes relative links absolute.
Set of classes and modules for creating HTML helpers
style_train builds CSS using pure Ruby, not a DSL interpreted via Ruby. This allows inheritance, modules, instance level calculations and all the goodness Ruby can offer.
Provides component-scoped CSS encapsulation using [data-capsule] attributes for Phlex components, ViewComponent components, and ERB templates. Styles are automatically scoped to prevent leakage between components. Inspired by component-based CSS approaches like Angular's view encapsulation and CSS modules. Works with Rails and can be used standalone in other Ruby frameworks (Sinatra, Hanami, etc.) or plain Ruby scripts.
Partials FX extends Rails' partials to make them quack more like components. Each partial, located in app/views/components/, is backed by a Ruby class with the same name. It also supports CSS modules, meaning you define CSS in the component class and it gets “scoped” to that component only.
Kit is DSC's Community and Content Management System (CCMS) built as a Rails engine for Rails 3.1 and above. It provides an entire application's worth of CMS functions including in-place WYSIWYG editing with versioning, flexible layouts and templates, CSS and JS all managed within your browser, drag and drop image/file uploading, modules for sophisticated forums (with in place moderation) asset management, calendars, advertising, menus, RSS feeds, re-useable components, full audit trail of editing, integration with mailchimp, Google Analytics and lots more.
<p>Sass or the much better approach of scss is really helpful and a big silver bullet for my css structuring in ruby projects.</p> \ <p>Standard sass command works for whole directories or single files only. In general it gets the jobs we want done, but in practical usage i think the sass command tool is a little bit unconvinient. A common scenario for me is, \ that you have whole bunch of sass files, which you want to compile to a single compressed output file. But if you have splitted your sass files in component based modules and you want to watch the complete folder you have to care for dependency handling in each file, because each file will be compiled for its own.</p> \ <pre># compiling a complete folder with scss ~ $ sass css/scss:css/compiled</pre> \ <p>So converting the whole folder is not what i want, because i don\'t want to import for example my color.sass config file in each module again. Compiling a single file seems to be the better solution, and it works in general, as expected, but the devil is in the detail. </p> <pre># compiling a single file where the other files are imported. ~ $ sass css/scss/main.scss:css/compiled/main.css</pre> \ <p>If we change a file with impact to our main.sass file, the --watch handle will not get it, because it observes only the timestamp of the given main.sass.</p> <p>Here is it, where mindful_sass tries to help out. You use it according to the single file variant of sass, but it tries to observe the whole folder the given sass file is placed. If a timestamp of file in the sass folder or its children changes it will compile the specified main.sass again.</p> \ <p>This gem is not aimed to replace anything in the sass universe. It is only a wrapper to avoid the described unconvinience, and i hope that it gets useless as fast as possible, because the sass development gets this feature done for themselves.</p> \ <p>Thanks anyway to the sass developer team.</p>
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.