Dependencies are split between runtime and development-time-only packages. The package.json file contains the list of dependencies that a Node project depends upon.

For reference, here is the documentation on the package.json structure. For the sake of brevity, we won’t dive into all of the properties, but we’ll take a look at the most important ones. The package.json file holds key information about the Node project. For example, we’re shipping a Node script in the eCars sample application that deploys the Salesforce project to an org, then configures and deploys a couple of related Heroku apps. We typically use it for formatting, linting, and testing, but you can get creative and do much more. You can use it for a variety of tasks in your local development environment and CI. You won’t be shipping a Node server application, but the power of Node also resides in the fact that it can be used as a OS-agnostic scripting engine. You may find yourself asking: “Why would I need to know about Node.js if I’m working on a Salesforce project?” The answer is that you can do without it, but you’ll miss out in terms of developer experience and code quality. Let’s take a look at the scripts and dependencies that support those actions. In this post, we’re going to tour the key aspects of Node.js in a Salesforce project you’ll learn how you can use it to format, lint, run LWC tests, and execute pre-commit checks. One key tool is a set of Node.js scripts and utilities that enhance your developer experience. When you create a new project with the Salesforce CLI’s force:project:create command or with VS Code’s command palette, the default project state provides you with some useful tools.

Node js projects