Skip to content

package.json #8

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

Merged
merged 1 commit into from
May 6, 2011
Merged

package.json #8

merged 1 commit into from
May 6, 2011

Conversation

arlolra
Copy link
Contributor

@arlolra arlolra commented May 6, 2011

if i'm going to work on getting haraka into the npm registry, a package.json is a good place to start

baudehlo added a commit that referenced this pull request May 6, 2011
@baudehlo baudehlo merged commit 12348f1 into haraka:master May 6, 2011
@baudehlo
Copy link
Collaborator

baudehlo commented May 6, 2011

OK merged and closed - but can cluster be made into an optional dependency, or does npm not support that?

@arlolra
Copy link
Contributor Author

arlolra commented May 6, 2011

optional dependency, that sounds like a bit of contradiction in terms.
npm man json does not list any sort of optional or add-on package field.

i guess you can remove it if it bothers you.
but, although haraka isn't strictly dependant on it, i don't see the harm in installing it.
can't be more than a couple kb.

@baudehlo
Copy link
Collaborator

baudehlo commented May 7, 2011

Well perl's CPAN stuff has optional dependencies and it allows you to provide a prompt which says "X is optional and provides feature Y. Do you wish to install it now? [Y/n]"... Just thought there might be something like that.

No there's no harm in forcing it to be honest. I'll just apply the pull request.

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