When we ship new node modules, or update our node modules we should be checking that the licenses are (still) acceptable. Generally I've been checking this when I've reviewed the addition of new modules, but I think it would be reasonable to have an automated check for which a linter which would mean we don't have to remember to do it, and we have the list already written. Currently I'm looking at using [license-checker-rseidelsohn](https://www.npmjs.com/package/license-checker-rseidelsohn), though a couple of packages it requires use a different license and [are obsolete](https://github.com/RSeidelsohn/license-checker-rseidelsohn/issues/127). So I'm going to see if we're able to get that package updated to not use those.
Bug 1940283 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
When we ship new node modules, or update our node modules we should be checking that the licenses are (still) acceptable. Generally I've been checking this when I've reviewed the addition of new modules, but I think it would be reasonable to have an automated check for which a linter which would mean we don't have to remember to do it, and we have the list already written. Currently I'm looking at using [license-checker-rseidelsohn](https://www.npmjs.com/package/license-checker-rseidelsohn), though a couple of packages it requires use a different license (which we haven't checked before) and [are obsolete](https://github.com/RSeidelsohn/license-checker-rseidelsohn/issues/127). So I'm going to see if we're able to get that package updated to not use those.