Skip to content

fix(@angular/build): enhance Vitest resolution for optimal package loading #31816

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
Nov 14, 2025
Merged

fix(@angular/build): enhance Vitest resolution for optimal package loading #31816

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
4 changes: 4 additions & 0 deletions packages/angular/build/src/builders/unit-test/runners/vitest/plugins.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,6 +124,10 @@ export async function createVitestConfigPlugin(
noDiscovery: true,
include: options.optimizeDepsInclude,
},
resolve: {
mainFields: ['es2020', 'module', 'main'],
Copy link
Contributor

@hybrist hybrist Nov 14, 2025

Choose a reason for hiding this comment

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

Given that this contains some values that could change over time (e.g. es2020), can we decrease the risk of getting out of sync somehow?

Copy link
Member Author

@clydin clydin Nov 14, 2025

Choose a reason for hiding this comment

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

Those are there for older APF packages. We stopped using that in newer APF revisions. It's just default now with a single code variant.

conditions: ['es2015', 'es2020', 'module'],
},
};

const { optimizeDeps, resolve } = config;
Expand Down
Loading