Dev Feed

First of, I don't know whether this is within scope of c8 or not, but I'm sharing here anyway for further input / visibility. NOTE: Our test suite is run via the same npm scripts - which control the choreography of downloading all docker containers + spinning up the server in the same order - in Github vs Local so I see no reason why the metric should be different, but here is the output. Local: <img width="851" height="313" alt="Image" src="https://github.com/user-attachments/assets/bc8ccd16-e68b-4208-8cb7-a74ce8bba75c" /> Github Action <img width="813" height="377" alt="Image" src="https://github.com/user-attachments/assets/82a76d72-0e50-430c-abd5-6d0dc843f001" /> Process: - Run test script - Script pulls down required docker dependencies - Spin up node server - Test APIs from mocha - Use c8 to track test coverage Anyone seen this before / any pointers?

Confirmed. Thanks for the turnaround 👍

Yeah I'm keen to see `knex` maintained even if just dependency updates and minor updates. Long-term though it feels like this package is being sunsetted?

Yep confirmed that works my side with 1.1

bump version

skip assgned promises as the assumed intent would be that they are aw…

No problem - Version: `0.6 Homebrew` - Example repo: https://github.com/rubengmurray/no-unawaited-dot-catch-throw <img width="662" height="135" alt="Image" src="https://github.com/user-attachments/assets/4eec0c04-2f1b-4ccc-bd1d-2c1f6225455c" /> vs <img width="678" height="163" alt="Image" src="https://github.com/user-attachments/assets/3d3c9ade-2560-4857-b5bc-ff1a91789c6b" />

This works, but I'm confused as to which change produced this error for me. My repo was fine up until a month or so ago. Only thing I can think is something to do with a Node 20 upgrade.

The following command results in zero'd Files & Lines + / - data. <img width="645" height="88" alt="Image" src="https://github.com/user-attachments/assets/4fb338bb-57df-459f-8a16-a813f9867655" /> `git who table -f -n 0 ':!*.json'` *Use case: exclude `.json` from "Lines" data where a lot of the changes could be in `package-lock.json` as a result of dependency installations / updates.

My old Linux machine died. Not sure if any of the reason substantial dependency bumps have had the side-effect of resolving this?