Understand package files and local scripts.
- package.json
- npm scripts
- dependency pinning
- build tools
A package manifest documents scripts and dependencies. Use a tool only when it solves a real need, such as running tests or bundling modules. Understand the distinction between project dependencies and development tools. Keep examples runnable without a large framework so language and browser behavior remain visible.
Blindly installing packages increases maintenance and supply-chain surface.
Create a package.json with a test script and run a small Node example without adding dependencies.
Open example.html in a browser and edit example.js. Save, refresh, and use the Console and debugger to inspect values.
Run npm start in this folder to execute node-example.mjs using the script in package.json. This example has no external dependencies.
- Explain the core idea in your own words without reading the code.
- Change one input and predict the output before running it.
- Test one boundary or failure case, then record what you changed.