Skip to content

tlvince/alle-publish

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

alle-publish

Build Status npm version License

An approximation of Lerna publish using alle

  1. Walk through a packages dir
  2. Collect package dependencies through static analysis
  3. Merge top-level package.json metadata
  4. Publish packages

Installation

npm install --save-dev alle-publish

Usage

Have something bump the version of the parent package, then call alle-publish.

Options

Looks for the nearest .allerc in JSON format (example shown here in JS for comments).

{
  // optional scoped package support
  scope: '@myorg',
  // package.json template extended into parent package
  template: {
    main: 'index.js',
    // supports private registries
    publishConfig: {
      registry: 'http://example.com'
    }
  },
  // pull these properties from the parent package.json
  extends: [
    'repository',
    'keywords',
    'bugs',
    'homepage',
    'license',
    'author'
  ],
  // optionally transform resolved dependencies during static analysis
  transformers: {
    // npm package/a package in node_modules
    // option or list of options passed to the transformer
    'allo-replace-transformer': {
      pattern: '/foo/',
      replacement: 'bar'
    }
  }
}

Author

© 2016 Tom Vincent git@tlvince.com (https://tlvince.com)

License

Released under the MIT license.

About

An approximation of Lerna publish using alle

Resources

License

Code of conduct

Security policy

Stars

Watchers

Forks

Sponsor this project

 

Packages

No packages published