Skip to content
This repository has been archived by the owner on Jul 3, 2019. It is now read-only.

Better config system #9

Open
zkat opened this issue Feb 3, 2017 · 1 comment
Open

Better config system #9

zkat opened this issue Feb 3, 2017 · 1 comment

Comments

@zkat
Copy link
Owner

zkat commented Feb 3, 2017

opt-check was a pretty basic option handling mechanism but I'm not feeling great about it: it silently fails if it gets unexpected options (and those options are later requested), it doesn't support types or any sort of verification for options, and it just assumes that everything is gonna want all the options.

But, as it turns out, as we call individual things, they expect other subsets of options. It might be nice to have an opts mechanism where every layer can specify what exactly it wants and needs, so it's easy to see what's using what, and at what level -- specially stuff we're passing to dependencies like cacache, which have a bunch of their own opts!

@zkat
Copy link
Owner Author

zkat commented Feb 9, 2017

Woo! So there's https://npm.im/figgy-pudding now, intended to be an initial spike at fixing this issue. Perhaps convert pacote to use that, and see how it feels?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant