Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reliably trigger VSCode extension rebuild #4162

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

owtaylor
Copy link
Contributor

Description

The code to trigger a rebuild on missing extension.js added in #3276
turns out not to be entirely reliable because esbuild sometimes falls back to full-contents comparison rather than using the modtime. To fix this, include a buildTimestamp file in the input, and rewrite that when we want to trigger a rebuild.

Testing instructions

What this fixes is that when you launching the extension debug mode from vscode (after the first time), sometimes vscode-extension:esbuild-notify just spins and spins and out/extension.js is never written.

cc: @halfline

Copy link

netlify bot commented Feb 14, 2025

Deploy Preview for continuedev canceled.

Name Link
🔨 Latest commit a11be01
🔍 Latest deploy log https://app.netlify.com/sites/continuedev/deploys/67b0da958232860008664b11

The code to trigger a rebuild on missing extension.js added in
continuedev#3276
turns out not to be entirely reliable because esbuild sometimes
falls back to full-contents comparison rather than using the modtime.
To fix this, include a buildTimestamp file in the input, and
rewrite that when we want to trigger a rebuild.
@owtaylor owtaylor force-pushed the trigger-esbuild-with-file branch from 54832d2 to 6475f8d Compare February 14, 2025 16:03
sestinj
sestinj previously approved these changes Feb 15, 2025
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