Skip to content

require emitter-component only#118

Closed
defunctzombie wants to merge 1 commit intosocketio:masterfrom
defunctzombie:patch-5
Closed

require emitter-component only#118
defunctzombie wants to merge 1 commit intosocketio:masterfrom
defunctzombie:patch-5

Conversation

@defunctzombie
Copy link
Contributor

It is confusing to have competing package managers within the same
require system. The rest of the code uses npm published modules; this
should too. We have tools which can bundle all of this properly
without resorting to source code confusion.

It is confusing to have competing package managers within the same
require system. The rest of the code uses npm published modules; this
should too. We have tools which can bundle all of this properly
without resorting to source code confusion.
@rauchg
Copy link
Contributor

rauchg commented Feb 18, 2013

emitter-component is legacy though. We can use the new NPM syntax for targetting a repo I think and call both emitter.

@rauchg rauchg closed this Feb 18, 2013
@defunctzombie
Copy link
Contributor Author

@guille using the npm syntax to target a repo sounds good. (It isn't that new, you can do git:// paths for a long time now.

I usually do the following format: git://github.com/user/repo.git#abcdef

Where abcdef are the commit hash of the version I want to use so that you don't go against master or some such.

I also wouldn't call emitter-component legacy really. That is the published name in npm which is currently the way people get all of these modules so being consistent is worth something there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants