@liip/npm-icons
Advanced tools
To get started quickly you can add `liip-npm-icons` dependency to your project:
To get started quickly you can add liip-npm-icons dependency to your project:
npm install liip-npm-icons
You would need to add the following variable to your .env
ICONS_BASE_URL="https://icons.liip.ch"
ICONS_SVG_BASE_URL="https://icons.liip.ch/icons"
ICONS_JSON_URL="https://icons.liip.ch/icons.json"
ICONS_TYPES="regular light"
ICONS_PATH="./assets/icons"
npx icons add <icon-name>
To contribute first clone the project:
git clone git@github.com:liip/npm-icons.git
The tool release-it is used to make a release so it is as simple as running the following command:
npm run release
Our documentation is made with nuxt-content and the docs theme If you want to make any changes you need execute the following commands:
cd docs
npm install
npm run dev
The deployment is made with github pages using static files thanks to
nuxt generate.
If you want to deploy some changes just run npm run release and
then answer yes to the question Do you want to build the docs?
then release-it will run nuxt generate and commit the changes into the
tag commit.
FAQs
Import svg icons using cli
We found that @liip/npm-icons demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
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.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.