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

Mark compatibility with angular 16 peer #3351

Closed
wants to merge 1 commit into from
Closed

Mark compatibility with angular 16 peer #3351

wants to merge 1 commit into from

Conversation

robertIsaac
Copy link
Contributor

Checklist

Description

update peer dependencies to support angular 16

@HarryAlvarado28
Copy link

Correct the pipeline to approve the change, it is necessary! 💥🐞

@robertIsaac
Copy link
Contributor Author

Correct the pipeline to approve the change, it is necessary! 💥🐞

can you explain to me why my changes made the test fails? I tried even on master it's the same locally
can you trigger the pipeline manually for master branch and let me know if it passes or not?

@wis-dev
Copy link

wis-dev commented May 17, 2023

@robertIsaac you neet to update .github/workflows/test.yml file with v16 version.

V15 example 👉🏼 https://github.com/angular/angularfire/pull/3291/files

@ntherndon97
Copy link

Any updates on this getting fixed to have merged into master so we can update to Angular 16?

@robertIsaac
Copy link
Contributor Author

@robertIsaac you neet to update .github/workflows/test.yml file with v16 version.

V15 example 👉🏼 https://github.com/angular/angularfire/pull/3291/files

there are many many problems that needs to be fixed, I can't touch the test file before making sure it actually working fine

if it won't be accepted like that, I will have to close it, I tried to fix the build locally, but nothing really work, this repo is too much old and currently it's not working on any node versions, I tried 12, 14, 16, and 18 it always fails with different errors

I can try to upgrade to Angular 16 to make sure it works at node 18 in another PR, but I have no idea how much time and effort it will need, so I can't promise anything

@robertIsaac
Copy link
Contributor Author

this is a nightmare to deal with in windows, nothing has been done in this repo to consider it working on windows, it's unfeasible for me to contribute on the project, so I'm closing the PR

@nicky-lenaers
Copy link

@robertIsaac Have you tried working with WSL? It may solve your Windows-related issues. I think your contributions are much appreciated!

@robertIsaac
Copy link
Contributor Author

@robertIsaac Have you tried working with WSL? It may solve your Windows-related issues. I think your contributions are much appreciated!

I tried before, it's a different nightmare
I will just stop trying to contribute to any repo that doesn't support windows

@jamesdaniels
Copy link
Member

Sorry for the troubles here, we're overdue to clean up the test suite and release a major—the test matrix is getting long in the tooth. We're going to start releasing majors in step with Angular which should really help.

@robertIsaac
Copy link
Contributor Author

Sorry for the troubles here, we're overdue to clean up the test suite and release a major—the test matrix is getting long in the tooth. We're going to start releasing majors in step with Angular which should really help.

If you are committed to keep the repo compatible with windows, I'd like to help tackle all the issues
I see you already released a version compatible with Angular 16

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants