npm Reviews

NPM is used to trigger your APM while in the background.

Node.js and NPM come as a bundle. When Node is installed NPM is automatically installed with the latest version.

The most valuable feature of NPM is to trigger APMs.

NPM can improve the package manager. For the packages we download for our APM studio to trigger our APM driver, it would benefit if we could have the latest version of NuGet Package Manager within the package manager control. For example, Visual Studio would be good. Then it would be easy for us to get the package manager from there instead of Googling it out and matching it with the current version. It would be less time-consuming for us.

It would be helpful if we could download the latest NPM packages from the Visual Studio marketplace.

I have been using NPM for approximately five years.

NPM is stable.

The scalability of NPM is good.

We have approximately 2,000 to 3,000 people who use NPM in my company which includes developers.

I have not contacted the technical support of NPM.

NPM is an open-source solution.

My advice to others is if you download the latest version of Node onto your system and the latest version of NPM by default. Later, you will have to check whether it is compatible with your APM. At this time you can upgrade or downgrade the NPM version depending on your needs.

It is a requirement for us to work with NPM for our APM to run, we need to have that NPM as a base. It's a precondition for us to have NPM installed on our systems.

I rate NPM a nine out of ten.

We use npm for most of the microservices that we write. With any new APIs, we always create them with npm.

It's an open-source setting that's very scalable and easily approachable.

I like that you can plug in many features to my product.

Some of the libraries that we try to use in npm have issues with security. Also, because it's an open-source solution, I think there are lots of challenges with security. So, the security layer could be improved.

I've been using npm for the past four years.

It is a stable solution. Before jumping into the major version, they'll roll out a beta version. They'll make sure that things are working first and that it's stable.

It's very scalable.

The initial setup is pretty easy.

It's an open-source solution, and there are no hidden fees.

There are a lot of features that are very fast in npm, even though it was developed 10 or 12 years back. It comes with a bundle or library, so your development time will radically reduce to half. If you need to spin up a new server or you need to have a developer at minimum cost, it can be easily achieved within npm.

Overall, I give npm a nine out of ten.

We are creating a branch, and making the changes. We work with the review comments and manage the pull requests, and if you want to delete the branch or the details related to the branch.

NPM is user-friendly, has a smooth workflow, and has great security. The reversal build, gendered build, migrated PCA, and CT, is excellent.  

I would like to see the architectural picture flow enhanced. When the flow is wrong, it will impact all of the details. I would like to see compatible versions, and what new features they will be providing. If it is a useful feature I can merge it. If it is not a usable feature, then I can ignore the newer version.

I have been using NPM for the past three and half years.

NPM is stable and the workflow is easy.

NPM is scalable.

NPM is complex and difficult without checking the compatibility of a particular version. Once we have checked the compatibility it is easy to understand or easy to install. The deployment itself took around seven minutes from start to finish.

The licensing cost is around one hundred and fifty dollars on a quarterly basis.

I would rate NPM 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.