async/await support in live editor
See original GitHub issueI’m not sure whether async
functions should be working in the LiveEditor
or not, but when I have that syntax, I get this error in the LiveError
:
“SyntaxError: Unexpected identifier”
I couldn’t find any documentation or issues regarding this.
EDIT:
It appears this works:
async function loop(next) {
But this syntax does not:
async next => {
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:8 (4 by maintainers)
Top Results From Across the Web
docusaurus: async await in examples with live editor
throws a runtime error in the live editor CompileError: Transforming async functions is not implemented. Use `transforms: { asyncAwait: ...
Read more >Async/Await callbacks | Intro.js Docs
Async /Await callbacks. Intro.js main functions to start/stop a tour return a Promise object. You can also return a Promise object in the...
Read more >[SOLVED] Using async/await inside initialize()
Hi, I'm trying to set up a PlayCanvas project that talks to a Nakama server for realtime multiplayer functionality.
Read more >Making asynchronous programming easier with async and await
First of all we have the async keyword, which you put in front of a function declaration to turn it into an async...
Read more >Async/Await in Editor script?
The continuations are accumulated but never get executed, except the moment when the editor starts script recompilation process. In this example ...
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 FreeTop 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
Top GitHub Comments
@tcc-sejohnson we’ve re-tagged
react-live@latest
to be3.1.1
(thanks for the tag @gksander !)@ryan-roemer Thanks for the quick response 😃 Yes, that does fix it – yay! Is it just a prerelease version? Any idea when we can expect 3.1.1 to go live?