Brandon Mills

Is there still a motivating use case for a default severity? `eslint.rules.customizations` takes care of the editor integration case, and scripting can be solved with `|| exit 0`.

The shareable config use case makes sense :+1:

I believe I have a repro of this in a public repository, [eslint/eslint-plugin-markdown](https://github.com/eslint/eslint-plugin-markdown/), that demonstrates a behavior change from npm 8.9 to 8.10. With [`npm=8.10.0`, the install step gets killed...

We accepted this change in the [2023-02-09 TSC meeting](https://github.com/eslint/tsc-meetings/blob/main/notes/2023/2023-02-09.md#consider-using-renovate). I'm working on `release-please` first and will try to get to this next, but anyone else who's interested should feel free...

:100: This is clever, I like it! Feel free to go ahead and port the examples over. :boom:

@sankho if it helps, I could publish this as an alpha under the reasoning that alphas are all about trying out new features, even if they're not quite ready to...

Hey @sankho, just checking in - do you plan on finishing this up?

This aims to be a very thin wrapper around https://github.com/markmarkoh/datamaps, so I'd be happy to accept a pull request that enables anything that already exists in that project. For some...

Apologies for the delay in looking at this 😥 The [bubbles example](https://github.com/btmills/react-datamaps/blob/935fa3c30f9bb7fbbb33fd642dfc982a234fb3fc/examples/bubbles-example.jsx#L56) returns the string wrapped in `...`, which I think `datamaps` uses to generate HTML for the box. What...

Sorry for the long delay here. When I wrote my previous comment about processor options being the ideal way to do this without forking, I had forgotten about [an already-accepted...