-
Notifications
You must be signed in to change notification settings - Fork 4
RxJS 5.5.0 ... and new lettable operators #4
Comments
@mlc-mlapis Thank you for this interesting question. Over here at Oasis Digital, we have been using the new lettable operators already. I like the new syntax quite a lot by the way. The problem you're describing, is a problem I need to solve for the materials we use in our Angular classes. When (if) I have a solution, I will post it here when I figure it out. I have an idea, it might involve generating the missing file. I believe the RxJS team has been going back and forth about exactly what what should be included in the distribution, to enable optimized use (without bringing in too much code) for different scenarios. The answer they have is probably optimized for MPM. So we might need to do something slightly hacky to get great results with System. |
@mlc-mlapis I was able to build with exactly the same system bundle commands as before, by using a bit of script to fill in the "missing" I'm using the same workaround in the materials we use to teach our class (Angular Boot Camp). In class we find it very convenient to work in the browser using SystemJS, but it is important to type exactly the same code that we would type in a Angular CLI application. So far it appears that this workaround achieves that. |
@kylecordes ... yes, it is the right way till RxJS team will introduce version 5.5.1 with their solution of the same. They are aware of the problem already ... ReactiveX/rxjs#2971 Thank you very much for your time. |
angular 5 support ngrx4 or not? |
Hi Kyle, @kylecordes, I am trying to solve a new problem with RxJS 5.5.0 and its new lettable operators.
Actually just simple GULP script produces the following problem:
It is probably related to
defaultExtension
becauseoperators.js
doesn't exist in reality just the directory and these lines inRx.js
on 191-192:Do you have any idea how to solve it by the simplest way? I guess that the problem is the same even for
rxjs-system-bundle
.The text was updated successfully, but these errors were encountered: