Tim Haines
Tim Haines
@philippederyck As the issue's still open and there's nothing obvious about it in the README, here's the reminder. :)
@maranov sounds good to me. Would love to see this warning disappear. 👍
Hi @WIStudent - FWIW, license_finder does check for licenses in the package.json (via npm list) before checking for license files. In the first instance, were the packages reported, but licenses...
Are there actually over 2000 unique packages? I'd be interested in getting a (sanitized) copy of your package.json to have a play too.
FWIW, the npm docs refer to SPDX - it's something they seek to educate on. https://docs.npmjs.com/cli/v7/configuring-npm/package-json#license Perhaps it's worth considering spdx_identifers or similar, to indicate it shouldn't be free-form.
FWIW, Blue Oak's license has an SPDX code; `BlueOak-1.0.0`. But yeah, you do see all kinds of content in that field. "See license in license" is somewhat common.
Would love to have these tweets rendering correctly.
@jakl Nice work. Is the other minor change fixing the tweet character botching? https://github.com/twitter/twitter-text-js/pull/122
`autoLinkWithJSON("my @name", entities, { usernameIncludeSymbol: true })` works too. Awesome. This is a non-issue for us now, but yeah, it seems like updating the defaults to match your display requirements...