Please publish current version on npm

[wcamarao]

As the current one published is broken due to be missing at least 314785a

[wcamarao]

If not a big deal :) can you rename the project name in package.json to backbone-relational?

We're using the git path on package.json to get the latest for now but it's downloading as node_modules/backbone-rel

[DouweM]

There is no official Backbone-relational build on npm. There's backbone-rel maintained by @dvv and backbone-relational maintained by @kmalakoff.

So, @dvv and @kmalakoff Could any of you update your package?

[kmalakoff]

I'd be happy to update my version or to hand it off to Paul to maintain since I'm not aware when new versions of relational are released. I think Paul often makes updates to the Github repository without bumping the version number.

Paul, wanna take over 'backbone-relational' on npm?

[kmalakoff]

I've updated the unofficial npm backbone-relational on npm.

Paul, the offer stands for you to take it over. Alternatively, just drop me a line whenever there is a new version to release (I check back from time to time, but it is difficult to know when there are changes without a bump in the version number and like this time, I might be too slow for the community to catch a new release).

[DouweM]

/cc @PaulUithol

[PaulUithol]

@kmalakoff : I just pushed 0.8.0. I've changed the package name to backbone-relational; I think someone asked about that a while back. Will that be okay? If not, I can revert that part.

[kschzt]

@PaulUithol can't see 0.8.0 in the npm registry, only 0.7.0. Could you please publish it? cc @kmalakoff

[kmalakoff]

I've published 0.8.0 and I also needed to publish 0.8.0+ (under "0.8.0plus") to provide support for Backbone 1.0.0. When there is an official release of a compatible version, please let me know.

On Wed, Mar 20, 2013 at 7:30 AM, kschzt notifications@github.com wrote:

@PaulUithol https://github.com/PaulUithol can't see 0.8.0 in the npm registry, only 0.7.0. Could you please publish it?

— Reply to this email directly or view it on GitHubhttps://github.com/PaulUithol/Backbone-relational/issues/223#issuecomment-15178751 .

[PaulUithol]

Thanks. Yep, we're working on that; not quite there yet, but getting closer every day.

[PaulUithol]

@kmalakoff : could you publish 0.8.8 on npm please? Thanks!

[kmalakoff]

@PaulUithol after creating BackboneORM I no longer use backbone-relational so it would be great to transfer the npm package to you.

I've added you to the Github repo and I'm happy to add you as an owner to the npm package - just let me know your npm name (or sign up if you do not have one).

[kmalakoff]

OK. Done.

Paul, please send me your npm account when you get a minute so I can transfer ownership to you. Cheers!

[PaulUithol]

Thanks, I'll try to get that to work soon.. your lib looks pretty nice btw!

[gdw2]

@kmalakoff Can you add the license field to the package.json in your unofficial npmjs offering?

Just curious: Why is the package.json found through npmjs so different than the one hosted here in the github repo?

[kmalakoff]

@PaulUithol You now have collaborator access to the Github repo so you can update it the license file.

I just added you to the npm package as an owner. Can you please remove me as owner?

$ npm owner rm kmalakoff backbone-relational

@gdw2 If you think the package.json is different when installed through npm, it is probably just that npm inserts some extra information to record like which tarball it was installed from (plus they add the no readme message, etc). If it looks like something different than this, post me a copy to look at.

[dminkovsky]

@kmalakoff Thanks for your maintenance of the package, and collaborating with @PaulUithol in passing it on to him.

[gdw2]

@kmalakoff Here is the package.json as found in my node_modules directory after npm installing it. A few of the fields (keywords, optional dependencies, license) are different enough that I wouldn't think it's something that npm does.

{
  "author": {
    "name": "Paul Uithol",
    "url": "https://github.com/PaulUithol"
  },
  "name": "backbone-relational",
  "contributors": [
    {
      "name": "Vladimir Dronnikov",
      "email": "dronnikov@gmail.com"
    }
  ],
  "description": "Get and set relations (one-to-one, one-to-many, many-to-one) for Backbone models",
  "keywords": [
    "backbone-relational",
    "backbone",
    "backbonejs",
    "relation",
    "relational",
    "nested",
    "model"
  ],
  "url": "https://github.com/PaulUithol/Backbone-relational/",
  "homepage": "https://github.com/PaulUithol/Backbone-relational/",
  "repository": {
    "type": "git",
    "url": "https://github.com/PaulUithol/Backbone-relational.git"
  },
  "optionalDependencies": {
    "underscore": ">=1.4.4",
    "backbone": ">=1.0.0"
  },
  "lib": ".",
  "main": "backbone-relational.js",
  "version": "0.8.8",
  "bugs": {
    "url": "https://github.com/PaulUithol/Backbone-relational/issues"
  },
  "dependencies": {
    "underscore": ">=1.4.4",
    "backbone": ">=1.0.0"
  },
  "_id": "backbone-relational@0.8.8",
  "_shasum": "d2f0c3287d8913f3ac0626c372cb983100f8ced5",
  "_from": "backbone-relational@~0.8.8",
  "_npmVersion": "1.4.9",
  "_npmUser": {
    "name": "kmalakoff",
    "email": "kmalakoff@gmail.com"
  },
  "maintainers": [
    {
      "name": "kmalakoff",
      "email": "xmann.intl@gmail.com"
    }
  ],
  "dist": {
    "shasum": "d2f0c3287d8913f3ac0626c372cb983100f8ced5",
    "tarball": "http://registry.npmjs.org/backbone-relational/-/backbone-relational-0.8.8.tgz"
  },
  "directories": {},
  "_resolved": "https://registry.npmjs.org/backbone-relational/-/backbone-relational-0.8.8.tgz",
  "readme": "ERROR: No README data found!"
}

[kmalakoff]

Yeah, that is to be expected. npm adds on its own information; for example, the shasum or tarball would be used when you run npm shrinkwrap so it knows where to lock the version from.

@PaulUithol by the way, I've deleted my old github repository for npm-backbone-relational and assigned you ownership rights to npm publish. You should update your package.json in your repo and add the requested licensing information.

Over to you...

[PaulUithol]

Hi @kmalakoff, I've taken ownership of the npm package. Noticed the repo was gone indeed after getting the invite to take over ownership. Thanks for your efforts! I'm not sure what you mean by "requested licensing information" though?

[gdw2]

If he's referring to the licensing info I requested, it's already in the package.json, so I don't think any more action is necessary. On Aug 6, 2014 7:08 AM, "Paul Uithol" notifications@github.com wrote:

Hi @kmalakoff https://github.com/kmalakoff, I've taken ownership of the npm package. Noticed the repo was gone indeed after getting the invite to take over ownership. Thanks for your efforts! I'm not sure what you mean by "requested licensing information" though?

— Reply to this email directly or view it on GitHub https://github.com/PaulUithol/Backbone-relational/issues/223#issuecomment-51339084 .

[kmalakoff]

Right on. Good luck guys!