New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add deprecation note in README.md - was: NPM out of date? #15
Comments
Thanks for the bug report! Sorry for the probs. I haven't used Also willing to take a PR. I suppose I should deprecate the package, if no one wants to pick it up ... |
No problem! In this case, I don't think you actually need a PR, just a re-publishing to npm. If you want to give me commit permissions, I can give it a try myself. Or if you'd rather mark it as deprecated I'll give nodemon a try :) 👍 Thanks! |
if you want to take over wr, happy to make you an npm owner, commit rights on the GH repo (or you can clone), etc. But I really suggest looking into an alternative, like nodemon. I enjoy the whole "no maintenance for me to do" aspect :-) |
@pmuellr Cool! I just tried nodemon with my Elm project, and it's working quite nicely. |
Might be worth adding your suggestion, and a note of deprecation to the readme? Thanks again! |
Ya, I deprecated the top-level package version, so you now see this when you
But nothing shows at https://www.npmjs.com/package/wr - previous experience deprecating packages is that you need to be very noisy (eg, in the README) about the deprecation ... |
Hi there, thanks for this great library!
I just ran
npm install -g wr
, which reported having installed v1.3.1, but I got the following error while trying to perform a watch:I took a look at
wr/lib/Executor.js:123
and noticed that the code didn't match the code that's up on Github in the master branch.I uninstalled from NPM, and then re-installed straight from GitHub:
npm install -g pmuellr/wr
and all worked as expected.
Could it be that NPM's copy has somehow gotten out of date? Would you mind pushing up a patch version or something, to make sure the right source is in there?
Just in case it matters, I'm running on Node v5.3.0
The text was updated successfully, but these errors were encountered: