…
|
||
---|---|---|
.. | ||
__fixtures__ | ||
src | ||
.eslintrc.json | ||
CHANGELOG.json | ||
CHANGELOG.md | ||
README.md | ||
jest.config.ts | ||
package.json | ||
project.json | ||
tsconfig.json | ||
tsconfig.lib.json | ||
tsconfig.spec.json |
README.md
Webpack loader for Griffel
A loader for Webpack 5 that performs build time transforms for @griffel/react
.
Install
yarn add --dev @griffel/webpack-loader
# or
npm install --save-dev @griffel/webpack-loader
Usage
Webpack documentation: Loaders
Within your webpack configuration object, you'll need to add the @griffel/webpack-loader
to the list of modules, like so:
module.exports = {
module: {
rules: [
{
test: /\.(js|jsx)$/,
exclude: /node_modules/,
use: {
loader: '@griffel/webpack-loader',
},
},
// If your project uses TypeScript
{
test: /\.(ts|tsx)$/,
exclude: /node_modules/,
use: {
loader: '@griffel/webpack-loader',
options: {
babelOptions: {
presets: ['@babel/preset-typescript'],
},
},
},
},
],
},
};
While the loader itself has a short circuit to avoid processing (invoking Babel transforms) it's better to reduce the scope of processed files. For example, you can enforce a restriction to have makeStyles()
calls only in .styles.ts
files:
module.exports = {
module: {
rules: [
{
test: /\.styles.ts$/,
exclude: /node_modules/,
use: {
loader: '@griffel/webpack-loader',
options: {
babelOptions: {
presets: ['@babel/preset-typescript'],
},
},
},
},
],
},
};
Handling Griffel re-exports
import { makeStyles, makeResetStyles } from 'custom-package';
// 👇 custom import names are also supported
import { createStyles } from 'custom-package';
By default, the Webpack loader handles imports from @griffel/react
. The webpack loader can be re-configured to handle re-exports of Griffel from custom packages. The makeStyles
function itself can also be renamed in this case.
module.exports = {
module: {
rules: [
{
test: /\.(js|jsx)$/,
exclude: /node_modules/,
use: {
loader: '@griffel/webpack-loader',
options: {
modules: [
{
moduleSource: 'custom-package',
importName: 'makeStyles',
resetImportName: 'makeResetStyles',
},
],
},
},
},
],
},
};
Note: "custom-package" should re-export following functions from
@griffel/react
:
__styles
__css
__resetStyles
__resetCSS
Configuring Babel settings
If you need to specify custom Babel configuration, you can pass them to babelOptions
. These options will be used by the Webpack loader when parsing and evaluating modules.
module.exports = {
module: {
rules: [
{
test: /\.(ts|tsx)$/,
exclude: /node_modules/,
use: {
loader: '@griffel/webpack-loader',
options: {
babelOptions: {
// Optional plugins specific to your environment
plugins: ['@babel/plugin-proposal-class-static-block'],
// If your project uses TypeScript
presets: ['@babel/preset-typescript'],
},
},
},
},
],
},
};
Configuring webpack resolve options
If your @griffel/react
modules import other files (eg., a set of common mixins or colors for your app), the loader resolves these using enhanced-resolve
. By default, it inherits the settings resolve.alias
, resolve.modules
, and resolve.modules
from your Webpack config, while using its own default values for resolve.extensions
and resolve.conditionNames
.
If you want to change this behavior, you can choose which resolve
options are inherited from your Webpack config.
module.exports = {
module: {
rules: [
{
test: /\.(js|jsx)$/,
exclude: /node_modules/,
use: {
loader: '@griffel/webpack-loader',
options: {
inheritResolveOptions: ['alias', 'modules', 'plugins', 'conditionNames'],
},
},
},
],
},
};
Alternatively, you can specify custom resolve
options. These values will override any options inherited from your webpack config. This can be particularly important if you use custom conditionNames
that do not include require
, which is necessary for transformation.
module.exports = {
resolve: {
conditionNames: ['source', 'import'],
},
module: {
rules: [
{
test: /\.(js|jsx)$/,
exclude: /node_modules/,
use: {
loader: '@griffel/webpack-loader',
options: {
webpackResolveOptions: {
conditionNames: ['source', 'require'],
},
},
},
},
],
},
};
Configuring module evaluation
module.exports = {
module: {
rules: [
{
test: /\.(js|jsx)$/,
exclude: /node_modules/,
use: {
loader: '@griffel/webpack-loader',
options: {
evaluationRules: [],
},
},
},
],
},
};
The set of rules that defines how the matched files will be transformed during the evaluation. EvalRule
is an object with two fields:
- test is a regular expression or a function
(path: string) => boolean
- action is an
Evaluator
function, "ignore" or a name of the module that exportsEvaluator
function as a default export
If test
is omitted, the rule is applicable for all the files.
The last matched rule is used for transformation. If the last matched action for a file is "ignore" the file will be evaluated as is, so that file must not contain any js code that cannot be executed in nodejs environment (it's usually true for any lib in node_modules
).
If you need to compile certain modules under /node_modules/
(which can be the case in monorepo projects), it's recommended to do it on a module by module basis for faster transforms, e.g. ignore: /node_modules[\/\\](?!some-module|other-module)/
.
The default setup is:
module.exports = {
module: {
rules: [
{
test: /\.(js|jsx)$/,
exclude: /node_modules/,
use: {
loader: '@griffel/webpack-loader',
options: {
evaluationRules: [
{
action: require('@griffel/babel-preset').shakerEvaluator,
},
{
test: /[/\\]node_modules[/\\]/,
action: 'ignore',
},
],
},
},
},
],
},
};
Troubleshooting
Under hood @griffel/webpack-loader
uses @griffel/babel-preset
, please check "Troubleshooting" there.