Trey Shugart

1. If the consumer has webpack, use that instead 2. If not, use ours.

CSS rules are added using the imperative DOM APIs. Because of that, their content doesn't appear as `` content. There's a couple of different scenarios here. 1. For React et...

Currently we have to do: ```js css({ '* :host': {}, '* ::slotted(*)': {} }); ``` This is because they're treated as a standard pseudo. We should special case them so...

We have a set of arguments that are passed into: * The top-level config function * Callbacks in each file config * Callbacks in JSON data We should ensure a...

We should add an option for specifying a `condition` that must return true in order to run the transform on the corresponding file. It would look something like this: ```js...

Instead of having to specify all your configs in the same file, or do something like: ```js module.exports = config( 'package.json': {} ); ``` You can do something like: ```js...

From #16. > Being able to nest the config file structure for subdirectories, currently we need to specify name as 'my-sub-dir/file.js'. It might be nice to be able to do...

From #16. > A QoL way to easily load config/data from an external file, either as raw data/string or function

From #16. > Maybe pass basename of the cwd as an option somewhere, its used in quite a lot of places (e.g. package.json, any files that are named after the...