Skip to content

Latest commit

 

History

History
100 lines (70 loc) · 3.95 KB

contribute.md

File metadata and controls

100 lines (70 loc) · 3.95 KB
Raw

Contribute to the Fluent State project 🤝

Thank you for wanting to contribute to the Fluent State project. With your contributions we can ensure Fluent State remains a leading solution for implementing State Machines within JavaScript projects.

Steps for success

  1. Issues:
    1. Always work off of an Issue. Please do not submit a Pull Request that is not associated with an Issue (create the Issue if necessary).
    2. If you are beginning work on an Issue, please leave a comment on the issue letting us know, and we'll assign the Issue to you. This way somebody else won't start working on the same Issue.
  2. Branches:
    1. Always branch off of main, which contains the latest version of Fluent State
  3. Pull Request (PR):
    1. Make sure you run the following scripts in local, and that all of them pass, before submitting a PR:
      1. npm run lint:fix
      2. npm run format
      3. npm test
    2. Make sure your PR is targeting the correct branch (see Step 2.i)
    3. At the top of your PR description write: "Fixes #n". Where n is the number of the Issue your PR is fixing (e.g., Fixes #33). This will tell GitHub to associate your PR with the Issue.

Development

Prerequisites

Source Code

  1. Clone the repo
  2. Change directories: cd fluent-state
  3. Install dependencies: npm i

Development

Start app in watch mode: npm run local

When file changes are detected, the app will automatically rebuild/restart

Linting

  • Check lint rules: npm run lint
  • Fix lint errors: npm run lint:fix
  • Fix formatting errors: npm run format

Appendix

Dev Tools

The following section includes optional dev tools that enhance the Fluent State development experience, but are not necessary.

NVM

The Fluent State project includes an .nvmrc file, so you can run nvm use to switch to the required version of Node.

Setup
  1. Install nvm: https://github.com/nvm-sh/nvm
  2. Install the Node.js version required by this app: nvm install
    1. NVM will determine the required Node version using the .nvmrc file
    2. NVM will install the required Node version if it isn't installed
    3. NVM will set your current Node version to the one required

Git Hooks

The Fluent State project includes Husky for running Git Hooks. Running git commit will trigger lint-staged which will lint all files currently staged in Git. If linting fails, the commit will be cancelled

Dependencies

  • chai: we must use v4.x because v5.x is pure ESM, and we require CommonJS modules

Deployment

Deployments to Prod consist of building and publishing the Fluent State lib to NPM, and are automated through our Continuous Deployment workflow.

1. Create New Version

  1. Checkout main.
  2. Increment the version in package.json, using semantic versioning (e.g., 1.1.0).
  3. Rebuild package-lock, to pick up the new version number: npm i --package-lock-only.
  4. Push changes: 
    git add .
git commit -m "Bump version to 1.1.0"
git push

2. Verify Checks

  1. Navigate to the CI workflow.
  2. Ensure the build checks for this push succeed.

3. Publish GitHub Release

  1. Navigate to Fluent State's releases.
  2. Click "Draft a new release":
    • Choose a tag: enter version (e.g., v1.1.0) and click "Create new tag"
    • Target: main
    • Previous tag: auto
    • Release title: (e.g., 1.1.0)
    • Description: click the "Generate release notes"
    • Set as the latest release
  3. Click "Publish release".

This will trigger the CDP workflow, which will build and deploy the package to NPM: https://www.npmjs.com/package/@2toad/fluent-state