Andrey Sitnik

Yes, Size Limit requires Node JS >= 14.

I send PR to `mdn/data` https://github.com/mdn/data/pull/642

@lahmatiy my PR to `mdn/data` was merged, but after `pnpm update` I still have an issue. Do we need to release `csstree`?

@Mouvedia no, `declaration-property-value-no-unknown` still doesn’t work https://github.com/logux/stylelint-config/actions/runs/6767060071/job/18389092890 @lahmatiy do we need to release a new `csstree` version with these `mdn-data` changes?

Do you have an idea how to fix it?

Will it be a better idea to pass environment variable? Like: ```sh SHOW_WHY_FOR=3 npx size-limit ``` Environment variable is more easy to use in your code (`process.env.SHOW_WHY_FOR`), they do not...

We can add `--why NAME` support to the `@size-limit/webpack` and `size-limit`. `NAME` is a `name:` value from Size Limit config. Do you like this API? You can send PR.

Sure, but you need to help me with PR since I am not so advanced GNOME developer :(

Do I understand correctly that you want `--why` with custom webpack config? In this case, just add Webpack Bundle Analyzer to your custom config. Maybe we can do it automatically?...

@jeffredodd Size Limit builds a project in memory. So you will not find it on the disk. Why do you need to find it?