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

tsConfig target:"ES2022" causes reference error on Safari v15.6 again #13395

Closed
andybastian opened this issue Jul 28, 2023 · 1 comment
Closed
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@andybastian
Copy link

Describe the bug

Hi, like in this issue before:

#12302

the target was set back to ES2022:
(f5129d8#diff-b55cdbef4907b7045f32cc5360d48d262cca5f94062e353089f189f4460039e0)

This causes reference errors in Safari 15.6.

Environment

Testet on MacOS Catalina 10.15.7
Safari 15.6.1

Reproducer

No response

Angular version

16.1.2

PrimeNG version

16.02

Build / Runtime

TypeScript

Language

TypeScript

Node version (for AoT issues node --version)

18.16.1

Browser(s)

Safari 15.6.1

Steps to reproduce the behavior

No response

Expected behavior

No response

@andybastian andybastian added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Jul 28, 2023
@andybastian
Copy link
Author

Update for everyone else who might find this. The issue has nothing to do with primeng. The problem in our case was due to the browserlist configuration, which excluded Safari 15.6.1. We had to reduce the settings to a lower version. Since the error was triggered within primeng calendar component, we were directed to a wrong path.

The issue is also discussed in at angular: angular/angular-cli#24355

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

1 participant