maritz

For some reason that doesn't work for me anymore now. Now I had to add this to my tsconfig.json: ``` "ArcticTypescript": { "node_path": "/home/developer/.nvm/versions/node/v0.12.3/bin/node" } ```

Any specific reason you want to use this deprecated module still? I'm not opposed to your change itself, I just don't thing it's actually needed.

Okay, but if dependencies are locked down, how is changing a dependency version gonna work? If you can change to the other package, I strongly advise you to do so.

Another more "atomic" way would be to create a lock immediately on remove and then do a more costly SCAN iteratively. Also possibly removing the on-instance .remove() in favor of...

Same problem as #104 I think this should be converted into a new feature for v2.x (probably 2.2 or 2.3), instead of attempting to put it into v0.9 and then...

Travis was borking, had to close/reopen.

@sam2x before you do that: I will not pull this into the 0.9.x branch, I think. So it'd have to be re-written in the 2.x branch.

I've been using v2 in my own small projects, so I'd say it is mostly usable. There are a few things not yet implemented properly in v2, like custom validation...

> Do we already have this feature in v2? No. This PR would have to be converted to typescript and included into the current code. I'm also not sure if...

Maybe the example isn't quite clear here, since its only supposed to show the typing stuff, not how to generally use nohm. I'll look into fixing that. nohm.register returns the...