Is Lebab a tool for real world?
See original GitHub issueConsider I have a very simple code using a namespace to bundle functionality under a name. I try to turn this code to ES6 using Lebab and I expect to see some classes but it seems Lebab fails to transpile this code (I saw this is a known issue #113 ).
Namespaces are a very common pattern, so what is the goal of using this kind of tools when they fail to provide new modern features of ES? I think very basic operations like changing var to const, removing “use strict” directives and etc. are not enough to use these kind of tools to transpile a real code. This not the only snag or limitation, consider a ES6 Code without Reflection, Proxying and etc…
**` var Bamblip = { Message: ’ ', };
Bamblip.Init = function() { Bamblip.Message = 'Hello '; };
Bamblip.Welcome = function(name) { Bamblip.Init(); alert(Bamblip.Message + name) }
Bamblip.Welcome(‘Bamblip’); `**
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:10 (4 by maintainers)
Top GitHub Comments
You need to know that:
But what you mean by a modern code in “real world”? Let’s say we have this code:
It uses promises. Do you think this is a modern code?
But what about this one?
Wait! What about this?
So I think you’re expecting Lebab something that is not supposed to do.
The answer is “YES”. I think we’re living in a world that Lebab is doing what it has to do.
I hope it eases well! 😉