Worms David

This is pretty much the case for every option. Not sure it provide much value.

This is a nightmare

Hum, that is an interesting possibility.

Does having both the "module" and "moduleResolution" set to "Node16" could resolve the issue ?

Otherwise, could someone reproduce the issue in a branch inside a dedicated "./demo/{package}". Reproducing the issue would help finding a solution

OK, then let's close it.

There is an "unofficial" and undocumented [module implementing WhatWG streams](https://github.com/adaltas/node-csv/blob/master/packages/csv-parse/lib/stream.js). It is [not very tested](https://github.com/adaltas/node-csv/blob/master/packages/csv-parse/test/api.web_stream.coffee). Last time I checked, about 2 years ago, it was about 50% slower than the...

Could you check the latest [version 5.4.1 with Are types wrong ?](https://arethetypeswrong.github.io/?p=csv-parse%405.4.1), the "csv-parse/sync" with node16 from CJS is now ok after the changes from #397.

I reproduce the issue. The code run. Only eslint is having an issue resolving ESM imports when the package uses the `exports` field. It might be related to https://github.com/import-js/eslint-plugin-import/issues/1810. In...

Doing some cleanup, closing.