Skip to content
This repository


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

How to Install #7

jasonmaster opened this Issue · 9 comments

6 participants

Jason Sweeney Piotr Yordanov Piotr Alistair Roche Geoff Greer chaoscollective
Jason Sweeney

does anyone know how to use this

Piotr Yordanov

+1 to that!

1am commented

+1 A short step-by-step instructions would be great.
I tried to do this but i keep getting errors like this all the time:

$ node app.js 
| * Starting Node service * |

        throw e; // process.nextTick error, or 'error' event on first tick
Error: ENOENT, no such file or directory '/.../SandboxApp/public/app.js'
    at Object.unlinkSync (fs.js:453:18)
    at Object.<anonymous> (/.../apps/Space_Editor/app.js:97:6)
    at Module._compile (module.js:441:26)
    at Object..js (module.js:459:10)
    at Module.load (module.js:348:31)
    at Function._load (module.js:308:12)
    at Array.0 (module.js:479:10)
    at EventEmitter._tickCallback (node.js:192:40)

Where can i find the SandboxApp which seems necessary to launch the server?

Piotr Yordanov

i was getting the same error :/

Jason Sweeney

me too

1am commented

pretty please :)

Alistair Roche


Geoff Greer

Here's how I got it working:

  • On line 61 of app.js, I changed EDITABLE_APPS_DIR to a path that exists.
  • On line 66, I changed REPLACE_SANDBOX_APP_DEMO_FILES to false.
  • I installed, then changed the initialization to work with the latest version of Express. See for more info on how to do this.
  • To work around some issues, I changed the config to try xhr and jsonp before websockets.
  • I linked node_modules/now/lib/client/now.js to public/nowjs/now.js to fix a 404.

Since my changes were so extensive, I forked this project. You should be able to get my fork running with the normal npm install and npm start.

Alistair Roche

Thanks @ggreer for helping to turn our initial code dump of the Space editor into something more useable for others.

As you can tell, Space evolved over time as we were figuring out the best way to use different packages and structures. It could stand to be a lot more modular. We'll be sure to keep that in mind for future releases (ideally publishing to NPM with proper package.json and dependency accounting). :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.