🚀 Feature: Use a shenanigans.json file instead of a "shenanigans" package.json property #300
Open
3 tasks done
Labels
area: tooling
Builds, infrastructure, packages, and other repository management
package: shenanigans-manager
type: feature
Suggested enhancement or new ability.
Bug Report Checklist
main
branch of the repository.Expected
I'm finding now that there are a lot of reasons to include metadata around a package's
shenanigans-manager
process (e.g. #298, #299). I think it's time to make a dedicatedshenanigans.json
file instead of a big property inpackage.json
files.Additional Info
Fun fact, this was used five+ years ago, but removed in #22. At the time
shenanigans.json
files just included package metadata already present inpackage.json
.The text was updated successfully, but these errors were encountered: