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...
Post
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) ...
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
0 reposts0 likes
What's the best way to approach this? Append finding to github.com/stylelint/st..., open 1 new issue or several issues?
Yeah, I think some small affordances could make the public API more open to composition, pick-and-choose which entry points you need. But also, it could open up possibilities to run (parts of) stylelint.io/demo/ in the browser without web containers.