-
Notifications
You must be signed in to change notification settings - Fork 12
test: try 20-next #292
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
base: main
Are you sure you want to change the base?
test: try 20-next #292
Conversation
✅ Deploy Preview for plugin-angular-universal-demo ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
import { appConfig } from './app.config' | ||
import { serverRoutes } from './app.routes.server' | ||
|
||
const serverConfig: ApplicationConfig = { | ||
providers: [provideServerRendering(), provideServerRoutesConfig(serverRoutes)], | ||
providers: [provideServerRendering(withRoutes(serverRoutes))], |
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 had to be migrated manually (checked how newly scaffolded project with npx @angular/cli@next new
sets things up) as ng update @angular/cli @angular/core --next
didn't cover it (initially it resulted in trying to import no longer existing provideServerRoutesConfig
function)
Note - test on Node 18 fail because it's unsupported with Angular 20:
Test setup would need adjustment to skip tests using Angular 20 when on not supported Node version to continue testing previous Angular major versions (or maybe drop testing this node version as it's no longer maintained anyway) |
This is just optimistic change trying out:
And ensuring min node supported version in Angular 20 is used to build the app