[jnzlab]

Description

The TypeScript setup section provides a tsconfig.json using "module": "nodenext" and demonstrates ESM import syntax in src/app.ts, but doesn't mention that package.json also needs "type": "module" set. Without it, TypeScript treats .ts files as CommonJS by default and throws ECMAScript imports and exports cannot be written in a CommonJS file under 'verbatimModuleSyntax'. (ts1295) when following the guide as written. This adds the missing step so the example works out of the box.

Changes

• Added a new step between the middleware-types warning and the tsconfig.json block explaining that "module": "nodenext" requires package.json to declare "type": "module"
• Included a package.json code snippet showing the required field
• Added a warning callout explaining the exact error users will hit if this step is skipped

Type of change

• Documentation fix/improvement

[netlify]

✅ Deploy Preview for expressjscom-preview ready!

Name	Link
🔨 Latest commit	f6a884b
🔍 Latest deploy log	https://app.netlify.com/projects/expressjscom-preview/deploys/6add04feacad7a78138b9a97
😎 Deploy Preview	https://deploy-preview-2464--expressjscom-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 93 (🔴 down 4 from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[krzysdz]

There is also another problem - while Node.js can detect and run .js/.ts files as ES Modules, npm init sets "type": "commonjs" by default, effectively blocking the detection mechanism.

[jnzlab]

Thanks @krzysdz, good catch. That makes the missing step even more important: since this page has readers run npm init first, their package.json will already have "type": "commonjs", so the guide as written fails even though Node itself could detect ESM. I've updated the wording to say to change "type" to "module" (with npm pkg set type=module) rather than just add it.

[krzysdz]

This feels to verbose for a simple step in a "getting started" guide. It should be enough to just write that the type must be changed to "module", because the TypeScript examples use the module syntax.