-
Updated
Dec 27, 2019 - JavaScript
css-modules
Here are 694 public repositories matching this topic...
Creating a "epic" type of ticket to track updates to documentation wanted/needed/done.
- #410 - Update CSS Blocks Readme to be more beginner friendly.
- #411 - Create "Getting Started" guide for CSS Blocks.
- #413 - Create "Using CSS Blocks in Ember" guide.
- #414 - Split up CSS Blocks Architecture documentation into high-level vs specific.
- #TBD
-
Updated
Mar 17, 2020
react 15.6.1
react-flexbox-grid": "^1.1.4"
and i am using create-react-app
I hosted my website on Heroku
in Heroku class names of row and col changing to "flexboxgrid__col-sm-12___1e5Uk flexboxgrid__col-md-6___5OSyJ" something like this, so CSS is not applying to the dom
-
Updated
Oct 4, 2018 - CSS
tl;dr;
Use https://github.com/sharegate/craco.
Create craco.config.js:
const CSS_MODULE_LOCAL_IDENT_NAME = '[local]___[hash:base64:5]';
module.exports = {
style: {
modules: {
camelCase: true,
localIdentName: CSS_MODULE_LOCAL_IDENT_NAME
}
},
babel: {
loaderOptions: {
// Without this Babel caches module name resolution,
// e.g.-
Updated
Apr 13, 2017 - JavaScript
-
Updated
May 23, 2020 - TypeScript
-
Updated
Mar 16, 2020 - JavaScript
when using the following syntax with React 15.x
Label {}
Label:prop(mode == 'edit') {}<Label mode="edit"/>React throws the following error:
Warning: Unknown prop `mode` on <div> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop
If I understand correctly what is being said [here](https://gist.github.com/jimfb/d99e
react-native-style-tachyons calculates line-height as being in rem but in the tachyons css they are actually unitless numbers, which by css specification get multiplied to the font's computed size.
So, to give an example, if the base font size (rem) is 16px and we have:
<p class="f3 lh-copy">where
`
Docs for CRA setup
Since I watched Mark's talk, I just love your concept of elements without surrounding blank space. It's genius!
Do you have any plans on adding the docs for other setups apart from sku? I think it would be a really amazing to be able to use it with Create React App!
Now it's possible to namespace a theme by using a themeNamespace property for the component. This avoids collisions between modules of different components using the same classname. It's a feature that it's working and it's published but not documented. We need to write a section detailing the API which is very simple!
npm WARN example@1.0.0 No description
npm WARN example@1.0.0 No repository field.
npm ERR! Linux 3.13.0-83-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v7.1.0
npm ERR! npm v3.10.9
npm ERR! path /home/davidm/src/Quramy/typed-css-modules/example/node_modules/typed-css-modules/lib/cli.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall
-
Updated
Mar 7, 2017 - JavaScript
When you kickstart a project with Gatsby or CRA you actually see a demo page in a clean and simple but nice looking layout. When you start React SSR Setup after cloning the repo it just looks plain and ugly. Maybe it's time to provide a layout that's a bit nicer than the current one.
-
Updated
Apr 4, 2020 - TypeScript
-
Updated
May 25, 2020 - JavaScript
-
Updated
May 23, 2020 - JavaScript
-
Updated
Mar 19, 2020 - JavaScript
-
Updated
May 17, 2019 - JavaScript
-
Updated
May 14, 2020 - JavaScript
Create global style
Thanks for the great library!
I haven't found a solution for creating global theming in the application based on theme properties: for instance, the name of font families. (Something like this: https://www.styled-components.com/docs/api#createglobalstyle)
Does a solution with generating own globals.css from interpolated string by webpack plugin is ok? Or reshadow has something inside for r
-
Updated
Feb 20, 2019 - JavaScript
Improve this page
Add a description, image, and links to the css-modules topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the css-modules topic, visit your repo's landing page and select "manage topics."

The Input component defines an input tag along with a role attribute equal to 'input'. This causes some accessibility scanners to raise the following violation:
"The WAI-ARIA role(s) and/or attribute(s) input are not valid for the element input"
Is there a way we can remove the redundant role or at least provide a way to override the value?