René's URL Explorer Experiment


Title: Angular Router zero-segment group replay can create duplicate outlet siblings and exhaust SSR workers · Issue #70997 · angular/angular · GitHub

Open Graph Title: Angular Router zero-segment group replay can create duplicate outlet siblings and exhaust SSR workers · Issue #70997 · angular/angular

X Title: Angular Router zero-segment group replay can create duplicate outlet siblings and exhaust SSR workers · Issue #70997 · angular/angular

Description: Which @angular/* package(s) are the source of the bug? router Is this a regression? No Description ImportantThis is a separate recognizer failure from #70932 and #70933. Those get their snapshot fan-out from empty-path routes matching th...

Open Graph Description: Which @angular/* package(s) are the source of the bug? router Is this a regression? No Description ImportantThis is a separate recognizer failure from #70932 and #70933. Those get their snapshot fa...

X Description: Which @angular/* package(s) are the source of the bug? router Is this a regression? No Description ImportantThis is a separate recognizer failure from #70932 and #70933. Those get their snapshot fa...

Opengraph URL: https://github.com/angular/angular/issues/70997

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Angular Router zero-segment group replay can create duplicate outlet siblings and exhaust SSR workers","articleBody":"### Which @angular/* package(s) are the source of the bug?\n\nrouter\n\n### Is this a regression?\n\nNo\n\n### Description\n\n> [!IMPORTANT]\n> This is a separate recognizer failure from #70932 and #70933. Those get their snapshot fan-out from empty-path routes matching the outlets a URL names, and become fatal when URL-sized state is copied into each snapshot. Here, the Router builds a tree that violates its own NG04006 invariant: two siblings targeting the same outlet under one parent. No query parameters or matrix parameters are required. The minimal reproducer is 28 bytes.\n\nA parenthesised group that consumes no segments is transparent to recognition. `processSegmentGroup()` hands it to `processChildren()` with the same `config` and the same `parentRoute`:\n\n```ts\nif (segmentGroup.segments.length === 0 && segmentGroup.hasChildren()) {\n  return this.processChildren(injector, config, segmentGroup, parentRoute);\n}\n```\n\nThe group costs no configured level and creates no node. Its contents are matched against the same route array again. Nest the groups and the array matches once per group, and every match lands in the snapshot tree as a sibling. Those siblings carry the same outlet name. NG04006 already says that is invalid.\n\nThe check that says so does not run on every list:\n\n```ts\nconst mergedChildren = mergeEmptyPathMatches(children);\nif (typeof ngDevMode === \"undefined\" || ngDevMode) {\n  checkOutletNameUniqueness(mergedChildren);\n}\n```\n\nThat gate is gone in an optimized build, so production builds a tree development would have rejected. The OOM below uses that.\n\nThe second gap has nothing to do with production. `mergeEmptyPathMatches()` takes two nodes that matched the same empty-path route, concatenates their children and normalizes the result recursively. That list never reaches `checkOutletNameUniqueness()`. The call site only sees what `processChildren()` got back, not the children inside the nodes on it.\n\nThis route is enough:\n\n```ts\n{\n  path: 'a',\n  children: [{\n    path: '', outlet: 'detail',\n    children: [{ path: ':id', component: DetailPanel }],\n  }],\n}\n```\n\n`/a/(detail:1//x:/(detail:2))`, 28 bytes, navigates. With `ngDevMode` **on**:\n\n```text\ndetail@''\n├── primary@:id  url=1\n└── primary@:id  url=2\n```\n\nTwo siblings on the primary outlet, under one parent, in a development build, no error. The tree is identical with `ngDevMode` off. The two gaps are independent: ungating the existing call site stops the replay below and leaves this untouched.\n\nThe route configuration is four lines. No empty-path level, no nesting, no guards, no resolvers:\n\n```ts\n{\n  path: 'dashboard',\n  component: Dashboard,\n  children: [{ path: ':id', outlet: 'detail', component: DetailPanel }],\n}\n```\n\nThe URL is a balanced tree of these groups. Wrapper names are one character and can repeat between levels, since `UrlSegmentGroup.children` is keyed by outlet name:\n\n```text\n/dashboard/(detail:1//x:/(detail:1//x:/(...)//y:/(...))//y:/(...))\n```\n\nSnapshots counted with a build instrumented only at `createSnapshot()`. One request, 511 groups, 7,669 bytes:\n\n| Fan-out | Panel contains                   |  Nodes |  Tree steps |\n| ------: | -------------------------------- | -----: | ----------: |\n|       1 | nothing                          |  1,024 |     659,205 |\n|       2 | one aside                        |  2,046 |   2,624,000 |\n|       4 | aside with two widgets           |  4,090 |  10,470,405 |\n|      13 | three panels, three widgets each | 13,288 | 110,406,675 |\n\nThe count is `2 * groups * matched_routes * fan_out + 2` in every row. `createSnapshot()` runs twice per match and the root snapshot is built directly,\nso the retained tree is half the count plus one.\n\nAn equal-byte control that reuses one wrapper name instead of distinct ones builds **236** nodes and walks **35,700** tree steps. Same-named siblings overwrite each other in `UrlSegmentGroup.children`, so the replay collapses. With no named outlet in the replayed set, recognition builds 8 nodes. **13,288 snapshots against 236, from one request of the same length.** That is the finding. The counts below are how far it goes.\n\nFan-out is application-controlled, not attacker-controlled. None of it appears in the URL. Every request count below is from the fan-out 13 shape. The four-line one is fatal too, but needs several times as many requests and I did not measure that\nprecisely.\n\nI tested Angular **22.2.0 on Node.js 24.16.0** with `outputMode: \"server\"`, against the three-panel configuration, at both request-line limits:\n\n|   Path bytes |     128 MiB |     256 MiB |          512 MiB |\n| -----------: | ----------: | ----------: | ---------------: |\n|      7,669 B | 10 requests | 20 requests | over 40 requests |\n|     15,349 B |  6 requests | 10 requests |      20 requests |\n\nEvery failure was V8 hitting its own heap limit, not the container being reaped. The equal-byte control survived all of them. Six requests of 15 KB is not a burst any rate limit would notice, and the 8 KB payload reaches the same heap for less total traffic.\n\nA `development` build answers 404 and the worker is unaffected, so this shape does not show up locally. The merge case above does not show up locally either, and that one is not about the build at all.\n\nTo isolate where the memory goes I ran the same payload with the existing check ungated. Four concurrent requests at 256 MiB:\n\n| Build         |   Peak RSS | Status |\n| ------------- | ---------: | -----: |\n| stock         |    296 MiB |    302 |\n| check ungated | **73 MiB** |    404 |\n\n73 MiB is the worker at rest. Recognition throws on the first duplicated sibling and the tree is never built, so the snapshot tree is where the memory goes. This is an ablation, not a proposal. It does not touch the merge case above.\n\n#### Secondary: the same gap under `withRouterResources()`\n\nThe replay is not the only thing that produces siblings sharing an outlet name. A flat URL of distinct names does it too, because `processSegmentAgainstRoute()` lets an empty-path route in the primary outlet match every named outlet the URL declares:\n\n```ts\n{ path: '', component: Shell, children: [\n    { path: ':id', component: Report, resources: threeResources },\n    { path: '', outlet: 'side', component: Panel },\n] }\n```\n\n```text\n/(a:1//b:1//c:1//...)\n```\n\nThat inflation is #70932's. What is new is that with `withRouterResources()` enabled, each duplicated instance costs a factory and its loaders. Three resources on 300 ms timers:\n\n|   Path bytes | Outlets | Heap | Requests | stock | with #70933 |\n| ---: | ---: | ---: | ---: | --- | --- |\n| 7,995 B | 1,246 | 256 MiB | 5 | OOM | OOM |\n| 16,073 B | 2,400 | 256 MiB | 3 | OOM | OOM |\n| 7,995 B | 1,246 | 512 MiB | 12 | OOM | OOM |\n| 16,073 B | 2,400 | 512 MiB | 8 | OOM | OOM |\n\nLoaders that resolve immediately kill nothing. The wait is what costs.\n\n`withRouterResources()` is developer preview and opt-in, and the flat fan-out belongs to #70932, so this is secondary. It is here because it shows the same gap costing memory instead of only producing a wrong tree.\n\n#### Backend amplification\n\nIf the route carries a `resolve`, the resolver runs once per activated route, so once per replayed group. `resolveData()` uses `concatMap`, so they run one after another and the request holds its worker slot for the sum.\n\n```ts\n{\n  path: 'dashboard',\n  component: Dashboard,\n  children: [{\n    path: ':id', outlet: 'detail', component: DetailPanel,\n    resolve: { item: itemResolver },   // fetch(API + '/item/' + id)\n  }],\n}\n```\n\n```text\n/dashboard/(detail:1//x:/(detail:1//x:/(detail:1)//y:/(detail:1))//y:/(...))\n```\n\nA backend answering in 250 ms, one request, no concurrency:\n\n|       Path bytes | Groups | Backend queries | Worker slot held | HTTP status |\n| ---------------: | -----: | --------------: | ---------------: | ----------: |\n|            230 B |     15 |              15 |         3,924 ms |         302 |\n|            950 B |     63 |              63 |        15,994 ms |         302 |\n|          1,910 B |    127 |             127 |        32,069 ms |         302 |\n| 1,910 B, control |    127 |               7 |         1,927 ms |         302 |\n\nQueries equal groups at every size. One 1,910-byte GET becomes **127** queries against whatever the resolver talks to, against 7 for the control. One is in flight at a time, so the 127 spread over 32 seconds. That is about 4 a second and buries nothing on its own. What one request costs reliably is a worker slot and a connection, held for those 32 seconds. The query load scales with concurrency.\n\nThe worker stays up the whole time, so what degrades is the service behind it. \nThat traffic comes from the SSR tier's own address, with its own credentials, and carries nothing the attacker controls. The client gets a 302 with a 20-byte `Location`. A 1,910-byte URI and a 32-second response both get logged, but nothing connects the queries back to the request.\n\nI measured `resolve` only.\n\n### Please provide a link to a minimal reproduction of the bug\n\nhttps://github.com/SkyZeroZx/angular-router-zero-segment-replay-lab\n\n```bash\n./scripts/validate.sh counts     # snapshot counts\n./scripts/validate.sh devprod    # development against production\n./scripts/validate.sh ablation   # stock, #70933, the gate\n./scripts/validate.sh backend    # the resolver table\n```\n","author":{"url":"https://github.com/SkyZeroZx","@type":"Person","name":"SkyZeroZx"},"datePublished":"2026-09-28T04:17:04Z","url":"https://github.com/angular/angular/issues/70997"}

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322
route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:15c2d705-02ca-93d6-6fc2-8b16f7a06195
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idA31E:1F8B56:8BFE99:C61982:6AFDC9C1
html-safe-nonce1b759261a8608d82ec9f73636a7cca86bf5597493bc741f250eac4263cda939c
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBMzFFOjFGOEI1Njo4QkZFOTk6QzYxOTgyOjZBRkRDOUMxIiwidmlzaXRvcl9pZCI6IjQzODE4MDk0OTY0MTA2NzE1NTMiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ==
visitor-hmac27fcfd0258a2863f53b6a6ab1119634af21fdc86ee69c296c2bb88533742f300
hovercard-subject-tagissue:5609233277
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angular/70997/issue_layout
twitter:imagehttps://opengraph.githubassets.com/528c0ccdee089521dc607a6a33ea1c9cd5e273691116ab523d5639866982d7a9/angular/angular/issues/70997
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/528c0ccdee089521dc607a6a33ea1c9cd5e273691116ab523d5639866982d7a9/angular/angular/issues/70997
og:image:altWhich @angular/* package(s) are the source of the bug? router Is this a regression? No Description ImportantThis is a separate recognizer failure from #70932 and #70933. Those get their snapshot fa...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernameSkyZeroZx
hostnamegithub.com
expected-hostnamegithub.com
None9ab00cc3b4fa90bbd3da70765dd38efc23cfa9d9b0930e41feea2bf67f60ecaf
turbo-cache-controlno-preview
go-importgithub.com/angular/angular git https://github.com/angular/angular.git
octolytics-dimension-user_id139426
octolytics-dimension-user_loginangular
octolytics-dimension-repository_id24195339
octolytics-dimension-repository_nwoangular/angular
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id24195339
octolytics-dimension-repository_network_root_nwoangular/angular
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release1b795ba060b92691fc16c5a12cf2bf95e83432b4
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/angular/angular/issues/70997#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fangular%2Fangular%2Fissues%2F70997
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fangular%2Fangular%2Fissues%2F70997
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=angular%2Fangular
Reloadhttps://github.com/angular/angular/issues/70997
Reloadhttps://github.com/angular/angular/issues/70997
Reloadhttps://github.com/angular/angular/issues/70997
angularhttps://github.com/angular
angularhttps://github.com/angular/angular
Codehttps://github.com/angular/angular
Issues833 (833)https://github.com/angular/angular/issues
Pull requests126 (126)https://github.com/angular/angular/pulls
Discussionshttps://github.com/angular/angular/discussions
Actionshttps://github.com/angular/angular/actions
Projectshttps://github.com/angular/angular/projects
Security and quality40 (40)https://github.com/angular/angular/security
Insightshttps://github.com/angular/angular/insights
https://github.com/angular/angular
New issuehttps://github.com/login?return_to=https://github.com/angular/angular/issues/70997
New issuehttps://github.com/login?return_to=https://github.com/angular/angular/issues/70997
#71055https://github.com/angular/angular/pull/71055
#70998https://github.com/angular/angular/pull/70998
Angular Router zero-segment group replay can create duplicate outlet siblings and exhaust SSR workershttps://github.com/angular/angular/issues/70997#top
#71055https://github.com/angular/angular/pull/71055
#70998https://github.com/angular/angular/pull/70998
area: routerhttps://github.com/angular/angular/issues?q=state%3Aopen%20label%3A%22area%3A%20router%22
needsTriagehttps://github.com/angular/angular/milestone/83
https://github.com/SkyZeroZx
SkyZeroZxhttps://github.com/SkyZeroZx
on Sep 28, 2026https://github.com/angular/angular/issues/70997#issue-5609233277
#70932https://github.com/angular/angular/issues/70932
#70933https://github.com/angular/angular/pull/70933
#70932https://github.com/angular/angular/issues/70932
#70933https://github.com/angular/angular/pull/70933
#70932https://github.com/angular/angular/issues/70932
https://github.com/SkyZeroZx/angular-router-zero-segment-replay-labhttps://github.com/SkyZeroZx/angular-router-zero-segment-replay-lab
angular-robothttps://github.com/apps/angular-robot
area: routerhttps://github.com/angular/angular/issues?q=state%3Aopen%20label%3A%22area%3A%20router%22
gemini-triagedhttps://github.com/angular/angular/issues?q=state%3Aopen%20label%3A%22gemini-triaged%22
on Sep 28, 2026https://github.com/angular/angular/issues/70997#event-31962648004
ngbothttps://github.com/apps/ngbot
needsTriagehttps://github.com/angular/angular/milestone/83
on Sep 28, 2026https://github.com/angular/angular/issues/70997#event-31962649183
SkyZeroZxhttps://github.com/SkyZeroZx
on Sep 28, 2026https://github.com/angular/angular/issues/70997#event-32021315123
fix(router): reject duplicate outlets in production buildshttps://github.com/SkyZeroZx/angular/commit/acd7c4071c6ed4561bdcf6ced81c0dca13afc9a7
https://docs.github.com/articles/closing-issues-via-commit-messages
acd7c40https://github.com/SkyZeroZx/angular/commit/acd7c4071c6ed4561bdcf6ced81c0dca13afc9a7
fix(router): reject duplicate outlets in production buildshttps://github.com/SkyZeroZx/angular/commit/f87c936fd7c973e6a5867301b959e1a465884a25
https://docs.github.com/articles/closing-issues-via-commit-messages
f87c936https://github.com/SkyZeroZx/angular/commit/f87c936fd7c973e6a5867301b959e1a465884a25
atscotthttps://github.com/atscott
completedhttps://github.com/angular/angular/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Acompleted
#70998https://github.com/angular/angular/pull/70998
on Sep 28, 2026https://github.com/angular/angular/issues/70997#event-32035145759
atscotthttps://github.com/atscott
on Sep 28, 2026https://github.com/angular/angular/issues/70997#event-32035145984
fix(router): reject duplicate outlets in production buildshttps://github.com/angular/angular/commit/82a4289d05cd5153b167d816eb36e0b64bf52c4f
https://docs.github.com/articles/closing-issues-via-commit-messages
82a4289https://github.com/angular/angular/commit/82a4289d05cd5153b167d816eb36e0b64bf52c4f
fix(router): reject duplicate outlets in production buildshttps://github.com/angular/angular/commit/3b6796f1ab279ab26b33d4e29e576d3b1762ccf5
https://docs.github.com/articles/closing-issues-via-commit-messages
3b6796fhttps://github.com/angular/angular/commit/3b6796f1ab279ab26b33d4e29e576d3b1762ccf5
fix(router): reject duplicate outlets in production buildshttps://github.com/angular/angular/commit/6489ca5d8460a9ed8ae4daf7b0c24ec052f20398
https://docs.github.com/articles/closing-issues-via-commit-messages
6489ca5https://github.com/angular/angular/commit/6489ca5d8460a9ed8ae4daf7b0c24ec052f20398
fix(router): reject duplicate outlets in production buildshttps://github.com/angular/angular/commit/cd8efcb924d26464bc42ee436d39e10784cfc240
https://docs.github.com/articles/closing-issues-via-commit-messages
cd8efcbhttps://github.com/angular/angular/commit/cd8efcb924d26464bc42ee436d39e10784cfc240
fix(router): require outlets to match a route before processing child…https://github.com/atscott/angular/commit/fa2b295bc5fe014efb02d447ac0b982f465f12ba
https://docs.github.com/articles/closing-issues-via-commit-messages
fa2b295https://github.com/atscott/angular/commit/fa2b295bc5fe014efb02d447ac0b982f465f12ba
fix(router): require outlets to match a route before processing child…https://github.com/atscott/angular/commit/f5e7a51468c030d29253bad42897cf0a88b92be7
https://docs.github.com/articles/closing-issues-via-commit-messages
f5e7a51https://github.com/atscott/angular/commit/f5e7a51468c030d29253bad42897cf0a88b92be7
fix(router): require outlets to match a route before processing child…https://github.com/atscott/angular/commit/85c24b85119ab82f6298f056a685ac6e96fe48f4
https://docs.github.com/articles/closing-issues-via-commit-messages
85c24b8https://github.com/atscott/angular/commit/85c24b85119ab82f6298f056a685ac6e96fe48f4
fix(router): require outlets to match a route before processing child…https://github.com/atscott/angular/commit/60251bb7a9e5f4ef89eb90f6c75616c4d2bf4b90
https://docs.github.com/articles/closing-issues-via-commit-messages
60251bbhttps://github.com/atscott/angular/commit/60251bb7a9e5f4ef89eb90f6c75616c4d2bf4b90
fix(router): require outlets to match a route before processing child…https://github.com/atscott/angular/commit/f95d5f04c66c3193103779b80c49a06335cf346c
https://docs.github.com/articles/closing-issues-via-commit-messages
f95d5f0https://github.com/atscott/angular/commit/f95d5f04c66c3193103779b80c49a06335cf346c
fix(router): require outlets to match a route before processing child…https://github.com/atscott/angular/commit/a47785d569c5a9082cf0238bb66f7d323b3a60ed
https://docs.github.com/articles/closing-issues-via-commit-messages
a47785dhttps://github.com/atscott/angular/commit/a47785d569c5a9082cf0238bb66f7d323b3a60ed
fix(router): require outlets to match a route before processing child…https://github.com/atscott/angular/commit/e528586f1387b976c1de972857c042d46bd0dc56
https://docs.github.com/articles/closing-issues-via-commit-messages
e528586https://github.com/atscott/angular/commit/e528586f1387b976c1de972857c042d46bd0dc56
fix(router): require outlets to match a route before processing child…https://github.com/atscott/angular/commit/aa2d61ce1e0c4213cb1642c9e5a27b59b877dab6
https://docs.github.com/articles/closing-issues-via-commit-messages
aa2d61chttps://github.com/atscott/angular/commit/aa2d61ce1e0c4213cb1642c9e5a27b59b877dab6
fix(router): require outlets to match a route before processing child…https://github.com/atscott/angular/commit/d501dfb1b39672b5f91adf5132d5a59232d5a10d
https://docs.github.com/articles/closing-issues-via-commit-messages
d501dfbhttps://github.com/atscott/angular/commit/d501dfb1b39672b5f91adf5132d5a59232d5a10d
fix(router): require outlets to match a route before processing child…https://github.com/atscott/angular/commit/2d4a137913c5a04d9237a24fcecd3f267a84704b
https://docs.github.com/articles/closing-issues-via-commit-messages
2d4a137https://github.com/atscott/angular/commit/2d4a137913c5a04d9237a24fcecd3f267a84704b
fix(router): require outlets to match a route before processing child…https://github.com/atscott/angular/commit/c78355bf0d8020a7009ec7693ac07c151f418b9f
https://docs.github.com/articles/closing-issues-via-commit-messages
c78355bhttps://github.com/atscott/angular/commit/c78355bf0d8020a7009ec7693ac07c151f418b9f
fix(router): require outlets to match a route before processing child…https://github.com/atscott/angular/commit/f0cddea2a912816dac03fadda4c9c4e5909cd190
https://docs.github.com/articles/closing-issues-via-commit-messages
f0cddeahttps://github.com/atscott/angular/commit/f0cddea2a912816dac03fadda4c9c4e5909cd190
fix(router): require outlets to match a route before processing child…https://github.com/atscott/angular/commit/f8b2d18f8d0fea04b903eb7fe89d67342bee5b3a
https://docs.github.com/articles/closing-issues-via-commit-messages
f8b2d18https://github.com/atscott/angular/commit/f8b2d18f8d0fea04b903eb7fe89d67342bee5b3a
fix(router): require outlets to match a route before processing child…https://github.com/angular/angular/commit/b6bf6504adab1a78cc62ad8402f6bed229e620bd
https://docs.github.com/articles/closing-issues-via-commit-messages
b6bf650https://github.com/angular/angular/commit/b6bf6504adab1a78cc62ad8402f6bed229e620bd
fix(router): require outlets to match a route before processing child…https://github.com/angular/angular/commit/e9bf52aa03a3b9b302c33ffbc967ef0e1de5fb79
https://docs.github.com/articles/closing-issues-via-commit-messages
e9bf52ahttps://github.com/angular/angular/commit/e9bf52aa03a3b9b302c33ffbc967ef0e1de5fb79
fix(router): require outlets to match a route before processing child…https://github.com/angular/angular/commit/b0d2ba0f54e21cb57ea5a0ca0d8e6065f28e23a0
https://docs.github.com/articles/closing-issues-via-commit-messages
b0d2ba0https://github.com/angular/angular/commit/b0d2ba0f54e21cb57ea5a0ca0d8e6065f28e23a0
atscotthttps://github.com/atscott
on Sep 30, 2026https://github.com/angular/angular/issues/70997#event-32174765514
fix(router): require outlets to match a route before processing child…https://github.com/angular/angular/commit/a83f8119acd466b524ae0113096ed188358d6d6c
a83f811https://github.com/angular/angular/commit/a83f8119acd466b524ae0113096ed188358d6d6c
https://github.com/apps/angular-automatic-lock-bot
angular-automatic-lock-bothttps://github.com/apps/angular-automatic-lock-bot
on Oct 29, 2026https://github.com/angular/angular/issues/70997#issuecomment-6484199574
automatic conversation locking policyhttps://github.com/angular/angular/blob/f0fbced1c55bc8b8ed9df01cea99df42f3e7eae3/contributing-docs/auto-issue-locking.md
angular-automatic-lock-bothttps://github.com/apps/angular-automatic-lock-bot
on Oct 29, 2026https://github.com/angular/angular/issues/70997#event-34533737650
Sign up for freehttps://github.com/signup?return_to=https://github.com/angular/angular/issues/70997
Sign in to commenthttps://github.com/login?return_to=https://github.com/angular/angular/issues/70997
area: routerhttps://github.com/angular/angular/issues?q=state%3Aopen%20label%3A%22area%3A%20router%22
needsTriageNo due datehttps://github.com/angular/angular/milestone/83
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.