document npm link commands in README

[cvan]

No description provided.

[cvan]

is this clear to folks?

[cvan]

and perhaps I should add a comment about npm unlink

[cvan]

superfluous newline

[ngokevin]

I was thinking about documenting this too, but I would have put it in vr-markup's documentation. I run npm link because I want to hack on vr-markup, not because I want to hack on vr-components.

Besides that, I would also document that the user should run both dev servers for ``vr-componentsandvr-markup`, and they should use the bundle served in memory at `http://localhost:9001/build/vr-components.js` rather than the one on the filesystem so they don't have to re-run build all the time.

[ngokevin]

vr-markup, not vr-components

[cvan]

ha, very good call

[cvan]

Besides that, I would also document that the user should run both dev servers for vr-components and vr-markup, and they should use the bundle served in memory at http://localhost:9001/build/vr-components.js rather than the one on the filesystem so they don't have to re-run build all the time.

Even if just vr-components's dev server is running, the bundle gets recompiled automatically actually when the files change. Does that not happen for you?

[cvan]

@ngokevin: thanks for the good feedback. I've addressed everything except the most recent comment, which I just responded to.

let me know what you think.

[ngokevin]

i guess so, I might've been running both just in case. Are you going to keep the link docs in this repo? I feel like it's focused on developing on markup rather than components. r+ otherwise since it's good to know how to link