Post

Ooooh, the Stylelint team are removing some dependencies and in the process also making it easier to run Stylelint in the browser. github.com/stylelint/st...

github.comRefactor `stringFormater` and `TIMING` to remove `table` and `string-width` deps by jeddy3 · Pull Request #9495 · stylelint/stylelintWhich issue, if any, is this issue related to? Closes #9341 Is there anything in the PR that needs further explanation? Replaces the table and string-width deps (and 11 transitive dependencies) ...

romainmenke

@romainmenke.bsky.social

9 Sept

Feel free to open an issue if there were specific dependencies that made it hard to run Stylelint in the browser :)

Bart Veneman

@veneman.dev

Thanks, I was going to give this another go after the next release! I think my main were that I'd like some specific non-node entry points to avoid all the globbing/IO etc. I can't remember exactly, but I will write it up.

9/9/26, 8:28 am0 reposts1 like

romainmenke

@romainmenke.bsky.social

9 Sept

You could try with the v18 branch (if you have time). Will be a while until we start planning a v19 so now is a good window to request such changes :)

Bart Veneman

@veneman.dev

9 Sept

Oooooh That's actually a pretty good idea.

Bart Veneman

@veneman.dev

20 Sept

I think I've nailed it down to these points (with a bunch of help from Claude): - Linting always starts from the `stylelint` global, no official way to skip I/O; also true for `createPlugin()` which leads ever - Several modules import Node API's to get EOL and process.env which trips the browser

Bart Veneman

@veneman.dev

20 Sept

What's the best way to approach this? Append finding to github.com/stylelint/st..., open 1 new issue or several issues?