"no-unresolved" flagged for import of `csv-stringify`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4.3k
- Forks
- 299
- Avg merge
- 16h 19m
- Merged PRs (30d)
- 1
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the TypeScript import from csv-stringify/sync after upgrading from 5.6.5 to 6.2.3, then inspect how the package entry point is resolved. The work is done when the import continues to run and the editor no longer reports no-unresolved for that path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100