Eclipse Community Forums: Orion (Archived) » One minute install as advertised, but opps...

Home » Archived » Orion (Archived) » One minute install as advertised, but opps...(Error when "starting" node app in shell)

Show: Today's Messages :: Show Polls :: Message Navigator

One minute install as advertised, but opps... [message #1127541]

Sun, 06 October 2013 20:15

Robin Mattern

Messages: 2
Registered: October 2013

Junior Member

I just discovered Orion today while watching the video listed below. Ken said I could install the NodeJS version of Orion in one minute and he was right! (except I had to hunt for the wiki page that I couldn't quite hear)

Discussing Eclipse Orion with Ken Walker (www.youtube.com/watch?v=MbmLREUhFB0)
Goto the Orion page in the Eclipse Wiki
Click on the link, Orion Node Getting Started Guide

So I followed these steps to install it:

Open Windows Command Prompt, cmd.exe
Install Orion with the command, npm install orion

Create a batch file, Start-Orion.bat, to run Orion from anywhere

 @echo off
   set  aPath=Node-apps\node_modules\orion
   set  aWS=Web-Root\Orion\Workspace1
  node %aPath%\server.js -p 8081 -w %aWS%

Execute the batch file, Start-Orion
Use Chrome to goto URL: localhost:8081

And it's running!!! What a beautiful piece of work. But, alas, when I went to
the Shell and issued the command,

node start hello.js

, with one line of Node javascript,

console.log( "hello" )

I got the following error:

TypeError: Cannot read property 'Location' of undefined

Did I miss a configuration step?

Thanks for your support.

Robin

Report message to a moderator

Re: One minute install as advertised, but opps... [message #1128281 is a reply to message #1127541]

Mon, 07 October 2013 14:32

Mark Macdonald

Messages: 35
Registered: July 2009

Member

No, you didn't miss anything... this is a bug. Did you by any chance create hello.js directly under Workspace1? That is what triggers this problem for me.

Just create a subfolder of Workspace1, move hello.js into the subfolder, and then the 'node' command should work.

I opened a bug for this in our bug system.

Report message to a moderator