|
|
Reply ·0 | |
|
|
|
Matt Attaway commented
11 years ago
My pleasure! I have a lot more stuff like it just laying around that I need to clean up and publish. |
Reply ·0 | |
|
|
|
|
Reply ·0 | |
|
|
|
|
Reply ·0 | |
|
|
|
Gabor Maghera commented
11 years ago
FYI - there is a fairly simple third party implementation in the npm registry with the same name - it's a wrapper around the p4 command. Npm does not distinguish the two, so it sees this third-party implementation as a legit update to yours. $ npm -q outdated p4 |
Reply ·0 | |
|
|
|
Gabor Maghera commented
11 years ago
Here's a link to that implementation in the npm registry: https://npmjs.org/package/p4 |
Reply ·0 | |
|
|
|
Matt Attaway commented
11 years ago
We can just rename ours to p4nodejs. Does that seem legit? (I used to manage one of our node experts, but I'm not one myself) 😄 |
Reply ·0 | |
|
|
|
Gabor Maghera commented
11 years ago
Sure, that sounds good. Publishing it to the npm registry with the new name might be a good idea. I'd be glad to assist if needed. |
Reply ·0 | |
|