add troubleshooting section to readme; reiterate installing the latest voodoospark

[kevinold]

This might be just for me and my recent issue (#33) but I think this section and reiteration would help others (maybe just me in a few weeks/months).

[rwaldron]

I like it!

What else can we put in there? I'm about to go radio silent for 5 hours, but dig through the issues and see what else is good fodder for this and I can land it when I get to Seattle :)

[kevinold]

I'll keep thinking on what tripped me up and that we can add to the list.

Another idea I had was to add a "postinstall" message to remind the user to
update voodoospark. I've never done it, but I think it'll work:

  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "postinstall": "echo \"Make sure you have the latest voodoospark!\""
  },

I can send this as another PR if you like the idea.

Kevin

Kevin Old
[email protected]

On Mon, Jul 28, 2014 at 4:01 PM, Rick Waldron [email protected]
wrote:

I like it!

What else can we put in there? I'm about to go radio silent for 5 hours,
but dig through the issues and see what else is good fodder for this and I
can land it when I get to Seattle :)

—
Reply to this email directly or view it on GitHub
#34 (comment).

[rwaldron]

Write a patch!

On Monday, July 28, 2014, Kevin Old [email protected] wrote:

I'll keep thinking on what tripped me up and that we can add to the list.

Another idea I had was to add a "postinstall" message to remind the user
to
update voodoospark. I've never done it, but I think it'll work:

"scripts": {
"test": "echo \"Error: no test specified\" && exit 1",
"postinstall": "echo \"Make sure you have the latest voodoospark!\""
},

I can send this as another PR if you like the idea.

Kevin

Kevin Old
[email protected] javascript:_e(%7B%7D,'cvml','[email protected]');

On Mon, Jul 28, 2014 at 4:01 PM, Rick Waldron <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');>
wrote:

I like it!

What else can we put in there? I'm about to go radio silent for 5 hours,
but dig through the issues and see what else is good fodder for this and
I
can land it when I get to Seattle :)

—
Reply to this email directly or view it on GitHub
#34 (comment).

—
Reply to this email directly or view it on GitHub
#34 (comment).

[kevinold]

I have the message working with a "prepublish" or "postinstall" but the placement is the same and it gets printed before the dependencies are installed so it could get lost in the noise. Ideas?