Improve parser

[kaleidawave]

Done

• Fix [,,] output dropping an empty
• Import assertions
• Remove variable field optional expression confusion
• Test declaration files (including our own for the WASM build), see issues here
• Fix weird single statement function with call (do function x(){}(); while (true);)
• Fix the new issue from the specification
• Make all tests run on main branch...?
• clippy
• Fix cfg related code issue
• Allows variable field for spread expression under extras
• Allow public for constructor things under full-typescript

Not great stuff introduced

• Parse error for large exponentials on numbers (rather than clamping the size of the number)

[kaleidawave]

Should look at the issue found here: https://gist.github.com/H-Plus-Time/fef7b91f2742fc0aed3dc6722756bb22?permalink_comment_id=4885532#gistcomment-4885532

[kaleidawave]

💚💚💚

[kaleidawave]

Just left is some TypeDeclarationModule stuff (might remove and have it all under Module). The following should parse only in type definition modules (it is the last thing to fix from the definition file generated in #114)

export default function x(): string;

Need a special default export variant which is an expression function with an optional body (normally all expression functions have to have a body but not in this case). Will fix tomorrow

[kaleidawave]

Lesson learnt: 10 minutes of sequential fuzzing runs doesn't run the same amount as 2 minutes of parallel fuzzing

[kaleidawave]

The fuzzer has something personal against me