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.
Prepping for ES8 Changes
See original GitHub issueAsync functions are a finished proposal and will be in the ES2017 spec. There are a couple of other interesting items I’d like to work on (though they probably won’t make it to ES2017).
My team is allowed to use any feature at Stage 3 of the proposal process or higher: https://github.com/tc39/proposals
Is there a plan for handling this?
I was considering adding an ECMASCRIPT8 and ECMASCRIPT8_STRICT language level. But for features which weren’t yet in any formalized spec, I was considering adding ECMASCRIPT_NEXT which is consistent with Babel.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I am, in fact, very close to having the async functions transpilation working. They’re working in not-yet-submitted code now.
What are these object rest/spread parameters you mention? I thought we were already transpiling all of the rest/spread stuff. Could you give me an example?
ECMASCRIPT_NEXTwas added.