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
{{ message }}
This repository has been archived by the owner on Mar 20, 2024. It is now read-only.
Hello I downloaded the repo and wanted to run it according to the documentation.
But unfortunately I get the following error when running npm install
npm ERR! syscall getaddrinfo
npm ERR! errno ENOTFOUND
npm ERR! network request to https://nexus3.eap.bit.admin.ch/repository/npm-all/yargs-parser/-/yargs-parser-4.2.1.tgz failed, reason: getaddrinfo ENOTFOUND nexus3.eap.bit.admin.ch
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'
We are not behind any proxy.
The text was updated successfully, but these errors were encountered:
PLEASE NOTE THAT THESE GUIDELINES ARE OUTDATED AND NOT SUPPORTED ANYMORE.
According to issue #661, there is a renewal project under way that should have been published very soon (#661 (comment)).
But that was in August 2021. Since then the publication just get's pushed back, last time from January 1st to July.
If you really need to use this project despite all this, you have multiple options:
a) Use the build folder and manually update or remove the Javascript content
b) Replace https://nexus3.eap.bit.admin.ch/repository/npm-all/ with https://registry.npmjs.org/
c) Remove the package-lock.json before running npm install
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello I downloaded the repo and wanted to run it according to the documentation.
But unfortunately I get the following error when running npm install
We are not behind any proxy.
The text was updated successfully, but these errors were encountered: