Troubleshooting Installation for Hugeicons Pro

If you encounter installation issues with Hugeicons Pro (e.g., 404 or unauthorized errors), this page will guide you through every possible cause and fix for both local development and popular deployment platforms.

If you're still stuck after trying these steps, join our Discord Support Server (opens in a new tab) for quick help.

1. Typical Error Example

You might see something like this:

npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@hugeicons-pro%2Fcore-stroke-rounded - Not found
npm ERR! 404 '@hugeicons-pro/core-stroke-rounded@*' is not in this registry.

This means your npm client is trying to install from npmjs.org instead of the Hugeicons private registry.

2. Correct .npmrc Setup

Create or edit a .npmrc file in your project root (next to package.json) with:

@hugeicons-pro:registry=https://npm.hugeicons.com/
//npm.hugeicons.com/:_authToken=<YOUR_TOKEN>

Important notes:

• The scope must be @hugeicons-pro (not @hugeicons).
• There must be no extra spaces or quotes.
• The auth token must be on a new line.
• This file must be available at build time in CI/CD too.

Then run:

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

3. Common Mistakes and Fixes

Wrong registry or missing token: Ensure .npmrc contains both lines shown above.

Wrong scope: Packages must start with @hugeicons-pro/.

Token expired: Re-generate from your dashboard and replace it.

Multiple .npmrc files: Global or user-level configs can override your project settings. Run:

npm config get @hugeicons-pro:registry

Expected output:

https://npm.hugeicons.com/

If not, remove the global setting:

npm config delete @hugeicons-pro:registry

Then retry installing.

4. Yarn and pnpm Users

Yarn

Create .yarnrc.yml:

npmScopes:
  hugeicons-pro:
    npmRegistryServer: "https://npm.hugeicons.com"
    npmAuthToken: "<YOUR_TOKEN>"

Then:

yarn add @hugeicons-pro/core-stroke-rounded

pnpm

Add to .npmrc or .pnpmrc:

@hugeicons-pro:registry=https://npm.hugeicons.com/
//npm.hugeicons.com/:_authToken=<YOUR_TOKEN>

Then:

pnpm install

5. Deployment & CI/CD Setup

Private registries often fail in CI/CD because .npmrc isn't found or environment variables aren't set.

Vercel

1. Go to Project Settings → Environment Variables

2. Add:

   • Key: NPM_TOKEN
   • Value: <YOUR_TOKEN>

3. In your project root, include this .npmrc:

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

Vercel will substitute the token during build.

Netlify

1. Add NPM_TOKEN under Build & Deploy → Environment.

2. Add .npmrc with:

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

3. If needed, append during build:

   echo "//npm.hugeicons.com/:_authToken=${NPM_TOKEN}" >> .npmrc
   npm install

Render / Railway / Fly.io

Add the same NPM_TOKEN variable and ensure .npmrc exists in the build context.

6. Local Debugging Steps

If you still get 404 or 401 errors:

1. Clean npm cache:

   npm cache clean --force
2. Remove lockfiles and reinstall:

   rm -rf node_modules package-lock.json
   npm install
3. Check effective registry:

   npm config get @hugeicons-pro:registry
4. Validate token:

   npm whoami --registry=https://npm.hugeicons.com

7. Known Issues with Custom Registries

1. Multiple npmrc layers — npm merges configs in this order: project → user → global → built-in. If another .npmrc sets a different registry, it may override yours. Use npm config list to inspect.

2. CI/CD build cache — Cached builds can keep old .npmrc files. Clear cache between builds.

3. Netlify and Yarn bug — Yarn sometimes ignores .npmrc during Netlify builds. Add a .yarnrc.yml as shown above to ensure registry consistency.

4. NPM CLI bug (older versions) — Some npm 7.x versions ignore scoped registries. Upgrade npm:

npm install -g npm@latest

5. Token not picked up in Docker builds — For Dockerized projects, pass token as ARG:

ARG NPM_TOKEN
RUN echo "//npm.hugeicons.com/:_authToken=${NPM_TOKEN}" > .npmrc

8. Example: Full Next.js Setup

Project structure:

my-app/
├── .npmrc
├── package.json
├── next.config.js

.npmrc:

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

Vercel env variable:

NPM_TOKEN=<YOUR_TOKEN>

Then run:

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

Done! This installs successfully in both local and deployed environments.

9. Need Help?

If you've followed all steps and still have issues, head to our Discord for instant help:

Join the Hugeicons Support Server (opens in a new tab)

Please include:

• Your .npmrc content
• The error message
• Your platform (local / Vercel / Netlify)

Our community and team will guide you right away.