forked from microsoft/accessibility-insights-web
-
Notifications
You must be signed in to change notification settings - Fork 0
/
style-plugin.js
111 lines (99 loc) · 5 KB
/
style-plugin.js
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
// Copyright (c) Microsoft Corporation. All rights reserved.
// Licensed under the MIT License.
const path = require('path');
const genericNames = require('generic-names');
const postcss = require('postcss');
const postCssModules = require('postcss-modules');
const sass = require('sass');
const generateScopedNameWithHash = genericNames('[local]--[hash:base64:5]');
const generateScopedNameWithoutHash = genericNames('[local]');
const CreateStylePlugin = (useHash = true) => {
return {
name: 'style-plugin',
setup(build) {
build.onResolve(
{
filter: /^css-module:/,
},
args => {
const prefixLen = 'css-module:'.length;
const extNameLength = path.extname(args.path).length;
return {
path: args.path.slice(prefixLen, args.path.length - extNameLength),
namespace: 'css-modules',
pluginData: args.pluginData,
};
},
);
/*
esbuild only allows you to create/resolve to a single piece of output per one file
matching the pattern/namespace combination. That is to say, after one onLoad method
returns contents for a particular file, that file is considered resolved and esbuild
will not continue to other onLoad methods (this includes onLoad methods in this plugin
OR other plugins). However, for our CSS, we want to create two: (1) a CSS file compiled
from the scss file featuring generated/hashed styles and (2) JS that connects the
generated/hashed styles to our code.
To do this, in our plugin's first onLoad method, we generate both the CSS and JS we need
using postCssModules. We then return the JS content, creating (2) in this case, and
append an import, for the styles, to our code with the 'css-module:' prefix. This prefix
allows us to create another pattern/namespace combination for our scss. These new import
statements will then be matched with this plugin's second onLoad method (per css-modules
namespace), which will finally create/return (1).
Note: the stylesheet only needs to be read once, in the first onLoad method, and can be
passed from there to the onResolve method, and from there to the second onLoad method.
The general idea for this solution was mainly derived from, in addition to looking at
various scss/sass esbuild plugins, this issue/comment:
(https://github.com/evanw/esbuild/issues/1723#issuecomment-954160553).
More info on plugins here: https://esbuild.github.io/plugins/.
*/
build.onLoad(
{
filter: /\.s?css$/,
},
async args => {
// per sass documentation, compile is twice as fast as compileAsync, hence it's
// usage here. https://sass-lang.com/documentation/js-api/modules#compileAsync
const normalizedPath = args.path.replaceAll(path.sep, path.posix.sep);
const source = sass.compile(normalizedPath).css.toString();
let singleModuleCssJSON;
const { css } = await postcss([
postCssModules({
generateScopedName: name => {
const scopedName = useHash
? generateScopedNameWithHash(name, normalizedPath)
: generateScopedNameWithoutHash(name, normalizedPath);
return `${scopedName}`;
},
localsConvention: 'camelCaseOnly',
getJSON(_, json) {
singleModuleCssJSON = JSON.stringify(json);
},
}),
]).process(source, { from: undefined });
let pathAsJsString = JSON.stringify(
normalizedPath.slice(normalizedPath.indexOf('src')),
);
let cssModuleImportString = pathAsJsString.replace(/^"/, '"css-module:');
return {
contents: `import ${cssModuleImportString};\nexport default ${singleModuleCssJSON};`,
loader: 'js',
pluginData: css,
};
},
);
build.onLoad(
{
filter: /.*/,
namespace: 'css-modules',
},
async args => {
return {
contents: args.pluginData,
loader: 'css',
};
},
);
},
};
};
module.exports = { CreateStylePlugin };