start-rollup

1.0.2 • Public • Published

start-rollup NPM version NPM monthly downloads npm total downloads

A start runner task for rollup through rolldown api

code climate standard code style linux build status windows build status coverage status dependency status

You might also be interested in always-done.

Table of Contents

(TOC generated by verb using markdown-toc)

Install

Install with npm

$ npm install start-rollup --save-dev

or install using yarn

$ yarn add --dev start-rollup

Usage

For more use-cases see the tests

import start from 'start'
import reporter from 'start-pretty-reporter'
import rollup = from 'start-rollup'
import files from 'start-files'
import clean from 'start-clean'
import write from 'start-write'
import buble from 'rollup-plugin-buble'
 
export const build = () => start(reporter())(
  files('build/'),
  clean(),
  rollup({
    entry: './main.js',
    targets: [
      { dest: 'build/index.es6.js', format: 'es' },
      { dest: 'build/index.js', format: 'cjs' }
    ],
    sourceMap: 'inline',
    plugins: [buble()]
    // or
    // plugins: ['buble']
    // or
    // plugins: [
    //   'commonjs'
    //   ['node-resolve', { jsnext: true }]
    //   ['buble', { target: { node: '4' } }]
    //   
    //   // or pass plugin function
    //   // [buble, { target: { node: '4' } }]
    // ]
  })
)
 

This task uses Rollup but through rolldown API, which gives some advantages to the original Rollup API. So checkout both docs or at least see rollup wiki page.

Rolldown gives you:

  • better plugins resolving (seems like browserify resolves its transforms from package.json)
  • more configuration options - such as options.source, options.ongenerate and options.onwrite
  • loading configs from package.json from your process.cwd()
  • and even you can create presets of plugins and configs (shareable configs/presets)

Related

Contributing

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.
Please read the contributing guidelines for advice on opening issues, pull requests, and coding standards.
If you need some help and can spent some cash, feel free to contact me at CodeMentor.io too.

In short: If you want to contribute to that project, please follow these things

  1. Please DO NOT edit README.md, CHANGELOG.md and .verb.md files. See "Building docs" section.
  2. Ensure anything is okey by installing the dependencies and run the tests. See "Running tests" section.
  3. Always use npm run commit to commit changes instead of git commit, because it is interactive and user-friendly. It uses commitizen behind the scenes, which follows Conventional Changelog idealogy.
  4. Do NOT bump the version in package.json. For that we use npm run release, which is standard-version and follows Conventional Changelog idealogy.

Thanks a lot! :)

Building docs

Documentation and that readme is generated using verb-generate-readme, which is a verb generator, so you need to install both of them and then run verb command like that

$ npm install verbose/verb#dev verb-generate-readme --global && verb

Please don't edit the README directly. Any changes to the readme must be made in .verb.md.

Running tests

Clone repository and run the following in that cloned directory

$ npm install && npm test

Author

Charlike Mike Reagent

License

Copyright © 2016-2017, Charlike Mike Reagent. Released under the MIT license.


This file was generated by verb-generate-readme, v0.2.3, on January 03, 2017.
Project scaffolded using charlike cli.

Package Sidebar

Install

npm i start-rollup

Weekly Downloads

1

Version

1.0.2

License

MIT

Last publish

Collaborators

  • vanchoy
  • tunnckocore