What is the package.json file?
The package.json file is a JSON file that stores metadata for a Node.js project. It contains information such as the project's name, version, description, and dependencies. This file is used by npm, the Node.js package manager, to manage the project's dependencies and scripts. It also contains scripts that can be run using npm, such as start, test, and build scripts. The package.json file is an essential part of any Node.js project, as it provides a way to manage dependencies and scripts in a standardized way.
- 1
The package.json file is the heart of a Node.js system. This file holds the metadata for a particular project. The package.json file is found in the root directory of any Node application or module
- 2
You can edit the parameters when you create a Node.js project.
Scenario Questions
0-2 years experience
- 1If you need to add a new library to your Node project, where would you make the change and what command would you run to update the file?
- 2Suppose you run `npm start` and the script fails because the `scripts` section is missing in package.json. How would you fix it?
- 3What happens if you delete the `main` field from package.json and then require the package from another project?
2-5 years experience
- 1You notice that after adding a dependency, the CI build fails due to a version conflict. Walk me through how you would investigate and resolve it using package.json.
- 2During a feature rollout, a teammate modifies the `scripts` section and the build script starts using a different Node version. How would you detect the cause and prevent it?
- 3Explain why the `package-lock.json` file is generated alongside package.json and what could go wrong if it's omitted from source control.
5-8 years experience
- 1Our monorepo contains dozens of services, each with its own package.json. How would you design a strategy to keep dependency versions consistent across the repo while allowing independent releases?
- 2We need to reduce startup time for a large Node application. Discuss how you could leverage fields in package.json (like `exports` or `type`) to improve module loading and what trade‑offs exist.
- 3If we want to enforce that all packages use a specific linting configuration, how would you use package.json fields and tooling to enforce this across multiple teams?
8+ years experience
- 1The company is migrating from npm to a new internal package registry and wants to phase out legacy package.json fields. Describe the architectural considerations and migration plan you would propose.
- 2How would you set up a governance model for package.json schemas across many micro‑services to ensure security, licensing compliance, and reproducible builds at scale?
- 3When introducing a new language feature like ES modules across all Node services, what changes to package.json would you mandate, and how would you coordinate the rollout to minimize disruption?
Follow-up Questions
- What exact JSON would you add to include a new dependency?
- How would you verify that a script change works across dev, CI, and production?
- Which tools do you use to audit the dependencies listed in package.json?