1.0.1 • Published 4 years ago

@pinpointhq/thumbtack v1.0.1

Weekly downloads
-
License
Apache-2.0
Repository
github
Last release
4 years ago

CircleCI

This project is using Percy.io for visual regression testing. This project uses Storybook. This project uses Prettier for code formatting. This project uses Auto for releases.

Development

Development of components is done mostly using Storybook, but features can be designed in projects that use the design system in parallel in order to properly test your changes using real world use cases.

In order to run storybook, run yarn storybook.

In order to compile a distribution, run yarn start. This will build a package distribution to the dist folder and then start watchers that'll compile CSS and JS every time you save a file in the src folder.

You can then refer to the package from within another project's package.json file to aid development. This can be done by replacing the version with a file path E.g. @pinpointhq/thumbtack: 'file:../thumbtack', assuming the Pinpoint and Thumbtack repositories sat within the same directory. You will have to run yarn upgrade @pinpointhq/thumbtack every time you want your changes to be reflected though.

Follow our best practices and commit onto a feature branch, before making a pull request into Develop. Use percy to confirm visual changes before merging the PR.

Distribution

We're using a package called (auto)https://intuit.github.io/auto/home.html to help us release versions. All you have to do is create and merge pull requests and it handles the rest.

Create a PR into master from develop and apply any one of the patch, minor, or major labels. This will automatically increment the version number, add entries into the changelog, deploy a new release to Github, and publish the new version of the package on NPM.

CircleCI should handle all of the building and deployment of the distribution so you don't have to worry about ensuring you've remembered to build the distribution.

Note: The only caveat here is that I can't work out how to stop auto from making the package public when releasing to NPM, so I'm having to manually reset the package back to private each time a new version is published. Apparently any package scoped under an org (I.e. @pinpointhq) should be automatically set as private, but this doesn't appear to be the case.

1.0.1

4 years ago

1.0.0

4 years ago

0.2.3

4 years ago

0.2.4

4 years ago

0.2.2

4 years ago

0.2.1

4 years ago

0.2.0

4 years ago

0.1.1

4 years ago

0.1.5

4 years ago

0.1.4

4 years ago

0.1.3

4 years ago

0.1.2

4 years ago

0.1.0

4 years ago