npm Reviews

I have experience in both GitHub and JMeter. I used JMeter in the earlier phase of my career for performance testing for around two to three years, and with GitHub, I have been using it almost every day for 10 years to manage code. In the CI/CD pipeline, we have been using the critical component of GitHub, which is Actions, implementing the CI/CD pipeline.

On GitHub, we have been using Copilot as well, and in GitHub Copilot, we have integrated the MCP servers. So integrating MCP server to generate code and reviewing the PR as well, using GitHub Copilot. I can self-review PR, and we can use it to review another person's PR as well.

I have experience in BrowserStack and I am doing automation with Playwright and Cypress, and these types of tools.

It was a kind of POC where we needed to decide the tool between LambdaTest and BrowserStack, and with these tools, I have been working for four years.

Because we did the POC and in the POC, we compared both of the tools. Then we decided to proceed with BrowserStack because of some advanced features and the bug-free tool experience as well.

npm command-line tools help us to execute the code. If the code is in JavaScript, then we need a Node server which compiles the code into its environment and helps us to run it. That's the main purpose of the Node environment. Using npm commands, if we ever need to pass any tag, for example, we need to run only the sanity suite or the regression suite, then we can pass the parameter into npm commands only to define the suite or the number of the parallel threads. We can pass any environment variable as well from the commands. Into the CI tool, such as GitHub Actions, we also write npm commands only, which help us to trigger the automation.

We have not published a package on npm. However, we have published some libraries onto Cloudsmith. Cloudsmith is a similar thing where we can publish libraries, and it's the sort of reusable code which we publish onto Cloudsmith. Then into our framework, we just need to install the dependency in the same way as we have been doing with npm. After it gets downloaded from Cloudsmith, we can use the same code into our framework. I did the similar thing in my previous project by Cloudsmith.

As of now, my every use case includes automated 1,000+ test cases both in UI and API.

BrowserStack is able to solve every issue which we have been facing, so I would rate it as a 10 out of 10 in terms of my experience.

Regarding pricing, I think the organization takes care of that. I am not really aware of the pricing of this, but I have made some personal projects as well in which I use GitHub Actions for free. We can push our code as well. As of now, I am using the free version for my personal use. For the organization, I think the organization is taking care of the same, so we do not need to bother about it.

Audit capabilities should be improved.

Regarding npm, I think that's all I remember for anything else I would like to add or improve. The only room for improvement for npm is their audit capabilities; otherwise, I am satisfied with the solution.

I have been using GitHub to manage code for 10 years.

We found some issues with BrowserStack as well, and at that time, we used to raise the issue to the BrowserStack support team. They definitely initiated a direct one-to-one call, took our feedback, and the resolution time is very quick. They prioritize the user's feedback, work on it, and then provide the fix in the next release. BrowserStack is a very better tool.

We found some issues with BrowserStack as well, and at that time, we used to raise the issue to the BrowserStack support team. They definitely initiated a direct one-to-one call, took our feedback, and the resolution time is very quick. They prioritize the user's feedback, work on it, and then provide the fix in the next release. BrowserStack is a very better tool.

Regarding GitHub, I have not personally reached the GitHub support team. However, I have seen the GitHub Overflow and Stack Overflow pages where they track the issues as well. I think GitHub, since it's a very big and leading platform in maintaining codebases, should have a good product and support team, or else it won't be easy to be one of the leaders in the world.

Positive

I can talk about BrowserStack regarding the features I find most valuable in LambdaTest.

npm is a 10 out of 10 for me.

I am currently working as a Senior QA Automation Engineer for Cosm. My overall review rating for this experience is 10.

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.

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.