Skip to content
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.

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

fix(material/core): prevent ng update schematic from checking node_modules #28152

Merged
merged 1 commit into from
Nov 20, 2023

Conversation

crisbeto
Copy link
Member

Fixes that the ng update schematic was cheking node_modules and .d.ts files when looking for legacy imports. Also changes the logic to only look at top-level imports and exports, as well as any files that don't include @angular/material at all.

Fixes #28150.

@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release labels Nov 19, 2023
@crisbeto crisbeto changed the title fix(material/core): preventing ng update schematic from checking node_modules fix(material/core): prevent ng update schematic from checking node_modules Nov 19, 2023
…dules

Fixes that the `ng update` schematic was cheking `node_modules` and .d.ts files when looking for legacy imports. Also changes the logic to only look at top-level imports and exports, as well as any files that don't include `@angular/material` at all.

Fixes angular#28150.
@crisbeto crisbeto force-pushed the 28150/schematic-node-modules branch from 7216fce to c1ce3eb Compare November 19, 2023 08:16
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Nov 20, 2023
@crisbeto crisbeto removed the request for review from andrewseguin November 20, 2023 10:34
@crisbeto crisbeto merged commit da692b1 into angular:main Nov 20, 2023
crisbeto added a commit that referenced this pull request Nov 20, 2023
…dules (#28152)

Fixes that the `ng update` schematic was cheking `node_modules` and .d.ts files when looking for legacy imports. Also changes the logic to only look at top-level imports and exports, as well as any files that don't include `@angular/material` at all.

Fixes #28150.

(cherry picked from commit da692b1)
@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 Dec 21, 2023
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 P2 The issue is important to a large percentage of users, with a workaround target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug(update): v17 migration process node_modules
2 participants