Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript Express Basics (2015) Developing Express Apps Like a Boss Interactive Debugging and Exploratory Programming

OSX: console logs "Internal error: illegal access" when breakpoint is supposedly hit

Happens on: OSX Chrome 50 Note: using latest version of all modules (node is 6.0.0) at the time of this post

So when running node-debug src/app and visiting the page all is well. Clicking the play button in the inspector starts the server as expected.

After setting the breakpoint via the inspector, and sending a GET request by visiting "localhost:300/blog" in order to hit the breakpoint, the console logs "Internal error: illegal access". Additionally, the breakpoint line isn't highlighted as to indicate that it has been hit. Also, nothing in the breakpoints local scope is available via the console.

Same here.

same!

I have the same problem too...

Same. I also had issues with installing node-inspector. I resolved that issue by using @0.7.4 when installing it.

4 Answers

Ok, my solution was to roll back my version of Node to 4.4.4LTS.

My system config is:

Mac OSX El Capitan

Node installed with Homebrew v4.4.4LTS

Check your version of Node by typing node --version

My version was 6.x.x which I suspect was causing the "internal error: illegal access" error. I removed node v6 and installed v4.4.4LTS, fired everything up and the error was not thrown.

If you're using the Homebrew installation of Node, this discussion might help get things sorted out. http://goo.gl/2fGu4Z

This issue has been corrected as of Node version 6.2.2 (possibly 6.2.1, but I didn't verify). Unfortunately, for those who use Homebrew, these versions are not available. However, NVM (Node Version Manager) can be installed via Homebrew and then used to install the newer Node version. It's easy:

brew install nvm

nvm install 6.2.2

All I can find on the issue. Seems to be V8. https://github.com/node-inspector/node-inspector/issues/413