TS/JS development in devcontainer is broken

[slartibart70]

I'm running vscode on linux in a devcontainer.
Development in Javascript/Typescript was flawless until recently - meaning that cross referencing of functions or Ctrl-clicks on function names do not work any more.
All we have now is a colorful text editor.

Opening the list of running plugins, i'm missing the 'javascript and typescript' plugin in the list. I also have error messages in the debug-console.

This all (same repo, same profile) works perfectly outside the devcontainer - but i really need the isolated environment of the devcontainer for testing (different node versions etc)

I also tried the 'javascript and typescript nightly' plugin (ok in normal mode, not ok in devcontainer)
Any hints on how to proceed?

Version: 1.105.1
Commit: 7d842fb
Date: 2025-10-14T22:33:36.618Z
Electron: 37.6.0
ElectronBuildId: 12502201
Chromium: 138.0.7204.251
Node.js: 22.19.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.16.12-200.fc42.x86_64

[mjbvz]

I tried to reproduce this issue but could not. I do see that error but I don't think it's relevant in this case

If you search @buildin typescript in the extensions view do you see the TypeScript and JavaScript language features extension being install:

If it's completely missing in this list, you may need to try re-installing VS Code inside the container. I believe the Dev Containers: Rebuild Container command will do this

[slartibart70]

Thanks for looking into this,
but i found out the real culprit:

devcontainers/features#1480

This stops vscode installing 'stuff' in the devcontainer which - besides other side effects - causes the problem
In the meantime, i have a workaround in place so i can disable my devcontainer-features and it's working again (for me)
Even with podman 5.7.0-rc1 it's still a problem

One thing to improve in such a situation:
Give better logs to the enduser, or improve the way finding the logs... i know vscode is running in a browser(electron) so for me debugTools makes sense. Still i think this might not be the case for others.

[mjbvz]

Thanks! Good find

I'll go ahead and close this as an upstream issue then. Sounds like the JS/TS extension really is missing or corrupted in this case due to that