Unexpected Token async function
See original GitHub issueDescribe the bug Upgrading strorybook@3 to latest version gives the following error Bug in @storybook\core\dist\server\build-static.js:31
async function Unexpected Token
As i am using node 6.9.1 and async support is from node version 7.4 So its node compilation error.
Expected behavior package.json should have “engines” https://docs.npmjs.com/files/package.json#engines
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (5 by maintainers)
Top Results From Across the Web
SyntaxError: Unexpected token function - Async Await Nodejs
I have no clue why, the terminal throws up an error when I try to execute the node code. helloz.js (async function testingAsyncAwait()...
Read more >Unexpected token error after adding await keyword to Node.js ...
Dylan Sather (Pipedream) : Hi , getting used to async / await and asynchronous programming in JS can take a long time even...
Read more >SyntaxError: Unexpected token function - Async Await Nodejs
JavaScript : SyntaxError: Unexpected token function - Async Await Nodejs [ Gift : Animated Search Engine : https://bit.ly/AnimSearch ] ...
Read more >SyntaxError: Unexpected token - JavaScript - MDN Web Docs
The JavaScript exceptions "unexpected token" occur when a specific language construct was expected, but something else was provided.
Read more >Async unexpected token function - App Platform
I'm writing a client side app for freshworks crm. I'm getting error on pack and validate. Its been running fine with “fdk run”...
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
@ndelangen He knows what the problem is, he’s saying we need to update our package.json to document the incompatibility.
Ooh-la-la!! I just released https://github.com/storybooks/storybook/releases/tag/v5.1.0-rc.0 containing PR #6809 that references this issue. Upgrade today to try it out!
Because it’s a pre-release you can find it on the
@next
NPM tag.Closing this issue. Please re-open if you think there’s still more to do.