Skip to content

Fix blank page: set VSCODE_DEV=1 for dev workbench template - #4

Merged
danialsamiei merged 1 commit into
mainfrom
devin/1771257507-fix-dev-mode
Feb 16, 2026
Merged

danialsamiei merged 1 commit into
mainfrom
devin/1771257507-fix-dev-mode

Conversation

@danialsamiei

Copy link
Copy Markdown
Collaborator

Fix blank page: set VSCODE_DEV=1 for dev workbench template

Summary

The site at https://ide.orcest.ai/ renders a blank page because the server expects bundled assets (workbench.css, nls.messages.js) that don't exist. These are only produced by the full packaging pipeline (gulp vscode-web-min), but the Dockerfile uses npm run compile which only compiles TypeScript to out/.

Setting VSCODE_DEV=1 makes isBuilt return false, which switches the server to use workbench-dev.html — a template that loads CSS dynamically via import maps instead of requiring a pre-bundled CSS file.

Review & Testing Checklist for Human

  • Audit side effects of VSCODE_DEV=1 in production. This flag controls isBuilt which is checked in many places beyond just the HTML template selection — it affects static file caching (ETAG vs immutable), extension loading, product.overrides.json loading, settings sync, and likely other behaviors. Grep for isBuilt and VSCODE_DEV across the codebase to assess whether any of these side effects are unacceptable for your deployment.
  • Verify the page actually loads after deploy. This fix is inferred from code analysis only — it has NOT been tested in the Render.com environment. After merge, confirm https://ide.orcest.ai/ renders the VS Code workbench (not a blank page or error).
  • Check CSS loading performance. The dev template uses ICSSDevelopmentService which runs ripgrep at server startup to discover all .css files. Verify this doesn't cause excessive startup latency or fail silently in the Docker container.
  • Consider replacing with a proper production build long-term. This is a workaround. The correct fix is to use the full VS Code web packaging pipeline to produce bundled assets, which would allow running without VSCODE_DEV=1.

Notes

npm run compile does not produce bundled workbench.css or nls.messages.js
(those require the full packaging pipeline). Setting VSCODE_DEV=1 makes
the server use workbench-dev.html which loads CSS dynamically via import
maps, matching the compile-only build output.

Co-Authored-By: Danial Piterson <danial.samiei@gmail.com>
@devin-ai-integration

Copy link
Copy Markdown

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@danialsamiei
danialsamiei merged commit 755beb6 into main Feb 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant