Potentially stupid question: is there a tool that can show you where in the code a parser error happened? I run into this a lot when refactoring code, where I end up with a parser error which prevents Prettier/TS etc from running. It takes a lot of effort to locate the problem.https://twitter.com/acemarke/status/1174356298227490816 …
-
-
Replying to @OliverJAsh
Not something already available but I think
@sebmck’s Rome is supposed to give better errors when that happens1 reply 0 retweets 4 likes -
Replying to @dan_abramov @OliverJAsh
Yep. There's dedicated error messages for every single possible syntax error, no more "Unexpected token". Some errors also use other contextual and token information to provide suggestions if it thought you meant something else.
1 reply 0 retweets 16 likes
Specific issue here seems to be excessive curlies? When Rome expects a closing character, like } or ], then it will also point to the location of the opening character that made it expect it.
12:49 PM - 18 Sep 2019
0 replies
0 retweets
12 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 