Whitelist dependency documentation about documentation HOT 4 CLOSED

@tmcw How would you feel about this option accepting a glob for the whitelist?

(edit) That would allow a direct whitelist and wildcard matching, but also traversing deeper into the dependencies. E.g.: --external turf-*, --external !(through2|request), --external */node_modules/*

from documentation.

👍 for the node-facing api, we could use something like micromatch or minimatch to augment the existing external modules check. That said, I'm really not sure whether globs written as cli arguments are always expanded, so not sure if it'll work on both levels.

from documentation.

Oh, good point about the cli expansion... Although, since it probably makes sense to treat the first node_modules/ as understood (so that I could say --external turf-* instead of --external node_modules/turf*), I think the globs that a user passed in on the command line would actually fail to match the real directories and thus just be passed in as strings.

Hoping to put in a PR for this soon.

from documentation.

👍 fixed in #60

from documentation.