-
Notifications
You must be signed in to change notification settings - Fork 24.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
Angular.dev Playground is broken #55298
Comments
Looks like all the tutorials are broken, not just the playground |
devversion
added a commit
to devversion/angular
that referenced
this issue
Apr 15, 2024
When we started fixing the version mismatch with local 1st-party packages, we also re-routed all dependencies like `@lezer/javascript` into `adev/node_modules`. This works fine, but results in a different version mismatch because the codemirror dependencies may resolve the Angular version from `/node_modules`- causing some subtle complex runtime error. This commmit fixes this by only re-routing dependenices that have dependency on e.g. `@angular/core` into `adev/node_modules`. Fixes angular#55298.
devversion
added a commit
to devversion/angular
that referenced
this issue
Apr 15, 2024
When we started fixing the version mismatch with local 1st-party packages, we also re-routed all dependencies like `@lezer/javascript` into `adev/node_modules`. This works fine, but results in a different version mismatch because the codemirror dependencies may resolve the Angular version from `/node_modules`- causing some subtle complex runtime error. This commit fixes this by only re-routing dependencies that have dependency on e.g. `@angular/core` into `adev/node_modules`. Fixes angular#55298.
devversion
added a commit
to devversion/angular
that referenced
this issue
Apr 15, 2024
When we started fixing the version mismatch with local 1st-party packages, we also re-routed all dependencies like `@lezer/javascript` into `adev/node_modules`. This works fine, but results in a different version mismatch because the codemirror dependencies may resolve the Angular version from `/node_modules`- causing some subtle complex runtime error. This commit fixes this by only re-routing dependencies that have dependency on e.g. `@angular/core` into `adev/node_modules`. Fixes angular#55298.
pkozlowski-opensource
pushed a commit
that referenced
this issue
Apr 15, 2024
When we started fixing the version mismatch with local 1st-party packages, we also re-routed all dependencies like `@lezer/javascript` into `adev/node_modules`. This works fine, but results in a different version mismatch because the codemirror dependencies may resolve the Angular version from `/node_modules`- causing some subtle complex runtime error. This commit fixes this by only re-routing dependencies that have dependency on e.g. `@angular/core` into `adev/node_modules`. Fixes #55298. PR Close #55349
iteriani
pushed a commit
to iteriani/angular
that referenced
this issue
Apr 16, 2024
When we started fixing the version mismatch with local 1st-party packages, we also re-routed all dependencies like `@lezer/javascript` into `adev/node_modules`. This works fine, but results in a different version mismatch because the codemirror dependencies may resolve the Angular version from `/node_modules`- causing some subtle complex runtime error. This commit fixes this by only re-routing dependencies that have dependency on e.g. `@angular/core` into `adev/node_modules`. Fixes angular#55298. PR Close angular#55349
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
Yes
Description
When I navigate to https://angular.dev/playground the code does not populate in
main.ts
andgame.html
.Please provide a link to a minimal reproduction of the bug
https://angular.dev/playground
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: