-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
feat(v8/angular): Merge angular and angular-ivy packages and start Angular support at v14 #11091
Conversation
0f6b33f
to
d9a6ad3
Compare
size-limit report 📦
|
ad0886f
to
6c36876
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work and kudos for figuring out Vitest!
I think this is in a good state; Will give it a spin with a couple of test apps and then we can 🚢 it!
6de10d1
to
b67eeb5
Compare
b67eeb5
to
2199c11
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested this PR in
- A simple NG17 test app ✅
- A simple NG14 test app ✅
- My personal side project running on NG14 ✅
- In the reproduction app of Jest starts throwing
Jest encountered an unexpected token
in Angular #9448 which appears to fix the issue ✅
As expected (but still good that it's confirmed), the SDK now no longer works in a simple NG13 app, meaning 14 will be the definitive lower bound for v8. I think this is perfectly acceptable.
Let's merge this - great work!
…gular support at v14 (getsentry#11091) Start using vitest for better ESM support (since Angular 13) closes getsentry#9830 --------- Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
Start using vitest for better ESM support (since Angular 13)
closes #9830