Skip to content

feat: publish conventional web extension artifacts - #6

Closed
peternhale wants to merge 4 commits into
mainfrom
feat-web-artifact-layout
Closed

feat: publish conventional web extension artifacts#6
peternhale wants to merge 4 commits into
mainfrom
feat-web-artifact-layout

Conversation

@peternhale

@peternhale peternhale commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator

Why

Code Builder Web expects web-compatible extensions to publish their browser bundle and runtime assets under the conventional dist/ layout. It also filters top-level out/ directories as desktop build waste.

What changed

  • publish desktop and browser extension entry points under lana/dist
  • resolve webview runtime assets from the same directory
  • update Rollup, Rolldown, VSIX, watch, and debug configuration for the new layout
  • clean intermediate log-viewer output before Rollup builds to prevent stale Rolldown chunks from entering the VSIX
  • add a reproducible pnpm build:vsix target backed by the local @vscode/vsce dependency
  • make pnpm serve:web launch Chromium interactively through vscode-test-web, while keeping the port-3001 server headless for Playwright E2E

Validation

  • pnpm lint
  • pnpm test --runInBand — 1,830 tests
  • pnpm build
  • pnpm build:fast
  • pnpm build:vsix
  • pnpm test:e2e:web — VS Code Web E2E passed
  • verified the resulting VSIX contains 25 current Rollup artifacts and no stale Rolldown-only chunks
  • verified the installed vscode-test-web CLI supports every interactive launcher option used by serve:web

@peternhale
peternhale requested a review from mshanemc August 21, 2026 20:18
@peternhale
peternhale marked this pull request as draft August 21, 2026 20:18
@peternhale
peternhale marked this pull request as ready for review August 24, 2026 12:00
Comment thread .vscode/launch.json
"request": "launch",
"args": ["--extensionDevelopmentPath=${workspaceFolder}/lana"],
"outFiles": ["${workspaceFolder}/lana/out/**/*.js"],
"outFiles": ["${workspaceFolder}/lana/dist/**/*.js"],

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this something we're doing just for us or planning to ship to certinia?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if it would be simpler to let CBW config specify the location by extension?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@peternhale

Copy link
Copy Markdown
Collaborator Author

Closing this approach. Code Builder Web can consume the existing out/ artifact via its distDir configuration, so the repository-wide dist/ migration is unnecessary. The standalone VSIX build command is being retained separately on main.

@peternhale peternhale closed this Aug 24, 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.

2 participants