tools

tools copied to clipboard

Description

Create a CI test that runs the parser against the 1000 most popular npm packages and fails if any of them fails parsing.

Plus points for:

• CI job only runs on lexer/parser changes
• It's possible to run the command locally too

How do you plan to do that? Personally, I don't - think it's doable doing this against all these repos. Unless we have bare package resolution, trying to get the source code from repo/npm tarball is going to require lot of resources

I would probably approach it similarly to how bench_parser works today. Create a libs.txt file with the URLs to the NPM packages.

Running the parser shouldn't take a lot of time in release mode. Even parsing TypeScript takes only 250ms on my machine.

Fair point! Sounds good!

I would put this job under a Cron job or trigger it via comment. It sounds to be an expensive job, probably we don't need it at every PR.

I would put this job under a Cron job or trigger it via comment. It sounds to be an expensive job, probably we don't need it at every PR.

Let's see what the runtime is. We could even consider putting t into the conformance job because the most expensive part will be compiling the release binaries.

👋 @rome/staff please triage this issue by adding one of the following labels: S-Bug: confirmed, S-Planned , S-Wishlist or umbrella