1. Package name
name identifies the package; required to publish to a registry.
"name": "my-app"Typorithm · easy
Step 1 of 8 · intro card
Modules & npm
package.json is the project manifest: name and version identify it, type picks the module system, scripts maps names to shell commands run via npm run, and dependencies lists runtime packages with semver ranges.
Every Node project has a package.json — the manifest describing the package. name and version identify it, and type chooses CommonJS or ES Modules.
The scripts object maps a name to a shell command. Running npm run build executes the build entry's command, with node_modules/.bin on the PATH so local tools resolve.
dependencies lists the packages your app imports at runtime, each pinned to a semver range like ^4.19.0. npm reads this list to install the right versions.
name + version identify the package (semver).
type "module" switches .js to ES Modules.
scripts maps names to commands run by npm run.
{
"name": "my-app",
"version": "1.0.0",
"type": "module",
"scripts": {
"build": "tsc",
"test": "vitest"
},
"dependencies": {
"express": "^4.19.0"
}
}Connect each part of the code to the concept before you type.
name identifies the package; required to publish to a registry.
"name": "my-app"version follows semver (major.minor.patch).
"version": "1.0.0"type set to module makes .js files ES Modules instead of CommonJS.
"type": "module"Each scripts entry maps a name to a shell command run by npm run.
"build": "tsc"dependencies lists packages your app needs at runtime, with a semver range.
"express": "^4.19.0"Read the concept map and follow the code breakdown.
Type the implementation, repair mistakes and work through every recall exercise.
Use the final check without hints; revisit weak concepts in short practice sessions.