make package.json editable, especially for version numbers about requirebin

[Raynos]

Thanks.

I will look into a PR for this

[max-mapper]

@Raynos you can try editing the package.json via the gist.github.com interface, and then reloading requirebin. there may be a bug there though, which is that I am not sure if the loading of cached modules (stored in indexeddb with level.js) will trigger cache misses if the version in package.json is newer than what's cached. that might be a good place to start if it doesn't do it already

[kirbysayshi]

@maxogden what do you think about allowing require within requirebin to do this:

var somepackage = require('[email protected]');

Perhaps it could either be a runtime check (find requires, then parse out possible @ when requesting deps) or whenever it's present in a require statement, it's used to update the package.json file but is stripped out when saving the actual file.

[max-mapper]

i'd rather have it be in some UI on the side, that way code is compatible with normal browserify/node usage

[kirbysayshi]

Cool cool, makes sense. Was just batting around the idea to keep the ui as minimal as possible.

[mauriciopoppe]

@maxogden package.json is now editable since #74, and modules are saved in the cache in the form module@version, e.g. [email protected] since max-mapper/browser-module-sandbox#11. There's the latest version bug on bundles (browserify/wzrd.in#75) which is not part of this issue, any objection to close this one?