arethetypeswrong / arethetypeswrong/arethetypeswrong.github.io
Incorrect fallback bug detection
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 65
- PR merge metrics
- No merged PRs in 30d
Description
For a package like this:
```ts
// package.json
{
"name": "some-pkg",
"version": "0.0.0",
"exports": {
".": {
"import": {},
"require": {},
"default": "./index.js"
}
}
}
// index.js
console.log('a')
// index.d.ts
export {};
```
Importing it works in Node (and TypeScript) but arethetypeswrong reports that it's relying on https://github.com/microsoft/TypeScript/issues/50762 when it's not since TypeScript is doing the correct thing in this case and working like Node.
(of course it makes no sense to do what's in the example, it's just to illustrate the problem)
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the report with the package.json, index.js, and index.d.ts layout shown in the issue, then trace the fallback bug-detection path that flags TypeScript issue #50762. Compare the analyzer’s result with Node and TypeScript resolution for the import/require/default exports; done means this case is not reported as relying on that issue while genuine fallback cases remain detected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100