Bjorn Lu

While HTML comments work in JS historically for compat, the JS expression block should technically contain only JS and comments would be `/* comment */` instead. So I'm not sure...

Update: the error message is still the same (and confusing), but syntax highlighting now has a small hint of the error:

If the field isn't specified, then the lowest node version supported from the first stable version would implicitly be it. Bumping beyond that would be a breaking change technically. Otherwise...

Is this PR still needed? I'm not sure about the error message if it fails, I assume if `node_modules` is not writable there would be errors already about it? Anyways...

I think in a way this PR is already a partial migrate to make the title work, and is better to implement this single feature first, then we can decide...

Maybe taking the [Baseline docs](https://web-platform-dx.github.io/web-features/#:~:text=Widely%20available,green%20icon), we can phrase it as this? > These browsers support common features that has been available for at least 2.5 years. Also, this link seems...

Sounds good to me. > These code use features... Would it be more accurate to start with "These browsers support features..." since we're referring to the browser versions?

If `rimraf` is only used for scripts after this, maybe it's worth swapping to [`premove`](https://www.npmjs.com/package/premove) too as it has less dependencies. (Not that it matters much in practice as it's...

We can just bump to 0.27.0 as we've done the same in the past. This'll likely be merged shortly after as a small v7 minor.

@denghongcai don't bother. He's one of the many spam recently creating AI slop PRs ☹️ --- About the feature request, it sounds reasonable, but it's more to maintain for us...