Skip to content
No description, website, or topics provided.
JavaScript
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
src Made commentStart and commentEnd take only the charachters appended t… Aug 23, 2016
test Made commentStart and commentEnd take only the charachters appended t… Aug 23, 2016
.babelrc
.eslintignore
.eslintrc.json
.gitignore
.npmignore
.travis.yml
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE.md
README.md
package.json

README.md

Travis

babel-plugin-add-header-comment

Will add a comment to the start of the transpiled code. Since transpiling via Babel is becoming one of the last steps of the build process it's handy to add some tooling around this final step. For instance could be used:

  • to add in license info
  • add in version numbers to builds
  • etc.

Installation

$ npm install babel-plugin-add-header-comment

Example

The following is an example .babelrc file. Using the following settings the comment will be created using 3 different features:

  1. Adding a hardcoded string ("This string will be inserted in")
  2. By executing a script and injecting the output (node executeThisOutputAddedToHeader.js)
  3. By reading in the contents of a file (readInTheContentsOfThisFile.txt)
{
  "presets": ["es2015"],
  "plugins": [
    ["add-header-comment", {
      "header": [
        "This string will be inserted in a comment header",
        "!node executeThisOutputAddedToHeader.js",
        "?readInTheContentsOfThisFile.txt"
      ]
    }]
  ]
}

Sometimes you may want to just add headers to specific files. In this case you can do the following:

{
  "presets": ["es2015"],
  "plugins": [
    ["add-header-comment", {
      "files": {
        "src/index.js": {
          "header": [
            "This string will be inserted in a comment header"
          ]
        }
      }
    }]
  ]
}

Plugin Options

  • newLineChar- This is the newline char that should be used by the plugin. Default value: '\n'
  • cache - This is a string which represents what type of operations should be cached. For instance if you wanted to cache both read and command executions you could pass in ?!. Default value: '?'
  • commentStart- This is a string which describes how the comment is started/opened. For instance if you'd like you're comment to start with /*COMMENT START pass in 'COMMENT START'. Default value: '*\n'
  • commentEnd- This is a string which describes how the comment is ended/closed. For example if you'd like your comment to end with COMMENT END*/ pass in 'COMMENT END'. Default value: '\n*'
  • commentLineStart- A string which is the leading charachter before a comment. Default value: '* '

License

MIT, see LICENSE.md for details.

You can’t perform that action at this time.