fix(v2): output .noWait() as 'NOWAIT' - #108
Conversation
was previously output as 'NO WAIT'
|
@prust any idea why the build is failing or how I can fix it? |
|
@joelmukuthu: Yes, the same thing happened on I suppose that's technically fair, since Node 4.x ended its maintenance cycle in April, but it makes me feel like a grumpy old man (why are major platform versions only supported for a few years instead of a few decades?) We'll need to update the |
|
Sorry for the late response. Haha, yeah the JS/Node community tends to move a bit too fast, which would not be a problem if only we'd support the old stuff a bit longer. Speaking of, how's it going with V3? :) |
|
thanks @joelmukuthu, this is merged & deployed to npm as 2.0.4.
Well, I guess I don't move too fast :-) I'm going to need to carve out some time to move forward on v3. I do want to, and plan to, but it's a matter of making the time in my work day or in my afternoons/evenings, both of which are a bit tight at the moment. |
|
Great, thanks! Sounds good with the plan and I'm not blocked on anything so no rush. I'm looking forward to it all the same! :) |
Was previously output as 'NO WAIT'.
This applies the fix made in #106 to the v2 branch.