-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Not browserify compatible #191
Comments
Would ❤️ if this library was browserify-able. I was able to achieve success by modifying code from #121 (I also had to patch http-browserify to not send credentials on HTTPS to avoid CORS errors). I'd be willing to work on this if there was interest, and @mikedeboer was interested in reviewing for me. |
Oh Thanks @feltnerm ! Let me check your work. Still, it would be nice to have the module browserify compatible :) |
Any update on this? I'm also interested on access GitHub API from browser... |
+1 |
I have browser support working. See #261 Until @mikedeboer merges, you can install my patch via: |
+1 would be great if the patch was merged to master |
@jamestalmage note that
I tried to browsery using your fork, but got |
update: browser compatibility is the next big milestone. I recommend to subscribe to this issue to stay up-to-date: #620 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The latest release of I recommend to subscribe to issue #620 to stay up-to-date with all things JavaScript Octokit :) |
Not sure we should mark it has an issue, but it is not possible to browserify the module (http://browserify.org/). Using variables in "require(...)" and reading the routes from a file is not browserify safe. Just raising the point ...
The text was updated successfully, but these errors were encountered: