diff options
| author | isaacs <i@izs.me> | 2010-03-04 01:52:44 +0300 |
|---|---|---|
| committer | isaacs <i@izs.me> | 2010-03-04 01:52:44 +0300 |
| commit | 58c06d864b13ba42875121be1977db1e8519b53b (patch) | |
| tree | ec320dbf094be1a624f4f44f570e121bf4a52f9a /README.md | |
| parent | 574663dfad1527d2bff4d41800e1277930862e8f (diff) | |
Remove the todo
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 1 |
1 files changed, 0 insertions, 1 deletions
@@ -112,7 +112,6 @@ All the "core functionality" stuff above. Most immediately: * Safely uninstall packages, failing if anything depends on it. * Install packages from the registry. Implement a "fetch" command that writes to `.npm/{pkg}/{version}/package.json`. * Install missing dependencies. For each one, fetch it, then figure out what it needs, then fetch that if we don't already have it, etc. Put off the resolveDependencies step until everything on the todo list has been installed, then go back and do the dependency linking. -* Install a link package from a folder. (Rebuilding and installing npm every time I make a change SUCKS.) It would be fine to just fs.symlink from the "package" folder to the folder being installed, and then read the package.json out of there, and do whatever. It might be good to have the fetch/unpack stuff in "install", and create a separate "link" command, and then have both call a "build" command. This way, I could factor a bunch more junk out of install.js. Some "nice to have" things that aren't quite core: |