-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
build(angular): update angular to version 12 #20042
Conversation
Thanks for taking the time to open a PR!
|
53d37be
to
9573e6c
Compare
@@ -1,5 +1,4 @@ | |||
import { Component, OnInit } from '@angular/core' | |||
import '@angular/material/prebuilt-themes/indigo-pink.css' |
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.
This import does not work this way in Angular. And was throwing a linting error
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.
LGTM 🚀
@@ -1,134 +0,0 @@ | |||
const wp = require('@cypress/webpack-preprocessor') |
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'm not sure why this file is in here as I don't see it being used anywhere
import * as path from 'path' | ||
import { AngularWebpackPlugin } from '@ngtools/webpack' |
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.
We need a way to use Webpack 5 now after updating to Angular v 12. This plugin has over 2 million weekly downloads and is essentially built to be an "Webpack 5.x plugin for the Angular Ahead-of-Time compiler"
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.
It sounds like this will be a blocker for merging, right? What's the urgency like for Angular 12.x support?
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.
Yeah I am actively working on this locally. Once I find a solution locally, I will attempt to add these changes here. I will say that when we release Angular CT we need to support the most recent version of Angular which is actually 13. There is a large number of Angular users who use the most recent versions. Currently we are unable to upgrade this app here to 13 though as Angular requires a minimum Node version of 16.10 and we are using 16.5. My plan was to get to 12 and then create a separate PR to get to 13 because of that
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.
Okay, great. Do you mind setting this to draft until it's read for a re-review?
User facing changelog
Updated Angular version from 11 to 12
Additional details
How has the user experience changed?
This should not effect the user experience as Angular CT has not been deployed yet
PR Tasks
cypress-documentation
?type definitions
?cypress.schema.json
?