Closed gaearon closed 10 years ago
Yep, as soon as package is fixed, I'll publish it up
Probably later tonight
There's also a different problem: peerDependencies
locks down Backbone at a specific revision, while I want to use a newer version. Since this is not expressible with git://
scheme, perhaps we could leave it as *
and make it ^1.1.3
as soon as it gets released?
Suggestions? I know peerDependencies is frowned upon these days...
I'd just leave it as *
and make sure it's documented.
Published to npm and fixed packaged deps https://github.com/akre54/Backbone.NativeView/commit/f0314bf76dfc7fafa4028e8902fadf960ee9fd2f
This repo does not appear to be registered on NPM. Would you mind doing it? Putting Github repo url in
package.json
feels.. wrong.