Rxjs: Problem with rxjs in last days?

[montella1507]

Hello i would like to ask you for help, because it could be a bug in rxjs?

My switchMap operator does not behave as it behaved 2 days ago (only node_modules reinstalled yesterday):
https://github.com/angular/angular/issues/19799 (Minimal reproduction repo included.)

Thank you for your answer.

[TomasRup]

Same here. We were using "^5.4.1", changed to "5.4.1", now it works.

[montella1507]

I will try to pin version to 5.4.3 (we have ^5.4.3 in package.json ) so we may have installed version 5.5.0 and there may be bugs...

[montella1507]

I can propably confirm it works with version < 5.5.0 .. with 5.5.0 even the primitive Observable.of(value).switchMap(data=>..) doesn't work..

But let me try it again to be 100% sure.

Any author here?

[montella1507]

OK. i can confirm.

< 5.5.0 works
5.5.0 errors in rxjs namespace

[stas-kh]

Guys, we have the same problem with 'forkJoin' in our app that uses Angular 4 and RxJS.
We fixed the version 5.4.3 in package.json as a temporary fix.

[evestraw]

i think 5.5.0 should be released as 6.0.0 because of breaking changes

[montella1507]

Yeah.. that is the one of the biggest problems of NPM+javascript...

1) Source-code distributed submodules of submodules of...
2) No idea about semver of developers
3) Range versions
:-(

It tooks 50% of developing time on fixing bugs in dependencies..

[jayphelps]

Hey all, I'm not a maintainer, but could someone include the text of the error they are actually getting? https://github.com/angular/angular/issues/19799 doesn't include the error either.

[benlesh]

These are unforeseen breaking changes, and they will be fixed. This issue appears to be a duplicate of #2984.

I can see a lot of people are frustrated, my sincere apologies for any problems this may have created. If you hit this issue for now just pin to 5.4.

I'm closing this as a duplicate, but rest assured we will fix it.

[montella1507]

Your work is very appreciated. Thank you.

[lock[bot]]

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.