Should not try to bundle CSS and other asset files about size-limit HOT 8 CLOSED

That's the exception thrown right now:

> size-limit
 ERROR  Error: 
ERROR in ./lib/Core-DnMX9gqv.css
Module parse failed: /Users/Sebastian/Workspace/sebastian-software/edge-core/lib/Core-DnMX9gqv.css Unexpected token (14:0)
You may need an appropriate loader to handle this file type.
|  */
| 
| ::before,
|  ::after {
|    background-repeat: no-repeat; /* 1 */
 @ ./lib/browser.es5.esm.js 13:0-44
 @ multi ./lib/browser.es5.esm.js
    at runWebpack.then.stats (/Users/Sebastian/Workspace/sebastian-software/edge-core/node_modules/size-limit/index.js:110:15)
    at <anonymous>

from size-limit.

Why we should not bundle them? They affects to bundle size and developers should take care.

Totally agree that it should not throw error. Let's add config for css-loader. Do you want to make PR?

from size-limit.

Both is okay in my opinion. If size-limit is mainly about JS size then it should respect JS only.

I mean right now you basically exclude asset files as well, as file-loader is replacing them with URLs.

I am not sure what is the right approach here.

If you like to have CSS included in the bundle, I'll do that PR.

from size-limit.

Are you sure, that file-loader replaces then to URL? I thought url-loader does it.

from size-limit.

It's the other way around.

"The url-loader works like the file-loader, but can return a DataURL if the file is smaller than a byte limit." via https://github.com/webpack-contrib/url-loader

from size-limit.

I am not sure about assets being added to the size. Sometimes you e.g. offer alternative file formats e.g. woff and woff2. I figure most people would never inline all of them.

from size-limit.

Here we go: #15

from size-limit.

Released in 0.10

from size-limit.