[BUG] Incorrect line number on "export * from ..."
See original GitHub issueDescribe the bug
An incorrect line number is reported by ts-prune when an export is using export * from ...:
To Reproduce
- Clone https://github.com/foxglove/studio/commit/e584cda2853dbd036b7d0109a9fec00fcec867d0
- Run
yarn && yarn lint:unused-exports
Expected behavior
Line 27 is reported (The export * from "./useConfig"; line)
Actual: Line 19 is reported (the line of the original export definition in a different file)
Optional: reference to the test project https://github.com/nadeesha/ts-prune/compare/master...jtbandes:export-from
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Line numbers are shown incorrectly when importing library ...
Line numbers are shown incorrectly when importing library that has default export #436.
Read more >Fix text-formatted numbers by applying a number format
Technique 1: Convert text-formatted numbers by using Error Checking. If you import data into Excel from another source, or if you type numbers...
Read more >[JDK-7024096] Stack trace has invalid line numbers
A DESCRIPTION OF THE PROBLEM : linenumbertable in compiled code only has line numbers for starts of statements. When a statement is using...
Read more >Exporting 2 address lines - eliminating line feed error [closed]
When this data is exported as a single address line - it throws an extra/bad line feed into the data that FUBARS everything...
Read more >Wrong line numbers in stack trace (release)
Using line numbers of the stacktrace, you'll find exactly what lines of codes are called when the app crashes. Share. Share a link...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I think this issue is still valid
Stale issue message