https://github.com/blueberryapps/js-package-template

Boilerplate for creating a new javascript package
https://github.com/blueberryapps/js-package-template

blueberry-opensource boilerplate javascript package package-creation

Last synced: about 1 year ago
JSON representation

Boilerplate for creating a new javascript package

• Host: GitHub
• URL: https://github.com/blueberryapps/js-package-template
• Owner: blueberryapps
• License: mit
• Created: 2017-04-12T20:45:07.000Z (about 9 years ago)
• Default Branch: master
• Last Pushed: 2023-01-24T17:28:47.000Z (over 3 years ago)
• Last Synced: 2025-04-13T23:08:08.776Z (about 1 year ago)
• Topics: blueberry-opensource, boilerplate, javascript, package, package-creation
• Language: Shell
• Homepage:
• Size: 258 KB
• Stars: 16
• Watchers: 28
• Forks: 1
• Open Issues: 5
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# XXX [![Dependency Status](https://dependencyci.com/github/blueberryapps/js-package-template/badge)](https://dependencyci.com/github/blueberryapps/XXX)

# Create new package

`

bash <(curl https://raw.githubusercontent.com/blueberryapps/js-package-template/master/create-new-package) NEW_PACKAGE_NAME

`

## Development

```

yarn install

yarn eslint

yarn eslint:fix

yarn test

```

## CI and autopublish

On Circle CI you need to add `NPM_TOKEN` which has rights to publish package to npmjs.org.

Also when you provide `SLACK_TOKENS` XXX/YYY/ZZZZ

(take them as one string from url `https://hooks.slack.com/services/XXX/YYY/ZZZ`)

it will let you know about new version.

When code gets to master branch, it will try to publish,

so if version in package.json is different, it will push it automatically.

## Made with love by

[![](https://camo.githubusercontent.com/d88ee6842f3ff2be96d11488aa0d878793aa67cd/68747470733a2f2f7777772e676f6f676c652e636f6d2f612f626c75656265727279617070732e636f6d2f696d616765732f6c6f676f2e676966)](https://www.blueberry.io)