Skip to content
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.

Sign up for GitHub

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

Jump to bottom

npm #6

Closed
nickl- opened this issue Aug 4, 2012 · 2 comments
Closed

npm #6

nickl- opened this issue Aug 4, 2012 · 2 comments
Milestone
Version 0.1

Comments

@nickl-
Copy link
Member

nickl- commented Aug 4, 2012

No current implementation

Should we differentiate between local and global?

This task needs to be completed as part of milestone Version 0.1 see #2
@alganet
Copy link

alganet commented Aug 6, 2012

We could search for a package.json file (including parent directories, just like Git does with it's folder). A switch for local/global (just like the npm's -g option) could be useful.

@nickl-
Copy link
Member Author

nickl- commented Oct 20, 2012

Npm has been enabled with initial support for commands

  • search
  • update
  • install

I'm closing this issue we can raise new ones.

global local could be addressed with pass through attributes perhaps

@nickl- nickl- closed this as completed Oct 20, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Version 0.1
Development

No branches or pull requests
2 participants
@alganet @nickl-