Skip to content

fix: ensure default sm resolution paths are kept for transpiled extensions #2110

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Oct 21, 2024
Merged

fix: ensure default sm resolution paths are kept for transpiled extensions #2110

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions src/ui/configuration/extensionHostConfigurationResolver.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,19 +46,23 @@ export class ExtensionHostConfigurationResolver
};
}

applyNodeishDefaults(config);

if (config.debugWebWorkerHost) {
config.outFiles = []; // will have a runtime script offset which invalidates any predictions
config.resolveSourceMapLocations = extensionHostConfigDefaults.resolveSourceMapLocations;
}

if (!config.outFiles && pkgJson && folder) {
const outFiles = await guessOutFiles(folder, pkgJson);
if (outFiles) {
config.outFiles = outFiles;
// Ensure the default resolution paths (the entire workspace folder)
// is kept so that transpiled sources work (#2101)
config.resolveSourceMapLocations ??= extensionHostConfigDefaults.resolveSourceMapLocations;
}
}

applyNodeishDefaults(config);

return Promise.resolve({
...extensionHostConfigDefaults,
...config,
Expand Down