Guillaume Humbert

I'm having a similar problem as well when using those CSV packages in a CJS context. I'm still not sure that's the whole story, but if I got this right,...

I second this, a custom _final_ formatter would be great to enable anyone to override the log output, which should be completely customisable, whether it is for the pretty or...

Sorry if I wasn't clear, I'm not suggesting that this plugin should natively support `exports` or `imports` fields in `package.json` files, I'd just want an `exceptTarget` parameter to see the...

That's great for ESM! Although when consuming `csv-parse` and `csv-stringify` from a CJS module, the [problem I've described previously](https://github.com/adaltas/node-csv/issues/354#issuecomment-1295839363) is still present AFAICT. When writing `import { parse } from...

Thanks for the demo @jonmast, and sorry for not getting back to you @wdavidw! Another thing I haven't tried is putting the `exports.*.types` key as the first key in the...

My apologies for assuming you'd be OK with a breaking change, I did not ask prior to writing the PR as I should have. Although to reassure you, the breaking...

Hi @d3c0d3dpt 👋 Thanks for taking an interest, I haven't had time to return to this PR until last time, but if I remember the remaining things were: - Rebase...

Hi everyone, do you reckon this PR has a reason to be blocked? Like a lot of people, I've been sticking with v2.26.0 of this plugin since https://github.com/import-js/eslint-plugin-import/issues/2682 has been...

> It must have been something else then, because this field clearly instructs Node.js to treat all .js files as ESM. (unless you `require` them) To me all files in...

Hi, same question here! Is this plugin ready for consumption? The checkmark in the readme seems to indicate so, but I don't think it is yet? At least it doesn't...