Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Porting code to ES6
See original GitHub issueES6 has a number of advantages and could be utilized in both tests and source. What are your thoughts on porting some of the protoype-style classes over to actual ES6 classes using the babelify transform and running it over the lib code?
You can also use it for the admin React components as well.
Issue Analytics
- State:
- Created 8 years ago
- Comments:17 (7 by maintainers)
Top Results From Across the Web
Porting a Large ES5 JavaScript Library to ES6 Modules and ...
In internal engine code, all class names and constants need to be accessed via the pc namespace. This is because the internals of...
Read more >Porting your Javascript to ES6 - Medium
Your frontend code may be trickier. One thing you need to manage yourself is the ES5/ES6 divide. In theory, you should be using...
Read more >Top 7 ES6 features - Migrate your code from ES5 to ES6
In the following video I explain top 7 ES6 features. I write ES5 code, explain the change made in ES6 and convert the...
Read more >How to write Javascript in ES6 with Nodejs
Let's get started ... The usual stuff, create a new folder to house our code and change directory to the folder. ... Use...
Read more >Migrating old-style JavaScript code to ES6 - Pejibaye Blog
Once I ran the build and the tests and everything looked good, then it was time to really port our code to ES6....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@cameronroe we’re going to launch the next version (0.4) with no babel build process for the server-side code (for simplicity), then drop support for node < 4 in one of the next significant versions so we can use ES6 natively. IMO the new versions of node with ES6+ support have been out long enough for that to be reasonable.
On a related note, 0.4 has ended up basically a complete rewrite, which has given us a much more robust architecture as well as the new React Admin UI, while at the same time we’ve been held back from making some big calls because I want to preserve as much backwards compatibility at the same time (not wanting to introduce unnecessary breaking changes AND rewrite in parallel, or we’ll make upgrading too risky).
Once we’re through this, the next few versions should happen much more quickly.
I’ll close this issue since Jed outlined everything perfectly above 👍