> ...it generated a bunch of errors... What errors did you get? Was it connected to a page that had your code loaded already? > Aside from it needing a brows

> ...it generated a bunch of errors... What errors did you get? Was it connected to a page that had your code loaded already? > Aside from it needing a browser to do anything with JS... If you eval a html file it will open it in a local webkit tab. You can then use that connection to eval js. A lot of the js tooling works better with the local connection too since it can directly hook into the devtools instead of having to send json over a websocket.