🤿 Introduction to a new world for Salesforce Developers and Architects

Welcome to my notebook from the perspective of a Salesforce Architect and Developer.

While this is not a detailed guide on the Node.js world, it is meant to provide you with a comprehensive overview of the essentials that you need to know in the context of the Salesforce ecosystem.

As Salesforce developers & architects, it is important to be familiar with these tools, but we don't need to become experts in them.

<aside> 📢 My goal is to give you a solid understanding of the most significant concepts and features for your daily tasks.

</aside>

I welcome any feedback you have, so feel free to leave comments and let me know if there's anything I missed.

What is node and what is npm?

Starting with the basics:

1. Node is a runtime application that allows running Javascript code outside the browser, making it possible to create server-side applications with JavaScript.
2. More important for us is that NPM (Node Package Manager) is a package manager for Node.js that allows developers to easily install, update, and manage packages (also known as modules or libraries).
   1. NPM provides a vast ecosystem of packages that can be used to quickly build applications, including frameworks, libraries, and utilities.
   2. Developers, like the Salesforce internal team can publish their own packages to the NPM registry for others to use (paid subscription required).
   3. NPM is installed along with Node.js, and can be used from the command line to manage packages and dependencies for a Node.js project.

So, the takeaways for you and me are:

1. NPM is part of the node family of tools.
2. While you will use some commands for LWC development with npm you will barely use node.

🍟 Using npm, npm run, npx to manage dependencies

The first exposure, that we have as developers, is installing the dependencies that we got when we are dealing with a package.json file.

The required command to install those dependencies from the NPM registry is: