Closed joemphilips closed 6 years ago
That looks like a duplicate xstream installation. Can you run npm ls | grep xstream
and see if you have other versions than 11.2.0?
Thanks for fast response.
by running yarn list | grep xstream
result was
│ │ └─ xstream@10.x || 11.x
│ └─ xstream@11.x
│ │ └─ xstream@10.x || 11.x
│ └─ xstream@11.x
│ └─ xstream@11.x
│ └─ xstream@10.x || 11.x
│ │ ├─ xstream@10.9.0
│ │ └─ xstream@10.x
│ └─ xstream@*
│ └─ xstream@^11.2.0
│ └─ xstream@>=10
│ ├─ xstream@^10.8.0
│ └─ xstream@10.9.0
│ └─ xstream@>=10
│ └─ xstream@^11.2.0
│ ├─ xstream@^11.2.0
├─ xstream@11.2.0
and the package which rely on only version 10 was
@cycle/time@0.8.0 -> @cycle/run@1.0.0
and
cycle-restart@0.2.3
I found that latest release of cycle-restart
has not yet included this patch.
So I'd better use build from the master branch in cycle-restart
and this should be fixed.
I really don't know what is the best way to use those unpublished version directly from the github, though.
By the way, thanks for this great library!
Yep. I released the new version of cycle-restart
for myself and the issue has fixed. So closing now. thanks again!
in xstream version
11.2.0
, when I triedI get the following error in.
I found this when I tried to use HTTPDriver in cyclejs, because it requires to
flatten()
the response. and it has a same signatureI workaround by casting it to
Stream<any>
, but of course this is not Ideal. Please tell me if I'm missing something. Thanks!