Skip to content

Conversation

clydin
Copy link
Member

@clydin clydin commented Aug 21, 2025

To attempt to workaround Windows pathing issues in the karma configuration migration, the default karma template is now resolved via require.resolve.

@clydin clydin added the target: patch This PR is targeted for the next patch release label Aug 21, 2025
@jkrems jkrems added the action: merge The PR is ready for merge by the caretaker label Aug 21, 2025
clydin added 2 commits August 21, 2025 09:57
…igration

To attempt to workaround Windows pathing issues in the karma configuration
migration, the default karma template is now resolved via `require.resolve`.
…psulation

In some cases it may be needed to override the schematics encapsulation option
for some first-party schematics. While this is not recommended, certain Node.js
functionality may need to be available.
@clydin clydin force-pushed the migrations/karma-win32-workaround branch from 558059f to aacbab0 Compare August 21, 2025 13:59
@clydin clydin linked an issue Aug 21, 2025 that may be closed by this pull request
1 task
@clydin clydin merged commit 12533a8 into angular:main Aug 21, 2025
31 checks passed
@clydin
Copy link
Member Author

clydin commented Aug 21, 2025

This PR was merged into the repository. The changes were merged into the following branches:

@clydin clydin deleted the migrations/karma-win32-workaround branch August 21, 2025 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
action: merge The PR is ready for merge by the caretaker area: @angular/cli area: @schematics/angular target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Karma migration fails migrating to 20.2.0: missing karma.conf.js.template
2 participants