Using `--why --save-bundle <DIR>` with multiple sections is buggy
- Linguagem predominante
- JavaScript
- Estrelas
- 6.9k
- Forks
- 1.8k
- Merge médio
- 44min
- PRs com merge (30d)
- 1
Descrição
I tried using `size-limit --why --clean-dir --save-bundle ./test` with a config file that looks like this:
```
const defaultConfig = {
path: './src/main-modules.ts',
brotli: false,
};
module.exports = [
{
name: 'Full package',
import: '*',
limit: '200 kB',
...defaultConfig,
},
{
name: 'Testing EventEmitter',
import: '{ EventEmitter }',
limit: '20 kB',
...defaultConfig,
},
{
name: 'Testing Pool',
import: '{ Pool }',
limit: '20 kB',
...defaultConfig,
},
];
```
While multiple `.html` report files are generated with different names, as the sections, the `.js` files generated are always with the same name. This results in only the last section actually being tested (I assume they override each other) and all the reports are taintent and identical. (based on the last section)
I didn't look into the library's code yet but I assume the solution should be to also generate multiple `index.js` files based on the section name.
P.S. It'd also be nice to be able to cancel minification from the config options. This helps a lot when trying to debug why tree-shaking is failing.
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Avaliação
Esta issue ainda não foi avaliada.