silverwind

Seeing this "close timed out after 1000ms" message [on Drone CI](https://drone.gitea.io/go-gitea/gitea/62946/1/11) as well. Test run still succeeds, and all tests are very simple unit tests, nothing fancy, nothing that would...

For me, it was on Node 18 with no coverage enabled.

I happen to have one case where it reproduces locally, in a around 1 in 10 runs. When it happens, the node process goes to 100% cpu and hangs forever....

Just `node --inspect node_modules/.bin/vitest` with chrome `chrome://inspect/#devices` waiting in background, see [here](https://nodejs.org/en/docs/guides/debugging-getting-started/). The problem with the method is one needs to be quick with opening the inspector window because once...

Still seeing it with esbuild 0.16.10, but I guess this issue has multiple potential causes, so the above update may have fixed one, but not all of them.

I do agree that a "strict" mode that actually follows the spec would be nice. As seen in https://github.com/npm/cli/issues/6370, the currently sloppy parsing already causes issues for npm itself.

Can [`eslint-plugin-i`](https://www.npmjs.com/package/eslint-plugin-i) be added to the list? With 136k weekly downloads, I think it easily qualifies as popular. It being a soft for of `eslint-plugin-import` likely means it won't gain...

> Can [`eslint-plugin-i`](https://www.npmjs.com/package/eslint-plugin-i) be added to the list? With 136k weekly downloads, I think it easily qualifies as popular. It being a soft for of `eslint-plugin-import` likely means it won't...

For Sublime Text, https://github.com/polygonplanet/sublime-text-eslint is listed but there is also the much more popular https://github.com/SublimeLinter/SublimeLinter-eslint plugin. It does appear to work fine with flat config at first glance.

> @jlarmstrongiv Out of curiosity: is it even maintained? the last version was published ~4 years ago! It may not be maintained but it sure is popular.