-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
bug(ALL): The Stackblitz links for Angular 16.1.0 are all completely broken #27297
Closed
1 task done
lztetreault-dev opened this issue
Jun 13, 2023
· 1 comment
· Fixed by angular/material.angular.io#1215
Closed
1 task done
bug(ALL): The Stackblitz links for Angular 16.1.0 are all completely broken #27297
lztetreault-dev opened this issue
Jun 13, 2023
· 1 comment
· Fixed by angular/material.angular.io#1215
Labels
area: material.angular.io
P2
The issue is important to a large percentage of users, with a workaround
Comments
lztetreault-dev
added
the
needs triage
This issue needs to be triaged by the team
label
Jun 13, 2023
lztetreault-dev
changed the title
bug(ALL): The stackblitz links for Angular 16.1.0 are all completely broken
bug(ALL): The Stackblitz links for Angular 16.1.0 are all completely broken
Jun 13, 2023
crisbeto
added
P2
The issue is important to a large percentage of users, with a workaround
area: material.angular.io
and removed
needs triage
This issue needs to be triaged by the team
labels
Jun 14, 2023
crisbeto
added a commit
to crisbeto/material.angular.io
that referenced
this issue
Jun 14, 2023
Updates the repo to Angular 16.1 final to resolve some build issues. Fixes angular/components#27297.
crisbeto
added a commit
to angular/material.angular.io
that referenced
this issue
Jun 14, 2023
Updates the repo to Angular 16.1 final to resolve some build issues. Fixes angular/components#27297.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
DigitalMaestro89
added a commit
to DigitalMaestro89/material.angular.io
that referenced
this issue
Apr 23, 2024
Updates the repo to Angular 16.1 final to resolve some build issues. Fixes angular/components#27297.
alexeagle
pushed a commit
to alexeagle/material2
that referenced
this issue
Nov 6, 2024
Updates the repo to Angular 16.1 final to resolve some build issues. Fixes angular#27297.
alexeagle
pushed a commit
to alexeagle/material2
that referenced
this issue
Dec 12, 2024
Updates the repo to Angular 16.1 final to resolve some build issues. Fixes angular#27297.
alexeagle
pushed a commit
to alexeagle/material2
that referenced
this issue
Dec 16, 2024
Updates the repo to Angular 16.1 final to resolve some build issues. Fixes angular#27297.
alexeagle
pushed a commit
to alexeagle/material2
that referenced
this issue
Dec 18, 2024
Updates the repo to Angular 16.1 final to resolve some build issues. Fixes angular#27297.
josephperrott
pushed a commit
that referenced
this issue
Dec 18, 2024
Updates the repo to Angular 16.1 final to resolve some build issues. Fixes #27297.
alexeagle
pushed a commit
to alexeagle/material2
that referenced
this issue
Dec 18, 2024
Updates the repo to Angular 16.1 final to resolve some build issues. Fixes angular#27297.
kseamon
pushed a commit
to kseamon/material2
that referenced
this issue
Dec 18, 2024
Updates the repo to Angular 16.1 final to resolve some build issues. Fixes angular#27297.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area: material.angular.io
P2
The issue is important to a large percentage of users, with a workaround
Is this a regression?
The previous version in which this bug was not present was
16.0.4
Description
All of the linked Stackblitz examples on https://material.angular.io fail to compile on
16.1.0
Reproduction
StackBlitz link:
Steps to reproduce:
Expected Behavior
The examples render successfully.
Actual Behavior
The page fails to load and spits out errors like the following
Environment
The text was updated successfully, but these errors were encountered: