Skip to content

Conversation

@clydin
Copy link
Member

@clydin clydin commented Feb 17, 2021

Some schematic only packages may not have entry points defined (main/exports). These type of packages will now be correctly resolved when attempting to locate update migrations.

Fixes #20032

…ints

Some schematic only packages may not have entry points defined (`main`/`exports`).  These type of packages will now be correctly resolved when attempting to locate update migrations.

Fixes angular#20032
@clydin clydin added the target: patch This PR is targeted for the next patch release label Feb 17, 2021
@google-cla google-cla bot added the cla: yes label Feb 17, 2021
@clydin clydin requested a review from alan-agius4 February 17, 2021 02:29
@alan-agius4 alan-agius4 added the action: merge The PR is ready for merge by the caretaker label Feb 17, 2021
@filipesilva filipesilva merged commit 3d99468 into angular:master Feb 17, 2021
@clydin clydin deleted the fix-update-migration-no-entry branch February 17, 2021 18:44
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ng update fails for custom schematic with "An unhandled exception occurred: Cannot find module"

3 participants