2.4.0 • Published 4 years ago

react-benzin-test v2.4.0

Weekly downloads
-
License
MIT
Repository
-
Last release
4 years ago

React Material components library. It supplies you with cool pre-defined style, while assuring that your project will follow all Material Design guidelines.

npm.io npm.io npm.io npm.io npm.io

Getting started

Installation

You can easily add BENZIN to your project with npm:

$ npm install react-benzin

BENZIN works best in kick-starting new projects and allows you to focus on the functionality, while all the beauty will be maintained by our library.

TIP: Create-React-App with Typescript is your GO-TO in most of the cases. Learn more.

You can find a minimal usage example here.

Functionality

BENZIN provides you with a bunch of cool components that greatly integrate with each other.

Explore src/lib/ folder to see what's available. Documentation is yet to come, but for now you can enjoy type definitons.

Chrono-Cube will also be a great example of usage, since it's the actual project which inspired us to create BENZIN.

Explore NPM package online

https://www.npmjs.com/package/react-benzin

Development

Running live demo

To run a live example, clone a repo and execute following commands:

$ npm i
$ npm start

It's worth noticing that presence of React-App in this repo forces us to split some configurations. For example, we have 2 Typescript configs: one for react-scripts to run live-demo, and the other one to build distribution files.

Running tests

$ npm test

NOTE: this command assures that ESlint does not throw any warnings and exits with a non-zero status code otherwise. That means CircleCI tests would fail even if a single warning is present. Therefore, you should always locally test your changes before publishing them.

Building

We've decided to use Typescript compiler to transpile our code, since we think Babel is a bit of an overkill here.

$ npm run build

This command will generate dist/ folder ready for distribution, which you of course can explore. Note that tsc creates type definitions (.d.ts) for every corresponding .js file. It's very useful because consumers also get access to them.

Deploying

Deploying to npm is fully automated through CircleCI: simply tag a commit as a Release and it will do the job.

2.2.3

4 years ago

2.4.0

4 years ago

2.3.3

4 years ago

2.3.0

4 years ago

2.2.8

4 years ago

2.2.0

4 years ago

2.1.1

4 years ago

2.1.0

4 years ago

2.0.4

4 years ago

2.0.3

4 years ago

2.0.2

4 years ago

2.0.0

4 years ago

1.1.1

4 years ago

1.1.0

4 years ago

1.0.9

4 years ago

1.0.8

4 years ago

1.0.6

4 years ago

1.1.4

4 years ago

1.0.5

4 years ago

1.1.3

4 years ago

1.0.4

4 years ago

1.0.3

4 years ago

1.0.2

4 years ago

1.0.1

4 years ago

1.0.0

4 years ago