https://github.com/buildit/taco-components
Components library for project taco
https://github.com/buildit/taco-components
react tacos travis
Last synced: about 1 month ago
JSON representation
Components library for project taco
- Host: GitHub
- URL: https://github.com/buildit/taco-components
- Owner: buildit
- License: mit
- Created: 2017-01-24T16:15:18.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2017-02-13T16:54:57.000Z (about 8 years ago)
- Last Synced: 2025-03-28T20:17:58.245Z (about 1 month ago)
- Topics: react, tacos, travis
- Language: JavaScript
- Size: 30.3 KB
- Stars: 0
- Watchers: 8
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Taco Components
A React components library for Project T.A.C.O.
## Usage
```
npm install --save taco-components
```
Then, in your React file:
```
import { QuantityPicker } from 'taco-components'
```
## For developers of Taco Components
We're using Travis to handle continuous deployment. Right now, it's very basic. It pulls in the latest code and attempts to publish it to npm's registry.
The publish only happens on tagged commits. Use npm's 'version' command to do the version tags. Here's a sample workflow:
Do some work. Commit it:
```
git add .
git commit -m "Fix bug"
```
If this work is worthy of a version bump, [bump it](https://docs.npmjs.com/cli/version):
```
npm version patch -m "Fix bug"
```
We're using pre and post version hooks (see package.json) to validate and push the code to the remote repo.
Travis is configured to run the job whenever a new commit is pushed to the remote repository. At that point, the new version will be published to npm, and any project that depends on Taco Components will be able to make use of the updated code.