Strange parser error when an `if` statement is at the top of an async arrow function about parse-function HOT 8 CLOSED

Well it's your patch. I look forward to the upcoming release 👍

from parse-function.

🐯🐯🐯🐯🐯🐯🐯🐯

from parse-function.

Hey there! 👋 Thanks for the report, it sounds me like problem here.
I bet it's because of this here src/index.js#L106-L113.

The idea about that if there, is if we have passed async method, then we should wrap it in object, so the parser can parse it correctly.

Can you try to add this check too and try again if it works

const isAsyncArrow = result.value.startsWith('async')

if (!(isFunction || isAsyncFn || isAsyncArrow) && isMethod) {
  result.value = `{ ${result.value} }`
}

Another reason and probably limitation is that we use babylon.parseExpression by default here, but as i remember, it was intentional.

from parse-function.

@charlike The patch works for me 👍 Thank you for the quick turnaround on that!

from parse-function.

Sweeeet! :D I love myself sometimes for such fast responses with good end :)

PR is welcome, otherwise i can push patch in coming days. Let me know if you need some help on contributing.

from parse-function.

@the1mills what? 😹 haha

@TooTallNate actually, yea, but it's not a problem for me. Go pr if you need it more soon.

from parse-function.

Please see #63.

@charlike P.S. I'd be happy to be added as a contributor, if this module has become a burden on your time.

from parse-function.

heya, just seen your comment here.

if this module has become a burden on your time

no, it's not, just i'm in period of switching ISP providers and following through smartphone is hard, haha.

i'll add you once I get stability and time, no problem :)

from parse-function.