<img src=https://centerkey.com/graphics/center-key-logo.svg align=right width=200 alt=logo>
Prepend a one-line banner comment (with license notice) to distribution files
add-dist-header uses the name
, homepage
, and license
from your project's package.json
file to create a header comment and prepend it to a build file.
<img src=https://raw.githubusercontent.com/center-key/add-dist-header/main/screenshot.png
width=800 alt=screenshot>
Example header comment for a .js file:
Example header comment for a .css file:
Automatically prepending headers to distribution files is particularly handy when your build
tools are configured to remove comments (such as if "removeComments": true
in set
in tsconfig.json).
For a real-world example, see the files in the dist folder at
w3c-html-validator
A) Setup
Install package for node:
$ npm install --save-dev add-dist-header
B) Usage
1. npm scripts
Run dist-header
from the "scripts"
section of your package.json file.
Parameters:
- The first parameter is the source file (defaults to
"build/*"
). - The second parameter is the output folder (defaults to
"dist"
).
Example package.json script:
"scripts": {
"add-headers": "add-dist-header build dist"
},
2. Global
You can install add-dist-header globally and then run it anywhere directly from the terminal.
Example terminal commands:
$ npm install --global add-dist-header
$ add-dist-header "build" "dist"
[17:13:50] add-dist-header build/my-app.d.ts --> dist/my-app.d.ts (413.11 KB)
[17:13:51] add-dist-header build/my-app.js --> dist/my-app.js (1,569.70 KB)
The parameters are optional:
$ add-dist-header
[17:13:50] add-dist-header build/my-app.d.ts --> dist/my-app.d.ts (413.11 KB)
[17:13:51] add-dist-header build/my-app.js --> dist/my-app.js (1,569.70 KB)
$ add-dist-header "meta/config.js"
[17:15:03] add-dist-header meta/config.js --> dist/config.js (3.91 KB)
3. CLI flags
Command-line flags:
Flag | Description | Values | Default |
---|
--delimiter | Characters separating the parts of the header comment. | string | ~~ |
--keep-first | Do not delete the original first line comment. | N/A | N/A |
--no-version | Do not substitute occurrences of {{pkg.version}} with the package.json version number. | N/A | N/A |
--note | Place to add a comment only for humans. | string | N/A |
--quiet | Suppress informational messages. | N/A | N/A |
Version number substitution:
In addition to prepending the header comment, add-dist-header also replaces all occurrences of
{{pkg.version}}
in each file with the version number found in package.json.
This enables inserting the current package version number into your distribution files.
The substitution feature is disabled by setting --version
flag to false
:
Examples:
add-dist-header temp dist --delimiter=🔥
Use "🔥" as the separator instead of "~~".add-dist-header --no-version build dist
Add headers but do not substitute the version number.
C) Application Code
Even though add-dist-header is primarily intended for build scripts, the package can easily be used programmatically in ESM and TypeScript projects.
Example:
import { addDistHeader } from 'add-dist-header';
const options = {
dist: 'dist',
delimiter: '🚀🚀🚀',
};
const result = addDistHeader.prepend('build/rocket.js', options);
console.log('The size of the new file is:', result.size);
See the TypeScript Declarations at the top of add-dist-header.ts for documentation.
CLI Build Tools
- 🎋 add-dist-header: Prepend a one-line banner comment (with license notice) to distribution files
- 📄 copy-file-util: Copy or rename a file with optional package version number
- 📂 copy-folder-util: Recursively copy files from one folder to another folder
- 🔍 replacer-util: Find and replace strings or template outputs in text files
- 🔢 rev-web-assets: Revision web asset filenames with cache busting content hash fingerprints
- 🚆 run-scripts-util: Organize npm scripts into named groups of easy to manage commands
- 🚦 w3c-html-validator: Check the markup validity of HTML files using the W3C validator
Feel free to submit questions at:
github.com/center-key/add-dist-header/issues
MIT License