Not getting cosmosDb module on npm install about azure-database

[manekinekko]

Thank you @bstrobach and @andreea96 for reporting this issue.

@kamilmysliwiec could you cut a new 2.0.0 release for npm?

[dinohorvat]

Since we are still waiting for this, I forked this repo and created a new npm package from it.

https://www.npmjs.com/package/@dinohorvat/azure-database

npm i --save @dinohorvat/azure-database

You can now import Cosmos correctly. When the fix is out, and this issue gets closed, switch back to the official npm package.

[bstrobach]

Same here. Cosmos modules are missing.

Maybe @manekinekko can help out?

Edit: I just saw this comment - comparing to the sources on npm, this is still the case.

@andreea96 If this is still relevant: For now you can directly link to the master branch of this repository:

package.json
...
"@nestjs/azure-database": "github:nestjs/azure-database#master",
...

[Dhiraj-JC]

Thank you @bstrobach and @andreea96 for reporting this issue.

@kamilmysliwiec could you cut a new 2.0.0 release for npm?

yes that will be great help.

[TheAvalanche]

Waiting for it very much, too! :)

[manekinekko]

@abouroubi I am sure Kamil is doing his best to maintain the Nest.js project and libraries. The current global pandemic situation has been tough for everyone. Please be patient!

In the meantime, you can install or update your package.json file to install this package from the master branch:

npm i -S github:nestjs/azure-database#master

Or update package.json:

"@nestjs/azure-database": "github:nestjs/azure-database#master",

Cheers.

[kamilmysliwiec]

If you don't have enough time to wait till the release gets published, create a fork in your repository @abouroubi. Your projects !== our/mine responsibility.

2.0.0 just got published.

[abouroubi]

Hi guys,

Is the project dropped ? It's been a year that I sent the PR to add CosmosDB support and it can't seem to be released on NPM yet.

@kamilmysliwiec it looks like you are the only one able to push a release to NPM, but didn't have the time to do it, I understand you have a lot on your plate with main NestJS repo, but if you can't manage this repo under the official @nestjs maybe you should drop it and let the community take care of it.

[jasperrosiers]

This issue is still here for me as well!

[manekinekko]

We are looking at this issue. Thank you all for your patience.

[manekinekko]

Thank you @dinohorvat for stepping in and offering your help. I appreciate it.

Hey @kamilmysliwiec @MarkPieszak can you guys cut a new 2.0.0 release for npm? This is becoming critical!

[murbanowicz]

@kamilmysliwiec @MarkPieszak - anything? It looks like it is just a matter of releasing to npm. It's a pretty useful module, which currently is not usable :/

[abouroubi]

@manekinekko I don't doubt that, and I'm really grateful for what he is doing to the community. My only regret is that he maybe taken responsibility for too many projects, and he should delegate a little bit.

Thanks for the advice, but I already have published a version to NPM that I'm using on my project.
I would not recommend pointing to a GitHub branch in a production project, due to the fact that it can introduce breaking changes.