Skip to content
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

Closed
rgiard opened this issue Sep 2, 2014 · 10 comments
Closed

Not browserify compatible #191

rgiard opened this issue Sep 2, 2014 · 10 comments
Assignees
Labels
Status: Pinned A way to keep old or long lived issues around

Comments

@rgiard
Copy link

rgiard commented Sep 2, 2014

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 ...

@feltnerm
Copy link

feltnerm commented Sep 2, 2014

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.

@rgiard
Copy link
Author

rgiard commented Sep 2, 2014

Oh Thanks @feltnerm ! Let me check your work. Still, it would be nice to have the module browserify compatible :)

@piranna
Copy link

piranna commented Feb 15, 2015

Any update on this? I'm also interested on access GitHub API from browser...

@revolunet
Copy link

+1

@jamestalmage
Copy link

I have browser support working. See #261

Until @mikedeboer merges, you can install my patch via:
npm install --save jamestalmage/node-github#browserify-compatibility

@kaizensoze kaizensoze added the Status: Up for grabs Issues that are ready to be worked on by anyone label Jun 26, 2016
@kaizensoze kaizensoze removed the Status: Up for grabs Issues that are ready to be worked on by anyone label Jul 28, 2016
@jwickens
Copy link

+1 would be great if the patch was merged to master

@gr2m
Copy link
Contributor

gr2m commented Jul 19, 2017

@jamestalmage note that browserify-compatibility branch no longer exist. Is it maybe browserify-and-promises now?

npm install --save jamestalmage/node-github#browserify-and-promises

I tried to browsery using your fork, but got Error: Cannot find module './api/vundefined'. Do you have a built somewhere you can share?

@gr2m gr2m added this to the v14.0.0 - Browser compatibility milestone Dec 26, 2017
@gr2m
Copy link
Contributor

gr2m commented Dec 26, 2017

update: browser compatibility is the next big milestone. I recommend to subscribe to this issue to stay up-to-date: #620

@gr2m gr2m self-assigned this Dec 26, 2017
@stale
Copy link

stale bot commented Jan 23, 2018

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.

@stale stale bot added the stale label Jan 23, 2018
@gr2m gr2m added Status: Pinned A way to keep old or long lived issues around and removed stale labels Jan 23, 2018
@gr2m
Copy link
Contributor

gr2m commented Feb 2, 2018

The latest release of @octokit/rest is compatible with browserify. See more news regarding browser support in my latest update: https://github.com/octokit/rest.js/issues/620#issuecomment-362715478

I recommend to subscribe to issue #620 to stay up-to-date with all things JavaScript Octokit :)

@gr2m gr2m closed this as completed Feb 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Pinned A way to keep old or long lived issues around
Projects
None yet
Development

No branches or pull requests

8 participants