Looking at v3 #298

New issue

Open

opened 2023-02-04 20:14:56 +00:00 by mcataford · 0 comments

mcataford commented

2023-02-04 20:14:56 +00:00

(Migrated from github.com)

It's been a while since Packwatch has been touched in any meaningful way, 2023 is time. 🚀

Open to feature requests

In mapping what v3 will look like and offer, the suggestion box is open! 🎉 Just post under this issue to start a discussion on features or changes you'd like to see in Packwatch 3.

Projected features

Ability to have greater control of threshold that trigger failing checks (https://github.com/mcataford/packwatch/issues/18)
Tracking the number of direct / transitive dependencies (via the Yarn API?)
A versioned schema for packwatch.json

It's been a while since Packwatch has been touched in any meaningful way, 2023 is time. :rocket: # Open to feature requests In mapping what v3 will look like and offer, the suggestion box is open! :tada: Just post under this issue to start a discussion on features or changes you'd like to see in Packwatch 3. # Projected features - Ability to have greater control of threshold that trigger failing checks (https://github.com/mcataford/packwatch/issues/18) - Tracking the number of direct / transitive dependencies (via the Yarn API?) - A versioned schema for `packwatch.json`

This repo is archived. You cannot comment on issues.