You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure where to post this, so I apologize if this is the incorrect location.
Issue Summary:
I am experiencing difficulties while trying to install the @bigcommerce/stencil-cli package using npm. The primary issue is that the installation consistently times out with an ETIMEDOUT error, indicating a network-related problem. I have made several attempts to resolve the issue, but it persists despite multiple troubleshooting efforts.
Troubleshooting Steps Taken:
Network Connectivity:
Ensured stable internet connection and verified access to other websites and resources.
Retry Installation:
Repeatedly attempted to run npm install -g @bigcommerce/stencil-cli to account for potential transient network issues.
Proxy Configuration:
Configured npm with proxy settings using npm config set proxy and npm config set https-proxy to accommodate proxy requirements if applicable.
Use Different Registry:
Tried changing the npm registry to a different one, such as the Yarn registry, using npm config set registry.
VPN Usage:
Attempted to install the package while using a VPN service to bypass potential network restrictions.
Offline Installation:
Downloaded the @bigcommerce/stencil-cli package manually from the npm website and attempted installation from a local file.
Alternative Network Connection:
Tried performing the installation from a different network or Wi-Fi connection to eliminate potential network-specific issues.
Checked Firewall and Antivirus:
Verified that firewall or antivirus software was not blocking npm requests.
Updated npm and Node.js:
Ensured npm and Node.js were updated to the latest versions using npm install -g npm@latest.
Traceroute Diagnostic:
Performed a network diagnostic using the traceroute (or tracert on Windows) command to analyze the network path and identify potential issues. The traceroute did not reveal any apparent network problems.
Despite extensive troubleshooting efforts, the issue persists, and I am seeking further assistance to resolve the problem. Any additional guidance or suggestions to address this network-related issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
I should add to this that I have worked on BigCommerce Stencil for years and years and this just started happening a few months ago. I have no clue what I changed.
I am not sure where to post this, so I apologize if this is the incorrect location.
Issue Summary:
I am experiencing difficulties while trying to install the @bigcommerce/stencil-cli package using npm. The primary issue is that the installation consistently times out with an ETIMEDOUT error, indicating a network-related problem. I have made several attempts to resolve the issue, but it persists despite multiple troubleshooting efforts.
Troubleshooting Steps Taken:
Network Connectivity:
Ensured stable internet connection and verified access to other websites and resources.
Retry Installation:
Repeatedly attempted to run npm install -g @bigcommerce/stencil-cli to account for potential transient network issues.
Proxy Configuration:
Configured npm with proxy settings using npm config set proxy and npm config set https-proxy to accommodate proxy requirements if applicable.
Use Different Registry:
Tried changing the npm registry to a different one, such as the Yarn registry, using npm config set registry.
VPN Usage:
Attempted to install the package while using a VPN service to bypass potential network restrictions.
Offline Installation:
Downloaded the @bigcommerce/stencil-cli package manually from the npm website and attempted installation from a local file.
Alternative Network Connection:
Tried performing the installation from a different network or Wi-Fi connection to eliminate potential network-specific issues.
Checked Firewall and Antivirus:
Verified that firewall or antivirus software was not blocking npm requests.
Updated npm and Node.js:
Ensured npm and Node.js were updated to the latest versions using npm install -g npm@latest.
Traceroute Diagnostic:
Performed a network diagnostic using the traceroute (or tracert on Windows) command to analyze the network path and identify potential issues. The traceroute did not reveal any apparent network problems.
Despite extensive troubleshooting efforts, the issue persists, and I am seeking further assistance to resolve the problem. Any additional guidance or suggestions to address this network-related issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered: