Open jderus opened 6 years ago
It's supposed to, but Angular/Webpack introduced some changes that break existing dependant projects, including this one.
I'm not sure what the fix is for #5. I tried a few vague proposed solutions, but I was unable to get a definitive success.
I would love to get it fixed, but I'm going to need some help with that because honestly, I'm still having trouble understanding the whole "the request of a dependency is an expression" situation. That zombie thread you mentioned is all over the place as well.
Yeah, that thread is definitely all over - which should be a good clue that webpack errors could be more robust :) My bigger concern here is why I don't seem to be pulling down a version with Angular 6 and the changes to RxJs. Is something more recent not published up to npm? (I see that your versions in package and package-lock do not match 1.1.0 and 1.2.1).
FWIW, my hack was simply a change in the import statements in core/esm5/core.js:
import { __assign, __extends } from 'tslib';
import { Observable } from 'rxjs';
import { merge } from 'rxjs/operators';
import { share } from 'rxjs/operators';
import { Subject } from 'rxjs';
import { Subscription } from 'rxjs';
Since I liked it so much in Angular 4-5, I was attempting to use this package (v1.1.0) with Angular 6x (core: ^6.0.3, cli: ~6.0.8, rxjs: ^6.0.0). I got the following:
Here is what I saw in my package-lock.json file:
That didn't seem to match the 6.0.3 core in the repo package.json.
To me, this looked like breaking changes in rxjs as of 6x, so I quickly hacked the imports in node_modules to see if it would mitigate. That got everything to build, but then I encountered: #5
This seems to be related to this zombie thread here: https://github.com/webpack/webpack/issues/196
Should we be expecting 1.1.0 to work with Angular 6 out of the box?