Share your experience using npm

We use the product as a packet manager for orchestration and dashboard management. It helps in running the development server.

The product's most valuable feature is dependency installation.

The product should be compatible with various programming languages, including both native and upcoming languages. There should be an extension for C++ language as many customers prefer it for the backend development.

We have been using npm for two and a half years.

It is a stable product.

The product's scalability depends on the backend architecture. We have around 1000 users for it.

While working with C++, we can directly write down dependencies and get URLs. Comparatively, npm is easier to use. We just have to write the configuration to the package installed.

The product's initial setup process is easy. It takes ten minutes to complete.

It is a good solution. I rate it a nine out of ten.

Our primary use case for this solution is to build the code. So if an application runs on the environment, we install the libraries from GitHub. We use NPM for that, install it and then build. If the build is ready, we copy it, deploy it, build the application, and then update the client. We deploy the solution on-premises.

The product can be improved by updating the libraries. Previously, libraries were missing, and we had difficulty building them. So a cleaner version would be helpful. Additionally, we have found many types of version issues.

We have been using this solution for five years.

The solution is stable.

The solution is scalable, and approximately ten users are utilizing this solution in our organization.

We do not have experience with customer service and support.

The initial setup is straightforward.

We use the open-source version, so it is free.

I rate the solution an eight out of ten. The solution is good, but the library could be updated.