Jumpei Ogawa

@mde I found I could send an update request to GitHub's vulnerability database from the link of CVE-2023-26105 by myself, so I have sent [the request](https://github.com/github/advisory-database/pull/1751). Therefore, you no-longer have...

@devongovett > it seems that is also behind an environment variable check. ~~Do you expect the Vite (and other bundlers) to ignore ``require(`../pkg`)`` block when the falsy value is set...

@devongovett @ArnaudBarre Sorry, that's what I missed when I post. Yes, lightningcss should not be bundled. Why did I think that it should be bundled...😅 As you might already noticed,...

If you merge this PR after `version-4` branch is merged to `main`, please switch the target branch of this PR to `main`. Let me know if any conflicts happened.

Sorry, I lost time contributing to EJS recently. :bow: If you can make use of my PRs, feel free to add your commits to the branches associated with my PRs....

Oh, so you use this plugin to ensure .editorconfig follows your ESLint config by the built-in rules or rules from `@eslint-stylistic`? That's not an expected use case of this plugin,...

That sounds reasonable. When I made this plugin, I added eslint to `dependencies` because it calls its API, but `peerDependencies` should be the better option.

Really? When I tested, this plugin didn't work properly at all with flat config. IIRC, I have tested when ESLint was v8, so ESLint might be updated so that legacy...

I quickly tested your config, but unfortunately, it didn't work on my end. This plugin internally calls the ESLint rules such as `indent` and `linebreak-style`, so it should not work...

@mde Thank you for the review! Because I was working another task today, I will check your comment and update this PR later. > Also adding you as a contributor...