-
Notifications
You must be signed in to change notification settings - Fork 147
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
[request] distribute the browserified highland with the NPM package #309
Comments
Just curious why don't require it in? I use browserify too, and this is my workflow:
|
@pajtai because that's not documented... |
@Announcement, can you clarify exactly what behavior is undocumented? Is it the ability to browserify a project that |
I think it's implied from the homepage: http://highlandjs.org/
as in, saying it's for the browser and then showing an npm command implies it works with browserify, the way browserify is meant to work - by just requiring npms in on the browser. |
The doc also states "You can also integrate highland in your own browserify bundle using a classical browserify workflow, but this is beyond the scope of this documentation." |
Distribute the browserified module as part of the NPM package. Closes #309.
We use NPM to manage both Node modules and browser packages, instead of Bower.
It would be great if the
dist
folder could be distributed as part of the NPM package, instead of justlib
.The text was updated successfully, but these errors were encountered: