Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Banner/License comment support #17

Open
andvgal opened this issue Dec 28, 2014 · 0 comments
Open

Banner/License comment support #17

andvgal opened this issue Dec 28, 2014 · 0 comments

Comments

@andvgal
Copy link

andvgal commented Dec 28, 2014

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.

  1. The simple way is to add a "banner" option similar browserify. It solves the problem partially.
  2. 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
  3. 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant