You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to do the diligence as a user and build a page to list all licenses of the OSS packages we're using and I noticed that the published npm packages do not contain the LICENSE file from the root of the repo (as required by the license itself). Including the license file in the distributed bundle will make it much easier for your consumers to abide by the license.
Is this something I should raise as an issue in this repo? Or in the Bob repo? With a little direction, I'd be happy to contribute a solution.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi gang!
I'm trying to do the diligence as a user and build a page to list all licenses of the OSS packages we're using and I noticed that the published npm packages do not contain the LICENSE file from the root of the repo (as required by the license itself). Including the license file in the distributed bundle will make it much easier for your consumers to abide by the license.
Is this something I should raise as an issue in this repo? Or in the Bob repo? With a little direction, I'd be happy to contribute a solution.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions