You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[LINK TO FEATURES](https://github.com/mean-expert-official/loopback-sdk-builder/wiki#features)
27
27
28
-
# FireLoop API (NEW)
28
+
# FireLoop API (NOTICE)
29
29
30
-
Are you willing to build pure and modern Real-Time applications?? Then [CHECK THIS OUT](https://github.com/mean-expert-official/loopback-sdk-builder/wiki/8.-(NEW)-FireLoop-API)
30
+
I want to notify all the users of FireLoop that result of the complete refactor in LoopBack 4, the real-time platform we love, will suffer a complete and imminently refactor as well.
31
+
32
+
The current version of both the `loopback-component-realtime` and the `loopback-sdk-builder` (main components in FireLoop) are stable and I personally will continue to keep fixing upcoming bugs and mainly coordinate community contributions for new features and bug fixes.
33
+
34
+
But the new development efforts will be focused on what is coming next. All the components that compose FireLoop will be written from scratch adopting the new LoopBack 4 architecture.
35
+
36
+
# Coming Next
37
+
38
+
I know it's difficult to hear that your framework is being refactored from scratch, being even more difficult to understand that modules and projects will suffer the same effect.
39
+
40
+
But after I started working in my first LoopBack 4 module (gRPC Support for LB4) I really feel this pain will be left behind and we will end with a much better platform to work on.
41
+
42
+
What is coming next:
43
+
44
+
- LoopBack 4 compatible SDK Builder (For Back and Front ends gencode).
45
+
- 100% TypeScript support (Back and Front ends).
46
+
- Framework agnostic typed and pluggable SDK (Angular, React, any).
47
+
- New real-time protocol using HTTP2 (gRPC).
48
+
- Compilable and npm publishable SDKs.
49
+
50
+
# Disclaimer
51
+
52
+
I have been off the media for some time now, it was difficult first to understand the upcoming changes, and second, how would these affect the ecosystem around LoopBack.
53
+
54
+
I needed to have clear what is coming next and be sure the position I needed to take, make some desitions.
55
+
56
+
Now that I'm clear on the upcoming changes and I got down to work on my first LB4 real-time module, I'm able to start communicating more often as I used to before.
57
+
58
+
I will start my blog series from scratch based on LoopBack 4 within the following weeks.
0 commit comments