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

@limetech/lime-elements

Package Overview
Dependencies
Maintainers
5
Versions
985
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@limetech/lime-elements

Lime Elements

  • 22.4.0
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
2K
decreased by-18.45%
Maintainers
5
Weekly downloads
 
Created
Source

Lime Elements

This package includes basic components like buttons, loading-spinners, etcetera.

Version semantic-release Commitizen friendly Greenkeeper badge

To start the dev-server, run npm start.

To build the dist build, run npm run build.

Requirements

The "Roboto" font is included for development purposes, but is not included in the published package. This font should be supplied by the consuming application. If not supplied, texts will fall back to suitable alternatives.

Deploy documentation

Documentation is deployed to GitHub Pages when a new release is built by Jenkins. It can also be deployed manually from a Linux or macOS computer. NB! Running the publish script locally will update your git config for the repository with the values of the GIT_AUTHOR_EMAIL and GIT_AUTHOR_NAME environment variables. If you set these to anything other than your own user, you may wish to update your config again after publishing. The script will also make changes to a few files, and will checkout these again at the end. Any uncommitted changes you've made to these files will be lost. The script also removes the local copy of the branch gh-pages.

Follow these steps:

  1. The following environment variables must be set:
  • GIT_AUTHOR_EMAIL - the email address for the user making the commit
  • GIT_AUTHOR_NAME - the name of the user making the commit
  • GH_TOKEN - a GitHub access-token with write-access to the repository
  • GH_USERNAME - the GitHub user to which the above access-token belongs
  1. Run git fetch.
  2. Run git branch and make sure you do not have a local copy of the branch gh-pages. If you do, push anything that should be pushed, and remove the local branch.
  3. From the repo-root, run npm run docz:publish -- --v=<version>, where <version> is the version of lime-elements you are building the documentation for. Any existing documentation for this version number will be overwritten. If no version is supplied, the version will be set to 0.0.0-dev. If --dryRun=true is supplied, the entire script will run, except the push to GitHub.

Get help

  • If you have a general question, or are in need of support, please open a Question issue on GitHub.

Keywords

FAQs

Package last updated on 27 Aug 2019

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