Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Angular v13 Upgrade

See original GitHub issue

Bug Report

What is the expected behavior?

What is the current behavior?

What are the steps to reproduce?

Providing a StackBlitz (or similar) is the best way to get the team to see your issue.

StackBlitz starter using latest npm nightly release:

What is the use-case or motivation for changing an existing behavior?

Which versions of Angular, Material, OS, TypeScript, browsers are affected?

Is there anything else we should know?

Issue Analytics

State:
Created 2 years ago
Reactions:37
Comments:34 (8 by maintainers)

Top GitHub Comments

46reactions

CaerusKarucommented, Nov 5, 2021

I’m actively investigating this, but ideally we’d move to the new APF v13 and start vending partial compilation artifacts just like Components and the framework. This is nontrivial work but I’m setting aside some time for it this week. No ETA as of yet though.

44reactions

CaerusKarucommented, Nov 16, 2021

I know this may come as a surprise, but upgrades are not mandatory. There’s nothing saying that you must upgrade tomorrow versus a week from tomorrow, except that you alone would like a new feature or change previously not available. Security patches, for instance, are always backported to supported versions. That being said, --force by definition is an option; whether it is viable for you or not is also up to you alone.

Now all that aside, we are working hard on supporting v13 and APF 13. We have made significant progress in stabilizing the build and are in the process of validating the artifacts through extensive testing. The last thing we want for such a dramatic change is to get it wrong.

Some have suggested just cutting an ordinary v13 release without APF 13. I’d like to avoid that because then we would have to postpone introducing the new package format until v14 at the earliest, and we are incredibly close to getting it right as it is.

I understand you’re all eager to upgrade; I’d like to ask for your patience while we get this wrapped up. Generally speaking, we like to get these things done in line with Angular releases, where we release no later than one week after the framework does. That slipped in this case due to the aforementioned APF/partial compilation changes. Thankfully we don’t expect too many of those over time, and usually we meet our target.