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 am adding this issue as a backlog as it is not really critical, but it may get a blocker for users obeying licensing rules (e.g. GPL).
There are many cases, when license or banner has to be included in result file (e.g. by license requirement).
Yes, it is possible to achieve now, but it is not very convenient.
The simple way is to add a "banner" option similar browserify. It solves the problem partially.
However, if sources from more than one module are included, it may be required to add several banners in result file header comment.
My proposal is to add:
a. "requireBanner" option to enforce checks that banner exists for every bundled module
b. "bannerMap" option for { require_name : banner_text } pairs
To make it more advanced and flexible, the "banner" and "bannerMap" options should get pre-populated with "banner" field from the corresponding module's package.json file, if present. It will ensure that always the correct banner text is included and no copy-paste is needed.
The text was updated successfully, but these errors were encountered:
I am adding this issue as a backlog as it is not really critical, but it may get a blocker for users obeying licensing rules (e.g. GPL).
There are many cases, when license or banner has to be included in result file (e.g. by license requirement).
Yes, it is possible to achieve now, but it is not very convenient.
My proposal is to add:
a. "requireBanner" option to enforce checks that banner exists for every bundled module
b. "bannerMap" option for { require_name : banner_text } pairs
The text was updated successfully, but these errors were encountered: