Add alwaysInclude & filters options

[gwatts]

Resolves #1092

Adds a alwaysInclude option that takes an array of packages (or a function returning an array) to always include in the third party dependency set.

license({
  thirdParty: {
    output: path.join(__dirname, 'dist', 'dependencies.txt'),
    alwaysInclude: [ './node_modules/tailwindcss/package.json' ],
    }
  },
})

Adds a filter option that lets you add a function to filter out (or potentially add more, or merge sets together, which is the use case i was solving for) arbitrary dependencies.

license({
  thirdParty: {
    output: path.join(__dirname, 'dist', 'dependencies.txt'),
    filter: (deps) => deps.filter((dep) => !dep.name.include('mycorp'),
  },
})

[msidorov-flowbox]

Hello.
Any chance of getting this PR merged?
Thanks in advance.

[mjeanroy]

@msidorov-flowbox Hi,

I could definitely accept a PR that would implement some kind of filter or exclude option.

For the alwaysInclude, I'm not a big fan of this, as it opens other questions that are not so easy to answer (in my opinion):

• What should the alwaysInclude look like?
  • If it's a package name, getting the README/License field from the package.json dependency is error prone, as the dependency path might change depending on the package manager and how the dependency is specified (is it a direct or transitive dependency? For transitive dependencies, is the dependency hoisted or not? Etc.)
  • If it is some kind of absolute path/relative path, what should be the base path?
• What if the dependency cannot be found in the dependency tree, should it fail the build or not?

I'm open to discuss it, but I don't think it's a good idea to merge this part "as is".