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

refactor(@angular/build): Pin the supported browsers in the default browserslist config #28719

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

JeanMeche
Copy link
Member

@JeanMeche JeanMeche commented Oct 25, 2024

In order to deterministic list of supported browser for a given version, we now pin the versions in the browserlists config.

This could fix issue where like in #28707, a minor of Angular broke support for Safari 16, where is previously worked (because the definition of "last 2" got updated to drop Safari 16 with that bump).

This would also address a demand on the fw side angular/angular#54195.

…rowserslist config

In order to deterministic list of supported browser for a given version, we now pin the versions in the browserlists config.

This would also address a demand on the fw side angular/angular#54195.
'Chrome >= 127',
'Edge >= 127',
'Firefox >= 129',
'Safari >= 16',
Copy link
Collaborator

Choose a reason for hiding this comment

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

Note: this matches 16, 17 and 18. Thus, not the last 2 major versions.

@alan-agius4
Copy link
Collaborator

Thanks for this but this would require a wider discussion and certainly the blessing of the framework team, thus let me mark this for further discussion.

@alan-agius4 alan-agius4 added the needs: discussion On the agenda for team meeting to determine next steps label Oct 25, 2024
@JeanMeche
Copy link
Member Author

SGTM, will bring this up in the next fw sync.

@dgp1130
Copy link
Collaborator

dgp1130 commented Oct 30, 2024

We started a conversation about this in Tooling and agree that pinning the version is likely a good thing to do, however there are broader challenges with Angular's current browser support policy which likely should be changed as well. I started a separate conversation about potentially revising that policy and depending on how that goes, we can consider updating the CLI's definition to match in this PR.

@dgp1130 dgp1130 removed the needs: discussion On the agenda for team meeting to determine next steps label Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants