Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@keboola/indigo-ui

Package Overview
Dependencies
Maintainers
5
Versions
206
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@keboola/indigo-ui

Keboola UI library

  • 2.8.2
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
23
decreased by-89.69%
Maintainers
5
Weekly downloads
 
Created
Source

Indigo UI

Build Status npm license

Indigo UI library, its CSS and React components. Also Styleguide app showing usages of this library.

Development

  1. Make sure you have Node 8 installed node -v
  2. Install grunt: npm install -g grunt
  3. Install dependencies: yarn
  4. Run storybook yarn storybook
  5. Open browser at http://localhost:9009/

Docker

  1. Build: docker-compose build (See Dockerfile to check what's inside)
  2. Run container: docker-compose run --rm --service-ports node
  3. Continue from step 3. (including) in section above (yarn, yarn storybook, ...)

Simultaneously with Keboola Connection (Docker only)

Since development version of Keboola Connection is served through https, you need to use indigo-ui library with https too.

There's https-proxy service prepared in docker-compose.yml file. This service will allow you to proxy requests to local instance of Storybook (localhost:9009) and serve it through https protocol. Additional headers are added to responses, check .dev/nginx/nginx.conf file for more information.

The following command:

docker-compose up node https-proxy

starts node and https-proxy services. After that, Storybook will be available on http://localhost:9009/ (same as above) and Nginx server serving same Storybook through SSL will be available on https://localhost:9010/.

Registering to Keboola Connection

Replace UPPERCASE marked variables and run the following command to register Storybook to your development instance of Keboola Connection:

curl \
  -X POST \
  -H X-KBC-ManageApiToken:DEV_KBC_SUPER_API_TOKEN \
  -H "Content-Type:application/json" \
  -d '{"manifestUrl":"http://STORYBOOK_HOST_AVAILABLE_FROM_DEV_KBC_HOST:9009/kbc-dev-manifest.json","activate":true}' \
  http://DEV_KBC_HOST:8800/manage/ui-apps

DEV_KBC_SUPER_API_TOKEN can be created in the Manage Apps section of your local connection. You need to provide the token with the scope: connection:ui-manage

You can find kbc-dev-manifest.json file in public folder in this repository.

You'll also need to add your local storybook host to Keboola Connection's CSP for styles and fonts. Update the public/index.php and add STORYBOOK_HOST_AVAILABLE_FROM_DEV_KBC_HOST:9010 to the style-src and font-src sections.

Also, please note that you'll need to visit your STORYBOOK_HOST_AVAILABLE_FROM_DEV_KBC_HOST:9010 and accept the self signed cert manually so that your browser will begin to allow it.

Deployment

First, check the content of .travis.yml file and documentation about Travis Deployment.

Storybook

  • Storybook is deployed on every push to master branch. There's "$TRAVIS_BRANCH" = "master" condition in .travis.yml.
  • The deploy-storybook.sh script is responsible for deploying. Basically, it's a "home made" replacement for Travis deploy section, since that section is used for something else (covered bellow).
  • After successful deployment, the Storybook build will be available online

UI library, its CSS and components

  • When you push new tag then yarn build-dist-css command is executed. There's "$TRAVIS_BRANCH" = "$TRAVIS_TAG" condition in .travis.yml.
  • After successful build, a deployment and publishing to registry is started. Check deploy section in .travis.yml
  • After successful deployment, there will be new version of CSS available to link from Cloudfront and package published to npmjs registry.

Registration in Keboola Connection

TBD

Releasing new version
  • Before pushing new tag, make sure you know what are you doing.
  • New tagged release is only needed if there's a change in src/indigo or src/components folders and you want to make those changes available for users.
  • Please respect Semantic versioning

Steps:

  1. Make sure everything is working as expected
  2. Prepare new version with npm version ... command (manual here). This command should create new commit (with version change in package.json) and tag for you. There's no need to change package.json manually or create tag manually.
  3. Push to master branch - e.g git push origin master
  4. Check if everything is as expected
  5. Push newly created tag - e.g. git push origin v2.0.0-beta-3 <- This triggers deploy!
  6. Check package in npmjs registry, try to install it or update to newer version from some project
  7. Write release notes keboola/indigo-ui/releases

Older, kbc-bootstrap branch

This branch was introduced only for compatibility with keboola/kbc-bootstrap. Releases from this branch are tagged as v0.1.x and you probably won't need to do anything with this branch. All releases are available here

Older, v1 branch

This branch contains some changes, but we decided to skip it and start with v2 and smaller, incremental steps.

FAQ

How to check what will be published to npmjs registry before pushing new tag?

Run npm pack. Check its manual here.

Keywords

FAQs

Package last updated on 29 Mar 2018

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc