Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unable to use REPL
See original GitHub issueTypeScript version: 2.5.3
» ts-node
> const x = 3
Thrown: ⨯ Unable to compile TypeScript
[eval].ts: Cannot find name 'exports'. (2304)
[eval].ts (0,11): Cannot find name 'module'. (2304)
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Can't use Repl.it - Replit
I tried refreshing the page, deleting the account and making another one but it doesn't seem to be effective in fixing the issue....
Read more >Repl error Unable to load and having a bit of trouble - Replit
whenever I open someone's repl, it shows this. And also when I reload it, it still doesn't work!
Read more >repl.it fails to connect - Replit
repl.it keeps on failing while trying to test any Python 3 code. It throws "Failed to connect. Reconnecting. ... Try to use CTRL...
Read more >I can't load my repl! How do I get my code back or how do I fix?
When I get to the repl, it loads and connects over and over, unable to see or copy my code. Is this happening...
Read more >How to fix it when it fails to connect. - Replit
when opening a new repl, sometimes it fails to connect. I'm going to show you the way I found to let it work....
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
Duplicate of https://github.com/TypeStrong/ts-node/issues/437.
No problem, I thought it was in the linked issue but it was in the duplicate of that duplicate. See https://github.com/TypeStrong/ts-node/issues/351#issuecomment-307178924.