@brody4hire - C. Jonathan Brody
@brody4hire - C. Jonathan Brody
@jasongin - thanks in advance!
I think this needs better promotion, somehow. It is the only form of Node.js version manager I have seen that works the same way between cmd, PowerShell, bash, etc. etc.,...
I would like to be able to install `nvs` in an arbitrary location, which would be a user-owned subdirectory of `/usr/local`, and *manually* update `$HOME/.profile` _(I do not care about...
Discussion in https://github.com/nodejs/version-management/issues/13 I hope `nvs` will work with standard Node files since it is the only Node version manager I know of that is truly cross-platform. _P.S. Yes it...
When I tried nvs rm with multiple version numbers it only removed the first one and ignored the rest. It would be better for nvs rm to show an error...
In general I think this is really awesome work and will do as much as I can (within reason) to promote it. That said, I suspect it should be possible...
I really like the advantages this framework has to offer in terms of eliminating the performance/complexity/interop costs of a virtual DOM but think this needs to be made much more...
Use npm prepare script to generate needed objects before publishing. For example: - - I would be happy to help with this one if you like. Maybe within the next...
I am curious if anyone thought about how this wonderful library might be used with custom elements, etc. I am thinking in comparison to react, as in a few articles...
- [ ] drop support for Node.js ~~pre-6.0~~ __pre-8.0 / pre-10.0__ _- likely in a new `engines` field in `package.json` (PR #443)_ - [ ] update `coffeescript` and _some_ other...