Top Related Projects
CSS Loader
Compiles Sass to CSS
Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
👩🎤 CSS-in-JS library designed for high performance style composition
Documentation about css-modules
Quick Overview
The style-loader
is a webpack module that injects CSS into the DOM. It is typically used in conjunction with the css-loader
to process CSS files imported into JavaScript modules.
Pros
- Dynamic Injection: The
style-loader
can dynamically inject CSS styles into the document, allowing for more flexibility and control over the styling process. - Hot Module Replacement (HMR): The loader supports Hot Module Replacement, which enables live updates of CSS changes without a full page refresh.
- Modular Approach: By integrating the CSS loading process into the webpack workflow, the
style-loader
promotes a modular and maintainable approach to styling. - Customizable Behavior: The loader offers various configuration options, allowing developers to customize its behavior to fit their specific needs.
Cons
- Increased Complexity: Integrating the
style-loader
into a webpack-based project can add some complexity to the build process, especially for developers new to webpack. - Performance Considerations: Dynamically injecting CSS into the DOM can have performance implications, especially for large or complex stylesheets.
- Limited Functionality: The
style-loader
is primarily focused on the task of injecting CSS into the DOM and may not provide advanced styling features or functionality. - Dependency on webpack: The
style-loader
is tightly coupled with the webpack build system, which means it may not be suitable for projects that do not use webpack.
Code Examples
Here are a few examples of how to use the style-loader
in a webpack-based project:
- Basic Usage:
// webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/,
use: ['style-loader', 'css-loader']
}
]
}
}
- Customizing the Injection Method:
// webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/,
use: [
{ loader: 'style-loader', options: { injectType: 'styleTag' } },
'css-loader'
]
}
]
}
}
- Enabling Hot Module Replacement (HMR):
// webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/,
use: [
{ loader: 'style-loader', options: { hmr: true } },
'css-loader'
]
}
]
},
devServer: {
hot: true
}
}
- Extracting CSS to a Separate File:
// webpack.config.js
const MiniCssExtractPlugin = require('mini-css-extract-plugin');
module.exports = {
module: {
rules: [
{
test: /\.css$/,
use: [
MiniCssExtractPlugin.loader,
'css-loader'
]
}
]
},
plugins: [
new MiniCssExtractPlugin()
]
}
Getting Started
To get started with the style-loader
in a webpack-based project, follow these steps:
- Install the
style-loader
andcss-loader
packages:
npm install --save-dev style-loader css-loader
- Configure the loaders in your
webpack.config.js
file:
module.exports = {
module: {
rules: [
{
test: /\.css$/,
use: ['style-loader', 'css-loader']
}
]
}
}
- Import your CSS files in your JavaScript modules:
import './styles.css';
-
(Optional) Customize the
style-loader
options, such as the injection method or enabling Hot Module Replacement (HMR), as shown in the code examples above. -
Run your webpack build process and enjoy the dynamic CSS injection
Competitor Comparisons
CSS Loader
Pros of css-loader
- Processes CSS files, handling imports and url() references
- Enables modular CSS with support for CSS Modules
- Provides more granular control over CSS processing and optimization
Cons of css-loader
- Requires additional configuration for injecting styles into the DOM
- May need to be used in conjunction with other loaders for full functionality
- Slightly more complex setup compared to style-loader
Code Comparison
css-loader:
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: ["css-loader"],
},
],
},
};
style-loader:
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: ["style-loader", "css-loader"],
},
],
},
};
Key Differences
- css-loader processes and resolves CSS files, while style-loader injects styles into the DOM
- css-loader is often used in combination with style-loader or other loaders for complete CSS handling
- style-loader provides a simpler setup for basic use cases, while css-loader offers more advanced features and flexibility
Use Cases
- Use css-loader when you need to process CSS files without injecting them into the DOM
- Use style-loader in conjunction with css-loader for a complete solution that processes and injects styles
- Choose css-loader for more complex CSS processing needs, such as working with CSS Modules or optimizing CSS output
Compiles Sass to CSS
Pros of sass-loader
- Compiles Sass/SCSS to CSS, enabling the use of Sass features
- Supports source maps for easier debugging
- Integrates with other loaders like postcss-loader for additional processing
Cons of sass-loader
- Requires additional dependencies (Node Sass or Dart Sass)
- Slightly more complex configuration compared to style-loader
- May increase build time due to Sass compilation
Code Comparison
sass-loader:
module.exports = {
module: {
rules: [
{
test: /\.scss$/,
use: ['style-loader', 'css-loader', 'sass-loader']
}
]
}
};
style-loader:
module.exports = {
module: {
rules: [
{
test: /\.css$/,
use: ['style-loader', 'css-loader']
}
]
}
};
Key Differences
- sass-loader processes Sass/SCSS files, while style-loader injects CSS into the DOM
- sass-loader is typically used in conjunction with style-loader and css-loader
- style-loader is more lightweight and focused on CSS injection, while sass-loader adds Sass compilation capabilities
Use Cases
- Use sass-loader when working with Sass/SCSS files and requiring Sass features
- Use style-loader when you only need to inject plain CSS into the DOM without Sass compilation
Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
Pros of styled-components
- Allows for dynamic styling based on props and theme
- Eliminates the need for separate CSS files, keeping styles and components together
- Provides automatic vendor prefixing and unique class names to avoid conflicts
Cons of styled-components
- Increases bundle size due to the additional JavaScript required
- May have a steeper learning curve for developers used to traditional CSS
- Can make it harder to share styles across different projects or frameworks
Code Comparison
styled-components:
const Button = styled.button`
background-color: ${props => props.primary ? 'blue' : 'white'};
color: ${props => props.primary ? 'white' : 'blue'};
padding: 10px 20px;
`;
style-loader (with CSS):
.button {
background-color: white;
color: blue;
padding: 10px 20px;
}
.button.primary {
background-color: blue;
color: white;
}
Summary
styled-components offers a more integrated approach to styling React components, with the ability to create dynamic styles based on props. However, it comes with a larger bundle size and potential learning curve. style-loader, on the other hand, allows for more traditional CSS usage but requires separate files and doesn't provide the same level of component-specific styling capabilities.
👩🎤 CSS-in-JS library designed for high performance style composition
Pros of emotion
- Offers a more powerful and flexible CSS-in-JS solution
- Provides better performance through optimized runtime and compilation
- Supports server-side rendering out of the box
Cons of emotion
- Steeper learning curve for developers new to CSS-in-JS
- Requires additional setup and configuration compared to traditional CSS approaches
Code Comparison
emotion:
import { css } from '@emotion/react'
const style = css`
color: hotpink;
`
const SomeComponent = ({ children }) => (
<div css={style}>
{children}
</div>
)
style-loader:
import styles from './styles.css'
const SomeComponent = ({ children }) => (
<div className={styles.someClass}>
{children}
</div>
)
Summary
emotion is a powerful CSS-in-JS library that offers more flexibility and performance optimizations compared to style-loader. It allows for dynamic styling and better integration with React components. However, it may require more setup and has a steeper learning curve.
style-loader, on the other hand, is a simpler solution that works well with traditional CSS files and webpack. It's easier to adopt for teams familiar with standard CSS practices but lacks some of the advanced features and runtime optimizations provided by emotion.
The choice between the two depends on project requirements, team expertise, and desired level of CSS integration with JavaScript.
Documentation about css-modules
Pros of css-modules
- Provides local scope for CSS classes, preventing naming conflicts
- Allows for more modular and reusable CSS
- Supports composition for better code organization
Cons of css-modules
- Requires additional setup and configuration
- May have a steeper learning curve for developers new to the concept
- Limited browser support without build tools
Code Comparison
css-modules:
.button {
color: green;
}
.buttonDanger {
composes: button;
color: red;
}
style-loader:
.button {
color: green;
}
.button-danger {
color: red;
}
Key Differences
- css-modules focuses on modular, scoped CSS with composition
- style-loader is primarily for injecting CSS into the DOM
- css-modules requires additional processing, while style-loader is more straightforward
- css-modules provides better encapsulation and prevents global namespace pollution
Use Cases
- css-modules: Large-scale applications with complex CSS structures
- style-loader: Simpler projects or when quick CSS injection is needed
Integration
- css-modules often requires additional loaders and plugins
- style-loader can be used directly with webpack
Community and Ecosystem
- css-modules has a dedicated community and various tools built around it
- style-loader is part of the webpack ecosystem and widely used in many projects
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
style-loader
Inject CSS into the DOM.
Getting Started
To begin, you'll need to install style-loader
:
npm install --save-dev style-loader
or
yarn add -D style-loader
or
pnpm add -D style-loader
It's recommended to combine style-loader
with the css-loader
Then add the loader to your webpack
config. For example:
style.css
body {
background: green;
}
component.js
import "./style.css";
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: ["style-loader", "css-loader"],
},
],
},
};
Security Warning
This loader is primarily meant for development. The default settings are not safe for production environments. See the recommended example configuration and the section on nonces for details.
Options
injectType
Type:
type injectType =
| "styleTag"
| "singletonStyleTag"
| "autoStyleTag"
| "lazyStyleTag"
| "lazySingletonStyleTag"
| "lazyAutoStyleTag"
| "linkTag";
Default: styleTag
Allows to setup how styles will be injected into the DOM.
Possible values:
styleTag
Automatically injects styles into the DOM using multiple <style></style>
. It is default behaviour.
component.js
import "./styles.css";
Example with Locals (CSS Modules):
component-with-css-modules.js
import * as styles from "./styles.css";
const divElement = document.createElement("div");
divElement.className = styles["my-class"];
All local variables (class names) are exported as named exports. To achieve this behaviour you also have to setup modules
option for css-loader
. For more information consult with css-loader
documentation
.
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
// The `injectType` option can be avoided because it is default behaviour
{ loader: "style-loader", options: { injectType: "styleTag" } },
{
loader: "css-loader",
// Uncomment it if you want to use CSS modules
// options: { modules: true }
},
],
},
],
},
};
The loader inject styles like:
<style>
.foo {
color: red;
}
</style>
<style>
.bar {
color: blue;
}
</style>
singletonStyleTag
Automatically injects styles into the DOM using one <style></style>
.
[!WARNING]
Source maps do not work.
component.js
import "./styles.css";
component-with-css-modules.js
import * as styles from "./styles.css";
const divElement = document.createElement("div");
divElement.className = styles["my-class"];
All local variables (class names) are exported as named exports. To achieve this behaviour you also have to setup modules
option for css-loader
. For more information consult with css-loader
documentation
.
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
{
loader: "style-loader",
options: { injectType: "singletonStyleTag" },
},
{
loader: "css-loader",
// Uncomment it if you want to use CSS modules
// options: { modules: true }
},
],
},
],
},
};
The loader inject styles like:
<style>
.foo {
color: red;
}
.bar {
color: blue;
}
</style>
autoStyleTag
Works the same as a styleTag
, but if the code is executed in IE6-9, turns on the singletonStyleTag
mode.
lazyStyleTag
Injects styles into the DOM using multiple <style></style>
on demand.
We recommend following .lazy.css
naming convention for lazy styles and the .css
for basic style-loader
usage (similar to other file types, i.e. .lazy.less
and .less
).
When you lazyStyleTag
value the style-loader
injects the styles lazily making them useable on-demand via style.use()
/ style.unuse()
.
â ï¸ Behavior is undefined when
unuse
is called more often thanuse
. Don't do that.
component.js
import styles from "./styles.lazy.css";
styles.use();
// For removing styles you can use
// styles.unuse();
component-with-css-modules.js
import styles, { "my-class" as myClass } from "./styles.lazy.css";
styles.use();
const divElement = document.createElement("div");
divElement.className = myClass;
All local variables (class names) are exported as named exports. To achieve this behaviour you also have to setup modules
option for css-loader
. For more information consult with css-loader
documentation
.
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
exclude: /\.lazy\.css$/i,
use: ["style-loader", "css-loader"],
},
{
test: /\.lazy\.css$/i,
use: [
{ loader: "style-loader", options: { injectType: "lazyStyleTag" } },
{
loader: "css-loader",
// Uncomment it if you want to use CSS modules
// options: { modules: true }
},
],
},
],
},
};
The loader inject styles like:
<style>
.foo {
color: red;
}
</style>
<style>
.bar {
color: blue;
}
</style>
lazySingletonStyleTag
Injects styles into the DOM using one <style></style>
on demand.
We recommend following .lazy.css
naming convention for lazy styles and the .css
for basic style-loader
usage (similar to other file types, i.e. .lazy.less
and .less
).
When you lazySingletonStyleTag
value the style-loader
injects the styles lazily making them useable on-demand via style.use()
/ style.unuse()
.
â ï¸ Source maps do not work.
â ï¸ Behavior is undefined when
unuse
is called more often thanuse
. Don't do that.
component.js
import styles from "./styles.css";
styles.use();
// For removing styles you can use
// styles.unuse();
component-with-css-modules.js
import styles, { "my-class" as myClass } from "./styles.lazy.css";
styles.use();
const divElement = document.createElement("div");
divElement.className = myClass;
All local variables (class names) are exported as named exports. To achieve this behaviour you also have to setup modules
option for css-loader
. For more information consult with css-loader
documentation
.
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
exclude: /\.lazy\.css$/i,
use: ["style-loader", "css-loader"],
},
{
test: /\.lazy\.css$/i,
use: [
{
loader: "style-loader",
options: { injectType: "lazySingletonStyleTag" },
},
{
loader: "css-loader",
// Uncomment it if you want to use CSS modules
// options: { modules: true }
},
],
},
],
},
};
The loader generate this:
<style>
.foo {
color: red;
}
.bar {
color: blue;
}
</style>
lazyAutoStyleTag
Works the same as a lazyStyleTag
, but if the code is executed in IE6-9, turns on the lazySingletonStyleTag
mode.
linkTag
Injects styles into the DOM using multiple <link rel="stylesheet" href="path/to/file.css">
.
â¹ï¸ The loader will dynamically insert the
<link href="path/to/file.css" rel="stylesheet">
tag at runtime via JavaScript. You should use MiniCssExtractPlugin if you want to include a static<link href="path/to/file.css" rel="stylesheet">
.
import "./styles.css";
import "./other-styles.css";
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.link\.css$/i,
use: [
{ loader: "style-loader", options: { injectType: "linkTag" } },
{ loader: "file-loader" },
],
},
],
},
};
The loader generate this:
<link rel="stylesheet" href="path/to/style.css" />
<link rel="stylesheet" href="path/to/other-styles.css" />
attributes
Type:
type attributes = HTMLAttributes;
Default: {}
If defined, the style-loader
will attach given attributes with their values on <style>
/ <link>
element.
component.js
import "./file.css";
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
{ loader: "style-loader", options: { attributes: { id: "id" } } },
{ loader: "css-loader" },
],
},
],
},
};
<style id="id"></style>
insert
Type:
type insert = string;
Default: head
By default, the style-loader
appends <style>
/<link>
elements to the end of the style target, which is the <head>
tag of the page unless specified by insert
.
This will cause CSS created by the loader to take priority over CSS already present in the target.
You can use other values if the standard behavior is not suitable for you, but we do not recommend doing this.
If you target an iframe make sure you have sufficient access rights, the styles will be injected into the content document head.
Selector
Allows to setup custom query selector where styles inject into the DOM.
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
{
loader: "style-loader",
options: {
insert: "body",
},
},
"css-loader",
],
},
],
},
};
Absolute path to function
Allows to setup absolute path to custom function that allows to override default behavior and insert styles at any position.
[!WARNING]
Do not forget that this code will be used in the browser and not all browsers support latest ECMA features like
let
,const
,arrow function expression
and etc. We recommend usingbabel-loader
for support latest ECMA features.
[!WARNING]
Do not forget that some DOM methods may not be available in older browsers, we recommended use only DOM core level 2 properties, but it is depends what browsers you want to support
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
{
loader: "style-loader",
options: {
insert: require.resolve("./path-to-insert-module"),
},
},
"css-loader",
],
},
],
},
};
A new <style>
/<link>
elements will be inserted into at bottom of body
tag.
Examples:
Insert styles at top of head
tag:
insert-function.js
function insertAtTop(element) {
var parent = document.querySelector("head");
// eslint-disable-next-line no-underscore-dangle
var lastInsertedElement = window._lastElementInsertedByStyleLoader;
if (!lastInsertedElement) {
parent.insertBefore(element, parent.firstChild);
} else if (lastInsertedElement.nextSibling) {
parent.insertBefore(element, lastInsertedElement.nextSibling);
} else {
parent.appendChild(element);
}
// eslint-disable-next-line no-underscore-dangle
window._lastElementInsertedByStyleLoader = element;
}
module.exports = insertAtTop;
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
{
loader: "style-loader",
options: {
insert: require.resolve("./insert-function"),
},
},
"css-loader",
],
},
],
},
};
You can pass any parameters to style.use(options)
and this value will be passed to insert
and styleTagTransform
functions.
insert-function.js
function insertIntoTarget(element, options) {
var parent = options.target || document.head;
parent.appendChild(element);
}
module.exports = insertIntoTarget;
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
{
loader: "style-loader",
options: {
injectType: "lazyStyleTag",
// Do not forget that this code will be used in the browser and
// not all browsers support latest ECMA features like `let`, `const`, `arrow function expression` and etc,
// we recommend use only ECMA 5 features,
// but it depends what browsers you want to support
insert: require.resolve("./insert-function.js"),
},
},
"css-loader",
],
},
],
},
};
Insert styles to the provided element or to the head
tag if target isn't provided. Now you can inject styles into Shadow DOM (or any other element).
custom-square.css
div {
width: 50px;
height: 50px;
background-color: red;
}
custom-square.js
import customSquareStyles from "./custom-square.css";
class CustomSquare extends HTMLElement {
constructor() {
super();
this.attachShadow({ mode: "open" });
const divElement = document.createElement("div");
divElement.textContent = "Text content.";
this.shadowRoot.appendChild(divElement);
customSquareStyles.use({ target: this.shadowRoot });
// You can override injected styles
const bgPurple = new CSSStyleSheet();
const width = this.getAttribute("w");
const height = this.getAttribute("h");
bgPurple.replace(`div { width: ${width}px; height: ${height}px; }`);
this.shadowRoot.adoptedStyleSheets = [bgPurple];
// `divElement` will have `100px` width, `100px` height and `red` background color
}
}
customElements.define("custom-square", CustomSquare);
export default CustomSquare;
styleTagTransform
Type:
type styleTagTransform = string;
Default: undefined
string
Allows to setup absolute path to custom function that allows to override default behavior styleTagTransform.
[!WARNING]
Do not forget that this code will be used in the browser and not all browsers support latest ECMA features like
let
,const
,arrow function expression
and etc, we recommend use only ECMA 5 features, but it is depends what browsers you want to support
[!WARNING]
Do not forget that some DOM methods may not be available in older browsers, we recommended use only DOM core level 2 properties, but it depends what browsers you want to support
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
{
loader: "style-loader",
options: {
injectType: "styleTag",
styleTagTransform: require.resolve("style-tag-transform-code"),
},
},
"css-loader",
],
},
],
},
};
base
type base = number;
This setting is primarily used as a workaround for css clashes when using one or more DllPlugin's. base
allows you to prevent either the app's css (or DllPlugin2's css) from overwriting DllPlugin1's css by specifying a css module id base which is greater than the range used by DllPlugin1 e.g.:
webpack.dll1.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: ["style-loader", "css-loader"],
},
],
},
};
webpack.dll2.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
{ loader: "style-loader", options: { base: 1000 } },
"css-loader",
],
},
],
},
};
webpack.app.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
{ loader: "style-loader", options: { base: 2000 } },
"css-loader",
],
},
],
},
};
esModule
Type:
type esModule = boolean;
Default: true
By default, style-loader
generates JS modules that use the ES modules syntax.
There are some cases in which using ES modules is beneficial, like in the case of module concatenation and tree shaking.
You can enable a CommonJS modules syntax using:
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
loader: "style-loader",
options: {
esModule: false,
},
},
],
},
};
Examples
Recommend
For production
builds it's recommended to extract the CSS from your bundle being able to use parallel loading of CSS/JS resources later on.
This can be achieved by using the mini-css-extract-plugin, because it creates separate css files.
For development
mode (including webpack-dev-server
) you can use style-loader
, because it injects CSS into the DOM using multiple <style></style>
and works faster.
[!WARNING]
Do not use together
style-loader
andmini-css-extract-plugin
.
webpack.config.js
const MiniCssExtractPlugin = require("mini-css-extract-plugin");
const devMode = process.env.NODE_ENV !== "production";
module.exports = {
module: {
rules: [
{
test: /\.(sa|sc|c)ss$/,
use: [
devMode ? "style-loader" : MiniCssExtractPlugin.loader,
"css-loader",
"postcss-loader",
"sass-loader",
],
},
],
},
plugins: [].concat(devMode ? [] : [new MiniCssExtractPlugin()]),
};
Named export for CSS Modules
[!WARNING]
It is not allowed to use JavaScript reserved words in css class names.
[!WARNING]
Options
esModule
andmodules.namedExport
incss-loader
should be enabled (by default forcss-loader@7
it is true).
styles.css
.fooBaz {
color: red;
}
.bar {
color: blue;
}
.my-class {
color: green;
}
index.js
import { fooBaz, bar, "my-class" as myClass } from "./styles.css";
console.log(fooBaz, bar, myClass);
Or:
index.js
import * as styles from "./styles.css";
console.log(styles.fooBaz, styles.bar, styles["my-class"]);
You can enable a ES module named export using:
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/,
use: [
{
loader: "style-loader",
},
{
loader: "css-loader",
options: {
modules: {
namedExport: true,
},
},
},
],
},
],
},
};
Source maps
The loader automatically inject source maps when previous loader emit them.
Therefore, to generate source maps, set the sourceMap
option to true
for the previous loader.
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
"style-loader",
{ loader: "css-loader", options: { sourceMap: true } },
],
},
],
},
};
Nonce
If you are using a Content Security Policy (CSP), the injected code will usually be blocked. A workaround is to use a nonce. Note, however, that using a nonce significantly reduces the protection provided by the CSP. You can read more about the security impact in the specification. The better solution is not to use this loader in production.
There are two ways to work with nonce
:
- using the
attributes
option - using the
__webpack_nonce__
variable
[!WARNING]
the
attributes
option takes precedence over the__webpack_nonce__
variable
attributes
component.js
import "./style.css";
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
{
loader: "style-loader",
options: {
attributes: {
nonce: "12345678",
},
},
},
"css-loader",
],
},
],
},
};
The loader generate:
<style nonce="12345678">
.foo {
color: red;
}
</style>
__webpack_nonce__
create-nonce.js
__webpack_nonce__ = "12345678";
component.js
import "./create-nonce.js";
import "./style.css";
Alternative example for require
:
component.js
__webpack_nonce__ = "12345678";
require("./style.css");
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: ["style-loader", "css-loader"],
},
],
},
};
The loader generate:
<style nonce="12345678">
.foo {
color: red;
}
</style>
Insert styles at top
Insert styles at top of head
tag.
insert-function.js
function insertAtTop(element) {
var parent = document.querySelector("head");
var lastInsertedElement = window._lastElementInsertedByStyleLoader;
if (!lastInsertedElement) {
parent.insertBefore(element, parent.firstChild);
} else if (lastInsertedElement.nextSibling) {
parent.insertBefore(element, lastInsertedElement.nextSibling);
} else {
parent.appendChild(element);
}
window._lastElementInsertedByStyleLoader = element;
}
module.exports = insertAtTop;
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
{
loader: "style-loader",
options: {
insert: require.resolve("./insert-function.js"),
},
},
"css-loader",
],
},
],
},
};
Insert styles before target element
Inserts styles before #id
element.
insert-function.js
function insertBeforeAt(element) {
const parent = document.querySelector("head");
const target = document.querySelector("#id");
const lastInsertedElement = window._lastElementInsertedByStyleLoader;
if (!lastInsertedElement) {
parent.insertBefore(element, target);
} else if (lastInsertedElement.nextSibling) {
parent.insertBefore(element, lastInsertedElement.nextSibling);
} else {
parent.appendChild(element);
}
window._lastElementInsertedByStyleLoader = element;
}
module.exports = insertBeforeAt;
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
{
loader: "style-loader",
options: {
insert: require.resolve("./insert-function.js"),
},
},
"css-loader",
],
},
],
},
};
Custom Elements (Shadow DOM)
You can define custom target for your styles for the lazyStyleTag
type.
insert-function.js
function insertIntoTarget(element, options) {
var parent = options.target || document.head;
parent.appendChild(element);
}
module.exports = insertIntoTarget;
webpack.config.js
module.exports = {
module: {
rules: [
{
test: /\.css$/i,
use: [
{
loader: "style-loader",
options: {
injectType: "lazyStyleTag",
// Do not forget that this code will be used in the browser and
// not all browsers support latest ECMA features like `let`, `const`, `arrow function expression` and etc,
// we recommend use only ECMA 5 features,
// but it is depends what browsers you want to support
insert: require.resolve("./insert-function.js"),
},
},
"css-loader",
],
},
],
},
};
Insert styles to the provided element or to the head
tag if target isn't provided.
custom-square.css
div {
width: 50px;
height: 50px;
background-color: red;
}
custom-square.js
import customSquareStyles from "./custom-square.css";
class CustomSquare extends HTMLElement {
constructor() {
super();
this.attachShadow({ mode: "open" });
const divElement = document.createElement("div");
divElement.textContent = "Text content.";
this.shadowRoot.appendChild(divElement);
customSquareStyles.use({ target: this.shadowRoot });
// You can override injected styles
const bgPurple = new CSSStyleSheet();
const width = this.getAttribute("w");
const height = this.getAttribute("h");
bgPurple.replace(`div { width: ${width}px; height: ${height}px; }`);
this.shadowRoot.adoptedStyleSheets = [bgPurple];
// `divElement` will have `100px` width, `100px` height and `red` background color
}
}
customElements.define("custom-square", CustomSquare);
export default CustomSquare;
Contributing
Please take a moment to read our contributing guidelines if you haven't yet done so.
License
Top Related Projects
CSS Loader
Compiles Sass to CSS
Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
👩🎤 CSS-in-JS library designed for high performance style composition
Documentation about css-modules
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot