Specify deprecation notice in rxjs-es package

[kwonoj]

RxJS version:
b.12

Code to reproduce:
https://www.npmjs.com/package/rxjs-es

Expected behavior:

Actual behavior:

Additional information:
Currently rxjs-es package is stay there with last available (b.12, https://www.npmjs.com/package/rxjs-es) , and there isn't any update further since newly published package won't include any ES2015 packages. NPM no longer allows delete package so anyone search npm packages can find, install unsupported package. While it is not available to remove packages, at least it is possible to specify given package's deprecated and not recommended to use - such as ghooks does recently (https://www.npmjs.com/package/ghooks), by publishing one dummy package with deprecation notice.

Thoughts? /cc @Blesh, @jayphelps .

[jayphelps]

Npm still supports the deprecate command, I believe? It would then warn the user when they install. Ben will have to do it I think.

[kwonoj]

If that's supported, that's good 👍

[aluanhaddad]

👍 for npm deprecating this if it is indeed abandoned. I still see recommendations to use rxjs-es with Rollup fairly often. It is confusing.

[alex-kinokon]

The official documentation still recommends installing rxjs-es. Perhaps time to update the docs?

[jayphelps]

@benlesh ^^^ they just need to be published

[benlesh]

@jayphelps I think what's in master would be in a bad state for publishing docs just now because of the extra docs around the new lettable operators. Once we get that fixed, I'll republish the docs.

[jayphelps]

@benlesh could you checkout the commit before the stuff you don't want, then publish from there?

[benlesh]

@jayphelps .. I could... might be a bit of digging.

[benlesh]

Closing this. I don't think this is any longer an issue.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.