Skip to Content
LicenseActivate License

Activate License

When using Hugeicons Pro icons, activate your license key to unlock all the Pro icons and developer features for your awesome projects.

Pro packages are installed from our private npm registry, npm.hugeicons.com, with npm, pnpm, Yarn or Bun.

🔥 Our custom registry now supports all pro styles 🔥

# Stroke Styles
✨ @hugeicons-pro/core-stroke-rounded
✨ @hugeicons-pro/core-stroke-sharp
✨ @hugeicons-pro/core-stroke-standard
 
# Solid Styles
✨ @hugeicons-pro/core-solid-rounded
✨ @hugeicons-pro/core-solid-sharp
✨ @hugeicons-pro/core-solid-standard
 
# Special Styles
✨ @hugeicons-pro/core-bulk-rounded
✨ @hugeicons-pro/core-duotone-rounded
✨ @hugeicons-pro/core-duotone-standard
✨ @hugeicons-pro/core-twotone-rounded

1. Get Your License Key

Log in or create an account, then open the Tokens tab and copy your Universal License Key.

2. Add the Registry Config

Create this file in your project root, next to package.json. It points to your key through the HUGEICONS_LICENSE_KEY environment variable instead of containing it, so it’s safe to commit.

.npmrc

@hugeicons-pro:registry=https://npm.hugeicons.com/
//npm.hugeicons.com/:_authToken=${HUGEICONS_LICENSE_KEY}

3. Set HUGEICONS_LICENSE_KEY

Add your key to your shell profile, then open a new terminal.

Add to ~/.zshrc or ~/.bashrc:

export HUGEICONS_LICENSE_KEY="your-universal-license-key"

npm, pnpm and Yarn don’t read .env files, so a key that is only in .env won’t be found. Bun is the exception.

4. Install

npm install @hugeicons-pro/core-stroke-rounded

Getting a 401 or 404? See Troubleshooting.

Deploying

Add HUGEICONS_LICENSE_KEY to your platform’s environment variables. Your committed config file does the rest.

Vercel, Netlify and other hosts

  • Vercel: Project Settings → Environment Variables. Enable it for Production, Preview and Development, then redeploy.
  • Netlify: Site configuration → Environment variables, with the Builds scope selected.
  • Cloudflare Pages, Render, Railway, Amplify, Heroku, etc.: add it wherever the platform keeps build-time environment variables.

pnpm 10 or later

pnpm 10+ never reads the token from the committed .npmrc, so the build has to hand it to pnpm first. Set your install command to:

pnpm config set "//npm.hugeicons.com/:_authToken" "$HUGEICONS_LICENSE_KEY" && pnpm install --frozen-lockfile
  • Vercel: Settings → Build & Development Settings → Install Command.
  • Coolify / Railpack: add it as the RAILPACK_INSTALL_CMD environment variable, marked as available at build time. Setting it to just pnpm install won’t work.
  • GitHub Actions and other CI: use it as the install step.

Your build logs show which pnpm version ran. If you pin one with packageManager in package.json, that version is used.

GitHub Actions

Save the key as a repository secret named HUGEICONS_LICENSE_KEY, then pass it to the install step:

- run: npm ci
  env:
    HUGEICONS_LICENSE_KEY: ${{ secrets.HUGEICONS_LICENSE_KEY }}

Use yarn install in place of npm ci as needed, or the pnpm 10+ command for pnpm. GitLab CI and Bitbucket work the same way with a masked variable.

Docker

Pass the key as a build secret. ARG and ENV would leave it readable inside the image.

# syntax=docker/dockerfile:1
COPY package.json package-lock.json .npmrc ./
RUN --mount=type=secret,id=hugeicons_license_key,env=HUGEICONS_LICENSE_KEY npm ci
docker build --secret id=hugeicons_license_key,env=HUGEICONS_LICENSE_KEY .

Keep Your Key Safe

  • Never paste the key itself into .npmrc, .yarnrc.yml, a Dockerfile or CI config.
  • Add .env and .env.* to both .gitignore and .dockerignore.
  • Don’t prefix the variable with NEXT_PUBLIC_, VITE_ or similar. The key is only needed to install packages, never in your app.
  • Leaked a key? Contact us on Discord or at [email protected] to have it rotated.
IntroductionTroubleshooting