Adding comments header for compiled & optimized files

Adding a plain text to the header of a compiled and optimized .js-file may be useful for multiple reasons:

• Adding metadata like version, compiler settings, date, …
• Adding execution information, e.g. #!/usr/bin/env node
• Adding a License, Author, Support info, URL, …

Such a plain text header could easily be added to a .js in a postprocessing step after compilation. However, if I am not mistaken, the Sourcemap would also have to be remapped. That seems to me like a quite involved chore.

This brings me to the following feature request: Would it be possible to add a “headerString” option to the SBT plugin, such that such a header can be added more easily?

[sjrd]

I would much rather insert actual JS comments (their grammar isn’t that hard to check, to make sure that no one is inserting anything but comments). That way reasonable use cases are addressed at the core.

And if someone really wants the shebang thing, they can insert a one-line comment, then do the patching.

[DirkToewe]

Comments alone would already be very helpful to me. The #!/usr/bin/env node shebang may be useful to others but I don’t have a use case for it.