Last 12 weeks · 33 commits
3 of 6 standards met
require deno to be installed to function reliably. Simply installing deno as an npm dependency seems to be the best, simplest, most secure approach? Alternatively, we could use the GH action in all the workflows, but that would introduce a difference between running locally and in CI. We could use curl to download, verify, extract a deno binary. The benefit would be that we could do this only in the pre-test hook of . But I took a stab at this and it's a lot of code and doesn't seem worth the complexity to me, especially since most of the time all the ecosystem tests are running anyway.
Repository: vitejs/vite-ecosystem-ci. Description: Vite Ecosystem CI Stars: 308, Forks: 83. Primary language: TypeScript. Languages: TypeScript (100%). License: MIT. Open PRs: 7, open issues: 4. Last activity: 1d ago. Community health: 62%. Top contributors: dominikg, renovate[bot], sapphi-red, patak-cat, bluwy, hi-ogawa, brillout, Aslemammad, danielroe, shulaoda and others.