ref: Switch JS parser from rslint to swc

[Swatinem]

The rslint parser is unmaintained and has a hard limit on how much code it can parse.

This changes the internal parser so swc, which is maintained and production ready.

Instead of having untyped SyntaxNodes that allow free navigation within the hierarchy, swc is rather based around typed AST nodes and a visitor pattern.

Conversion between the two is mostly straight forward but does involve quite some manual work.

[codecov-commenter]

Codecov Report

Merging #13 (233fa92) into master (9bc019c) will decrease coverage by 0.66%.
The diff coverage is 90.22%.

❗ Current head 233fa92 differs from pull request most recent head 5a532a6. Consider uploading reports for the commit 5a532a6 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #13      +/-   ##
==========================================
- Coverage   89.84%   89.18%   -0.67%     
==========================================
  Files           6        6              
  Lines         394      490      +96     
==========================================
+ Hits          354      437      +83     
- Misses         40       53      +13     

[kamilogorek]

Not sure about this one. Feels inconsistent to me. You access it as obj_literal.named_prop in the end.
Also, Chrome is printing both now:

const foo = {
    bar: function baz() {
        throw new Error('wat')
    }
}

foo.bar()

// Uncaught Error: wat
//    at Object.baz [as bar] (<anonymous>:3:15)

[kamilogorek]

Note that it's the same for Node and any other V8 environment.

[Swatinem]

I would argue that if you are giving an explicit name to a function, you would want that to show up.
In your example, baz (the fn name) is also the "primary" thing thats being called out. as bar (the name you call) is only "secondary" information.