> Any other answers to my original question?

put it on npm. Have your users install it from npm and then use it with a
commonJS compliant tool like browserify.

If you really want to support everyone I recommend you use `browserify
--standalone` and put that code in `dist/my-lib.js` on github or your
website. `--standalone` generates UMD and works with everything.


On Thu, Jul 18, 2013 at 6:34 PM, Ryan Schmidt <[email protected]>wrote:

> On Jul 15, 2013, at 00:26, Hage Yaapa wrote:
> > On Mon, Jul 15, 2013 at 6:50 AM, Ryan Schmidt wrote:
> >> On Jul 14, 2013, at 12:21, Hage Yaapa wrote:
> >>> On Sun, Jul 14, 2013 at 4:25 PM, Ryan Schmidt wrote:
> >>>
> >>>> It appear to require that I publish my source on Github?
> >>>
> >>> Not at all. Component can do many things apart from creating modules
> for the front-end. Here is a tutorial I wrote specific to for front-end
> components -
> http://www.hacksparrow.com/loading-javascript-modules-in-the-browser-with-component-js.html
> >>
> >> Thanks for that detailed tutorial; that's very helpful. But doesn't it
> confirm what I said?
> >>
> >> The tutorial shows running "component install yields/capitalize".
> That's https://github.com/yields/capitalize.
> >>
> >> How would I allow others to install my library by running "component
> install ryandesign/mylibrary" without having to host it at
> https://github.com/ryandesign/mylibrary?
> >
> > Oh, for others to install you will need to put in on a public repo. I
> haven't looked into using SVN. You can ping TJ Holowaychuk, the author, on
> Twitter, if he hasn't noticed this post already.
>
> After a lengthy email discussion with TJ, he confirms that yes, my
> library's code must be in a git repository on github for component to be
> able to get its files. If I want to host my development repository
> elsewhere, as I currently do, that's fine, as long as I copy the code into
> a git repository on github to make it available to component. Which is a
> little like saying that I have to have Brussels sprouts for dinner, and if
> I don't like Brussels sprouts that's ok, I can eat whatever I want for
> dinner, so long as I have Brussels sprouts for dessert.
>
> It's unfortunate that such a cool idea, whose goal is to be unopinionated
> about JavaScript DOM frameworks, is instead opinionated about where and how
> code should be hosted online.
>
> Any other answers to my original question? Or is component the consensus,
> and I just have to deal with this?
>
> --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to