VSCode Extension Resolver

VSCode extension build failures in Nix occur when an extension source is unavailable or misconfigured. Test sources systematically across nixpkgs, vscode-marketplace, and open-vsx in priority order, adding one failing extension at a time to isolate the issue and identify a reliable source.

Hash mismatches and attribute-not-found errors happen when an extension's source URL is stale, moved, or doesn't exist in the queried marketplace. The resolver catalogs these error types and recommends alternative sources from nixpkgs curated, vscode-marketplace, or open-vsx.

Yes. Incremental testing isolates failures by adding one extension at a time to your nix configuration, allowing you to identify which extension causes the build to fail and which source resolves it before updating modules/vscode/extensions.nix.

Test multiple sources in order: nixpkgs curated extensions first, then vscode-marketplace, then open-vsx. The resolver systematically checks each source, handles marketplace 500 errors, and recommends the first working source for your extension identifier.

Yes. The resolver enforces function signatures that include nix-vscode-extensions and verifies it's present in your environment before diagnosing extension failures and updating your configuration.