Skip to content

Commit 6680419

Browse files
committed
Adjust readme
1 parent 2f4713c commit 6680419

File tree

1 file changed

+4
-17
lines changed

1 file changed

+4
-17
lines changed

README.md

+4-17
Original file line numberDiff line numberDiff line change
@@ -274,26 +274,13 @@ module.exports = {
274274

275275
## Using svelte-loader in combination with thread-loader
276276

277-
There is a way to make `svelte-loader` support `thread-loader`.
277+
By default `svelte-loader` uses a Map to store css, and passes keys to that Map through custom loader string in query parameter.
278278

279-
Enable `inlineCss: true` in options as shown below. It will make `svelte-loader` output component css in base64 as a query string to webpack, instead of saving it to a Map, and passing key to that map.
279+
This won't work for multiple `thread-loader` processess. `css-loader` won't find component's css in a Map that is located in other process.
280280

281-
This will make console output unpleasant to look at, but `thread-loader` will have access to the css data it needs to function properly.
281+
If you set up `thread-loader` on top of `svelte-loader` however, it will pass whole base64'd css in a query, without using Map.
282282

283-
```javascript
284-
...
285-
{
286-
test: /\.(html|svelte)$/,
287-
exclude: /node_modules/,
288-
use: {
289-
loader: 'svelte-loader',
290-
options: {
291-
inlineCss: true,
292-
},
293-
},
294-
},
295-
...
296-
```
283+
It will clutter the console output, but you will gain compilation speed, especially when using `tailwindcss` with `@apply` through `svelte-preprocess`.
297284

298285
## License
299286

0 commit comments

Comments
 (0)