-
-
Notifications
You must be signed in to change notification settings - Fork 848
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
issue installing #6
Comments
@nnarhinen is the owner of npm package of that name which, in his case, is the same as the name of GitHub repository. I have already written to him as he is looking for maintainer, and I'm willing to take this responsibility. Until the name in npm is released by him, as a workaround, you can add this repo to your package.json by adding this line:
And you should be good to go! If you were using version 0.0.x by @nnarhinen, be sure to check out Upgrade guide. |
Would be nice if this fork could become the official version, or at least get merged back in again. Installing from npm is nicer, particularly with yarn. @nnarhinen, any update? |
@jarekwg Since I got no reply from him on several email, I've emailed npm team. We'll see what we can do :) |
Oh sorry. I did not notice any emails! I have now given you push rights to my repository. What's your NPM username, will add publish rights there too! |
@jarekwg @Solitaryo You should be able to enjoy the latest & greatest without any hacks now! |
If i run
npm install --save react-pdf
i got the @nnarhinen version, not yours, any idea why?The text was updated successfully, but these errors were encountered: