Zero App Client
🚀 Builds Status
Master:
Development:
💅 Test Coverage
Master:
Development:
📝 Documentation
Requirements
- nvm v0.34.0 (install details)
- Node v12.16.1 (install details)
- npm v5.6.0
Stack
Environment Variables
Application variables
Set Application variables in the .env file
- NODE_ENV
- ENV
- DEV (changes the development mode for the use of the library)
- NPM_TOKEN (token do publish in npm)
Initialization
git clone git@gitlab.com:laborit/zero-client.git
cd zero-client/
cp .env.sample .env
npm i
npm run devTesting library to localhost
Changes the development mode for the use of the library
npm run build:lib
npm run dev:browserBuild
Build library to production
npm run build:liboutput path /lib
Build client to production
npm run build:distoutput path /dist
Testing
Using jest with enzyme and chai (see examples on ./src/**/*.spec.js)
npm test
npm run test:coverageLinting
Using eslint
npm run lintDeploy
NPM package
Locally
Logged in at NPM with your user
Build the library
npm run build:libUpdate package version:
npm version major | minor | patchsee more details in npm-version
Publish the package
npm publishWith Gitlab CI
Set the npm token on gitlab ci environment variable NPM_TOKEN
Before commit, update package version:
npm version major | minor | patchsee more details in npm-version
After than, commit to branch master:
git push origin master
Why?
It removes all original styling and ensures that all outputted code conforms to a consistent style.
As you can see, these two tools we make sure our codebase is consistent across all developers, IDE's and operating systems. Make sure you have them properly configurated on your IDE before starting writing code.