Consider allowing configuration to be loaded from package.json.

[wtgtybhertgeghgtwtg]

Like what yargs does with pkgConf. If I had a package.json like

"someKey": {
  "someFlag": "someValue"
}

and told meow to look at someKey, it'd take that configuration into account. Maybe you could even pass someKey as an argument, like

myTool -configKey someKey

[sindresorhus]

Hmm, I kinda like the idea, but I have to consider whether it's worth bundling it. It's easy enough to use pkgConf directly. The benefit would be discovery and being able to recommend that practice.

and told meow to look at someKey

When enabled it can just look for a key that matches the package name.

[wtgtybhertgeghgtwtg]

Wouldn't you end up hitting the file system twice for the same package.json if you used pkg-conf?