1. Home
  2. Forum
  3. Angular - EJ 2
  4. npm install @syncfusion/ej2-angular-lists Fails with ENOTFOUND Error Unable to Resolve npm.syncfusion.com

npm install @syncfusion/ej2-angular-lists Fails with ENOTFOUND Error Unable to Resolve npm.syncfusion.com

npm install @syncfusion/ej2-angular-lists --save

npm error code ENOTFOUND

npm error syscall getaddrinfo

npm error errno ENOTFOUND

npm error network request to https://npm.syncfusion.com/@syncfusion%2fej2-angular-lists failed, reason: getaddrinfo ENOTFOUND npm.syncfusion.com

npm error network This is a problem related to network connectivity.

npm error network In most cases you are behind a proxy or have bad network settings.

npm error network

npm error network If you are behind a proxy, please make sure that the

npm error network 'proxy' config is set properly. See: 'npm help config'

npm error A complete log of this run can be found in: /Users/amara/.npm/_logs/2025-01-28T12_09_10_429Z-debug-0.log


3 Replies 1 reply marked as answer
PM Prasanth Madhaiyan Syncfusion Team January 30, 2025 11:46 AM UTC

Hi Amara,

 

Greetings from Syncfusion support.


We have reviewed your query and understand that you are facing issues while installing the packages. We suggest you ensure the following possible causes and try the given solutions.

 

Possible Causes:

 

  1. Incorrect or Unavailable Registry URL in .npmrc
    • Your .npmrc file might have an incorrect or outdated registry URL for Syncfusion.
    • Run npm config get registry to check if it's set correctly.
  2. Blocked by Corporate Firewall or Security Software
    • If you’re working within a corporate network, firewalls or security policies may block access to npm.syncfusion.com.
    • Try connecting via a mobile hotspot to rule this out.
  3. Corrupt npm Cache
    • Sometimes, npm cache corruption can cause network-related errors.
    • Try running npm cache clean --force and reinstalling.
  4. Node.js or npm Version Issue
    • An outdated or incompatible Node.js or npm version can cause installation failures.
    • Run node -v and npm -v to check, and update if necessary.
  5. Incorrect Global npm Configuration
    • Check if a global .npmrc file or npm config settings are interfering.
  6. Conflicting npm Packages or Lock Files
    • Existing package-lock.json or node_modules might be causing conflicts.
    • Try deleting node_modules and package-lock.json, then reinstall:

 

Troubleshooting Steps

 

  • Clear the npm cache using npm cache clean --force.
  • Check your .npmrc file using npm config list.
  • Upgrade npm and Node.js (npm install -g npm and ensure Node.js is the latest stable version) as we mentioned in our system requirements documentation manner.
  • Disable VPN or any firewall temporarily to see if the issue persists.
  • Follow our installation guidelines steps to install packages properly.

Regards,

Prasanth Madhaiyan.


AM Amara January 30, 2025 12:19 PM UTC

this solve my problem thanks

npm config set @syncfusion:registry https://registry.npmjs.org/


Marked as answer
KG Kalpana Ganesan Syncfusion Team January 31, 2025 04:49 AM UTC

Hi Amara,


You are welcome. Please get back to us for further assistance.


Loader.
Up arrow icon