Skip to content

refactor(@angular/build): show unexpected Sass import resolution errors #27608

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

Merged
merged 1 commit into from
May 8, 2024

Conversation

clydin
Copy link
Member

@clydin clydin commented May 7, 2024

When attempting to resolve a Sass import, failure to read the contents of a directory that is not caused by a non-existent directory will now cause an exception to be thrown. This prevents abnormal situations from being hidden during the build.

A deprecated Sass interface was also replaced and was a type only change.

When attempting to resolve a Sass import, failure to read the contents of a
directory that is not caused by a non-existent directory will now cause
an exception to be thrown. This prevents abnormal situations from being
hidden during the build.

A deprecated Sass interface was also replaced and was a type only change.
@clydin clydin added the target: rc This PR is targeted for the next release-candidate label May 7, 2024
@alan-agius4 alan-agius4 added the action: merge The PR is ready for merge by the caretaker label May 8, 2024
@alan-agius4 alan-agius4 merged commit 7223c3f into angular:main May 8, 2024
33 of 34 checks passed
@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 Jun 8, 2024
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: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants