Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore(workspace): update sample app to Angular 20#3671

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
markgoho wants to merge3 commits intoangular:main
base:main
Choose a base branch
Loading
frommarkgoho:mgoho/chore/update-angular

Conversation

@markgoho
Copy link
Contributor

@markgohomarkgoho commentedSep 10, 2025
edited
Loading

Checklist

  • Issue number for this PR:update sample app to Angular 20 #3669 (required)
  • Docs included?: no significant changes
  • Test units included?: yes, and they pass now 🤓
  • In a clean directory,yarn install,yarn test run successfully? yes, for thesample directory

Description

Updating sample app to Angular 20

Author's Notes

  • installing angular/fire v20 was fun, I had to initially uninstall it from the sample app, update to Angular 20, then build v20 from source, then add it back in
  • many of the changes are lint-related
  • Karma tests are passing with the inclusion of atest.ts file -- it kept complaining about needing Zone.js even though this is a zoneless app, since there's only 3 tests, we may want to explore Vitest as an alternative
  • sadly, I did need to pass--no-verify when committing this, there are ~350 lint errors in the repo and I didn't want to include those fixes in this change
  • both client and server apps run, no errors appear locally, and most functionality that I could test continues to work
  • many, many updates needed to this app to bring it in line with newer patterns in Angular that have evolved since Signals came out, but we can tackle those in future PRs

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

new file courtesy ofgrok-code-fast-1, we're doing something similar in other sample apps in the project, but if there's something here we don't need, let's call that out


if(isMainModule(import.meta.url)){
// eslint-disable-next-line @typescript-eslint/dot-notation
constport=process.env['PORT']||4000;
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

bothprocess.env.PORT (trying to access a property on an index type) andprocess.env['PORT'] (please use dot notation) have some sort of error associated with it, I went with this option

we may want to take a look at lint rules in the future

Comment on lines +28 to +35
@defer (hydrate on idle) { <app-database /> } @placeholder { Database!
&hellip; } @defer (hydrate on idle) { <app-firestore /> } @placeholder {
Firestore! &hellip; } @defer (hydrate on idle) { <app-functions /> }
@placeholder { Functions! &hellip; } @defer (hydrate on idle) {
<app-messaging /> } @placeholder { Messaging! &hellip; } @defer (hydrate on
idle) { <app-remote-config /> } @placeholder { Remote Config! &hellip; }
@defer (hydrate never) { <app-storage /> } @placeholder { Storage! &hellip;
} @defer (hydrate on idle) { <app-upboats /> } @placeholder { &hellip; }
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

I'd recommend we start usingprettier for formatting (something to think about)

"scripts": {
"ng":"ng",
"start":"firebase emulators:exec --import seed\"ng serve\"",
"start":"npx --yesfirebase-tools@latest emulators:exec --import seed\"ng serve\"",
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

maybe someone had firebase-tools installed globally, but I don't and I'd prefer to follow the pattern I see in the rootpackage.json of installing this on demand

alternatively, we could install the package in thedevDependencies and keep it up to date

@markgoho
Copy link
ContributorAuthor

@jamesdaniels any feedback for this PR?

@markgoho
Copy link
ContributorAuthor

@jamesdaniels should we try to get this in before v21 comes along? 🤓

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@markgoho

[8]ページ先頭

©2009-2025 Movatter.jp