1.1.7 • Published 2 years ago

open-source-starter v1.1.7

Weekly downloads
14
License
MIT
Repository
github
Last release
2 years ago

This starter provides all necessary setup to quickly start an open source project, with fully automated release, tests, generate CHANGELOG.md, version bump, publish to NPM.

Content

Babel : Use next generation JavaScript

All .js files in src/ will be compiled with Babel and added in the dist/ folder

Config : .babelrc

ESLint : A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease

config: .eslintrc

Prettier : Opinionated code formatter

config: .prettierrc

Husky : Use git hooks with ease

Here it just call lint-staged on pre-commit

config: "husky" in package.json

lint-staged : Run linters against staged git files

Here it calls ESLint and Prettier on git add

config: "lint-staged" in package.json

Commitizen : Conventional commit messages CLI

Semantic Release : Fully automated version management and package publishing

Jest : JavaScript Testing Framework

Add your test files either in src/ with my-file.spec.js format, or in the __tests__ folder at your project root directory

config : jest.config.js

Requirements

*note: this repo use Github actions, but you can use any continuous integration system you want, see semantic-release-cli documentation for or more informations.*

Installation

  1. Fork or clone this repo git clone https://github.com/JimmyBeldone/open-source-starter.git
  2. Run yarn setup
  3. Configure semantic-release with semantic-release-cli : npx semantic-release-cli setup. semantic-release-cli
  4. You're all set !

Usage

Stage a file

git add src/my-file.js

From now on when you will use git add on a file in src/, it will be automatically linted and prettified.

Use conventional commit

yarn commit

This script will open Commitizen to help you write conventional commit

Release / Publish

All you need to do is merge on master branch, simple as that.

It will :

  1. Triggers CI
  2. Run your test during CI
  3. Run semantic-release steps :
    • Analyse your commits
    • Bump version
    • Add release notes
    • Generate CHANGELOG.md
    • Publish to NPM & Github

Contributing

Contributions are welcome ! See contributing guidelines

License

MIT

Copyright (c) 2019 Jimmy Beldone

1.1.7

2 years ago

1.1.6

2 years ago

1.1.5

3 years ago

1.1.4

3 years ago

1.1.3

3 years ago

1.1.2

3 years ago

1.1.1

3 years ago

1.1.0

3 years ago

1.0.9

3 years ago

1.0.8

3 years ago

1.0.7

3 years ago

1.0.6

4 years ago

1.0.5

4 years ago

1.0.4

4 years ago

1.0.3

4 years ago

1.0.2

5 years ago

1.0.1

5 years ago

1.0.0

5 years ago