New Release?

[ssbyoung]

Looks like there's been quite some time between the latest commit (10/16/2018) and the latest release (6/1/2015). Any chance we can get all of those commits released to an npm version?

Thanks.

[boussou]

true. You can also try Epoxy, a bit heavier but very useful.

[ssbyoung]

@boussou respectfully, I'm not interested in upgrading my legacy application to use another library.

For those finding this later. I ended up pointing my npm to the latest commit in this repo:
in package.json

"backbone.modelbinder": "git://github.com/theironcook/Backbone.ModelBinder.git#fe4015ec7b6f3472fdddb6679f7b6d83ef56b2b6",

[theironcook]

I'm sorry @ssbyoung - I've been pretty negligent on this project due to time constraints. Is there any chance you could help me generate a new release and have it published to npm? I could give you rights to the project if necessary.

[ssbyoung]

@theironcook Sure. Give me the permissions and I'll cut a new version.

[ssbyoung]

@theironcook can you take a look at #236 to see if I missed anything before going forward? Right now I'm thinking about having this be a patch release.

[ssbyoung]

@theironcook looks like I was able to publish the package on github but not on npm. My npm account does not have the permission to publish.

Judging by https://docs.npmjs.com/cli/owner , it seems like you would need to do something like

npm owner add ssbyoung backbone.modelbinder

thanks!

[ssbyoung]

@theironcook any chance to get npm permissions? Alternatively you can do npm publish if you're on the latest.