## The symptom
An Encore TypeScript starter template builds with errors and has broken
TypeScript path resolution in VS Code. There is also a weird `encore.dev`
entry inside `node_modules` that VS Code says does not exist.
## What is actually wrong (two things)
1. The `encore.dev` entry in `node_modules` is a **symlink to a folder**, not a
file. That is why VS Code looks confused when you click it. The maintainer
confirmed the symlink layout is correct.
2. The real breakage: the reporter had bind mounted their local project folder
into a prebuilt docker image, which broke the symlink to
`/root/../../encore.dev` and killed module resolution.
## The fix
- Do not bind mount your project over the docker image, or
- if you must, re-create the `encore.dev` symlink so it points at a real folder.
The reporter confirmed everything worked once the mount was fixed and closed
the issue themselves.
## The general lesson
A symlink that points through an absolute path breaks when the container
filesystem layout differs from where the image was built. If module resolution
dies inside a bind-mounted container but the same code works outside it, check
the symlinks in `node_modules` first.