npm install fails - Cannot access private registry dependency

[Vansman23]

npm install fails - Cannot access private registry dependency

Description

Unable to install dependencies for kpaste project due to network errors when trying to fetch ksuite-bridge package from Infomaniak's private registry.

Steps to Reproduce

1. Clone the repository: git clone https://github.com/infomaniak/kpaste.git
2. Navigate to project directory: cd kpaste/
3. Run: npm install

Expected Behavior

Dependencies should install successfully, allowing the project to be set up and run locally.

Actual Behavior

npm install fails with network errors when trying to fetch the ksuite-bridge@0.3.3 package from https://verdaccio.dev.infomaniak.ch/infomaniak/ksuite-bridge/

Error Output

npm ERR! syscall getaddrinfo
npm ERR! errno ENOTFOUND
npm ERR! network request to https://verdaccio.dev.infomaniak.ch/infomaniak/ksuite-bridge/-/ksuite-bridge-0.3.3.tgz failed, reason: getaddrinfo ENOTFOUND verdaccio.dev.infomaniak.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 If you are behind a proxy, please make sure that the 'proxy' config is set properly. See: 'npm help config'

Environment

• OS: Debian 12 (also tested on Windows and WSL)
• Node.js version: 19.9.0
• npm version: 9.6.3
• Network: Various environments tested (fresh VM, Windows, WSL)

Root Cause

The package ksuite-bridge appears to be hosted on Infomaniak's private npm registry (verdaccio.dev.infomaniak.ch) which is not publicly accessible. This prevents external contributors from installing dependencies and setting up the project locally.

Possible Solutions

1. Make the dependency public: Publish ksuite-bridge to the public npm registry
2. Remove private dependency: Replace or remove the dependency on ksuite-bridge
3. Provide public alternative: Create a public version without internal dependencies
4. Update documentation: Add setup instructions for contributors on how to access the private registry (if intended)
5. Mock/stub the dependency: For development purposes, provide a public stub version

Additional Context

This issue prevents external contributors from:

• Setting up a local development environment
• Contributing to the project
• Testing the application

The error occurs consistently across different operating systems and network environments, suggesting this is a project configuration issue rather than a local network problem.

Impact

• Blocks external contributions
• Prevents community adoption
• Makes the open-source project unusable without Infomaniak internal access

[L3o-pold]

We'll look into it internally to see how we can improve this.

[zifeo]

See #15 for a potential approach.