Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Closed
Description
Before You File a Bug Report Please Confirm You Have Done The Following...
- I have tried restarting my IDE and the issue persists.
- I have updated to the latest version of the packages.
- I havesearched for related issues and found none that matched my issue.
- I haveread the FAQ and my problem is not listed.
Relevant Package
types
Playground Link
No response
Repro Code
NOTE:Thisaffectsafew`@typescript-eslint/`packages.I'll take one package example:1.Visit https://www.npmjs.com/package/@typescript-eslint/types?activeTab=code2.Check`dist/ts-estree.d.ts.map`3.Noticethe`"sources"`pointsto`"../src/ts-estree.ts"`whichisn't published
ESLint Config
irrelevanttsconfig
irrelevant
Expected Result
The sourcemap"sources" should point to an existing file, or the sourcemap should be removed entirely.
Actual Result
The sourcemap"sources" points to unpublished files, meaning that the IDE can't use it to navigate to the original types or declaration if I want to "go to source definition". Any stacktraces using the sourcemap would also point to a non-existing file, making it not possible to visit the file for debugging.
Additional Info
I find that this affects a few packages including:
@typescript-eslint/types@typescript-eslint/eslint-plugin@typescript-eslint/parser@typescript-eslint/typescript-estree@typescript-eslint/type-utils@typescript-eslint/utils
It might be easier to remove the.d.ts.map files entirely as the.js files don't have sourcemaps either.
Versions
I'm copying my local versions here but I'm pretty sure it's relevant in the current latest releases too
| package | version |
|---|---|
@typescript-eslint/eslint-plugin | 8.43.0 |
@typescript-eslint/parser | 8.43.0 |
@typescript-eslint/typescript-estree | 8.43.0 |
@typescript-eslint/type-utils | 8.43.0 |
@typescript-eslint/utils | 8.43.0 |