Repository navigation
"no-unresolved" flagged for import of csv-stringify #372
Description
Describe the bug
Not exactly a bug because it's not truly blocking me and I'm sure it's got something to do with my environment, but wanted to post here to help figure it out.
Basically I've upgraded to the latest version of this package and updated my imports to 'csv-stringify/sync', but my editor is flagging it as an unresolved dependency (even tho they path is resolved when I hover it). Everything seems to work fine, it's just annoying that this is being flagged.
Using TypeScript here as well, if that is relevant.
To Reproduce
- Updated
csv-stringifyfrom 5.6.5 to 6.2.3 - Change imports from...
...to...
import * as stringify from 'csv-stringify/lib/sync';import { stringify } from 'csv-stringify/sync';
Additional context
Reacted by Joshua and Sufiyan
Activity
wdavidw commentedon Dec 1, 2022
I am no export in the TS field, anyone ?
nwalters512 commentedon Jan 12, 2023
This is because this package now uses
exportsto declare what files are available, andeslint-plugin-importdoesn't yet support that: import-js/eslint-plugin-import#1810.Adding a file
sync.jsorsync/index.jsto the published version of these packages would resolve this.karlhorky commentedon Aug 25, 2023
Hm, I just tried upgrading to
csv@6.3.2(which also includes the changes from #397) and I no longer need an ESLint disable forimport/no-unresolved(not sure if this was caused by this change or some other earlier change) - can anyone else confirm that this is fixed now?