-
Notifications
You must be signed in to change notification settings - Fork 304
Resolve name
as name/name
.
#586
Comments
@antaranian Expanding Note however that your motivation is based on some false assumptions I think. You do not need to do this:
component knows how to resolve just this:
The only time you would need |
If @jonathanong is cool with it @antaranian feel free to submit a pull-request. You basically just need a small pure function. Also while we're on this topic here are other wacky possibilities:
Personally I don't need this stuff, just sharing. |
@jasonkuhrt the comma thing seems silly, as brace expansion already works ;)
|
@stephenmathieson Yup! 👍 |
Wandering if it's more Spec's related and depends on decision guys will make on componentjs/spec#52, as this change may or may not involve changes to dependencies section in manifest file? |
i don't really see the point since the cases where this would actually be useful is very few |
it's also needlessly ambiguous |
Resolve main repository in organization, when only org-name is provided, where main repository is the one with the same name as organization.
E.g.
should be equivalent to:
Same should work with
require
, likerequire('moment')
.While using in conjunction with naming conventions introduced by Component v.1 all parties (publishers and users) can release and "require" modules without naming differences across Component and npm.
And
require('name')
looks better thanrequire('name-name')
I think.The text was updated successfully, but these errors were encountered: