2013/5/26 Eldar <[email protected]>:
> I migrated to components for both client and server side, though my
> motivation is different:
>
I don't want this thread to turn into npm vs component design, just
fix discoverability for those who prefer gh paths is sufficient.
> 1) node_modules is a weak structuring pattern
>
> The most common approach for applications is to have a bunch of local
> modules without package.jsons and a huge root
> package.json with all external dependencies listed here. But it's obviously
> better to have even local modules to be completely specified and
> independent.
> Though you can do that there are still rough unrounded corners. For example
> it's hard to use two versions of the same lib in one app (say slow migration
> to a newer version with API changes). There are other unfortunate points -
> runtime overhead, specification of dependencies is not forced, etc.
>
> 2) component.json is just better
>
> What I mostly like about component.json is that it requires explicit listing
> of all assets. I found my .scripts array to be constantly simpler,
> containing fewer entries than a properly configured .npmignore (which is
> overhead and complexity by itself)
>
> 3) components are better for browser and other environments
>
> As a consequence of better design component system is much easier to
> implement and use for browser, chrome apps and any other environment. With
> time the difference between them becomes more and more obscure. For example
> many node specific objects and modules like Buffer, fs, etc are already
> available on browser. We already have a lot of code making sense for both
> client and server with time everything will work everywhere. That means we
> need a common package format for the whole web. Component is a better
> candidate for such.
>
> 4) npm register is hard to setup
>
>
> On Saturday, May 25, 2013 10:49:09 AM UTC+4, stagas wrote:
>>
>> Hi all,
>>
>> I really want to name my modules however I like and be installable and
>> require-able.
>>
>> For example, I want to write a 'merge' utility, and I don't want to
>> struggle coming up with a random set of letters because I want my code
>> to read require('merge') not require('golalamergifiable').
>>
>> What are my options currently? Anyone have any solutions?
>
> --
> --
> 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.
