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.
Is this project still relevant/maintained?
See original GitHub issueNow that there’s node --inspect, do you still plan to maintain this tool?
I’m seeing a lot of confused people because everybody is talking about node --inspect but new people accidentally check out node-inspector, which is a completely different tool and has a few issues.
So what’s the current state?
It would be nice to have a deprecation messagein the readme and maybe a link to a tutorial with node --inspect. e.g. https://medium.com/@paul_irish/debugging-node-js-nightlies-with-chrome-devtools-7c4a1b95ae27#.jtswxc8y7
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@marcbachmann Since most of the smart TV providers are using this tool for their browsers and they won’t update their node versions (so we won´t be able to use
node --inspect), this is the only way that people who develop with TVs can debug properly (the alternative is weinre, which is a really old-fashioned tool in these times).For these reasons, I think that this project is still relevant.
OK, Is this project still relevant/maintained? The answer is YES. I’am closing this issue now.