-
Notifications
You must be signed in to change notification settings - Fork 65
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 JSChannel to npm #29
Comments
I'd love this too. |
@erm0l0v I've noticed you made a pull request to fix this, but jschannel doesn't look very active anymore - no recent commits, pulls, or responses to the issues. I'd suggest we do as @lucasconstantino did here for bower with #27 and simply publish it to npm, with the caveat that the link can be changed if Mozilla wishes. I'm happy to do this if you'd rather not? |
Looks like this is the most active fork https://github.com/adtile/jschannel . Probably will be better if adtile team publish their version to npm. |
I've forked their version and published it, since adtile doesn't have issues enabled for their fork. https://www.npmjs.com/package/jschannel Happy to cede the links/ownership back to anyone else interested in taking active ownership of the project, but otherwise I'll try to do what I can myself. |
Thanks for doing this @yochannah. |
Hey. Why don't you add JSChannel to npm? Any problems with this package manager.
I like this library and I would like to use it with webpack without copy a file manually.
The text was updated successfully, but these errors were encountered: