René's URL Explorer Experiment


Title: `@angular/build:unit-test`: with the default jsdom runner and zone.js, an export from a shared chunk is `undefined` when read during class-field initialisation from a spec with an async test · Issue #33728 · angular/angular-cli · GitHub

Open Graph Title: `@angular/build:unit-test`: with the default jsdom runner and zone.js, an export from a shared chunk is `undefined` when read during class-field initialisation from a spec with an async test · Issue #33728 · angular/angular-cli

X Title: `@angular/build:unit-test`: with the default jsdom runner and zone.js, an export from a shared chunk is `undefined` when read during class-field initialisation from a spec with an async test · Issue #33728 · angular/angular-cli

Description: Command test Is this a regression? Not known to be — this is the @angular/build:unit-test builder's default (jsdom) runner; I have no earlier version where this worked. Description Under the unit-test builder's default jsdom runner, a mo...

Open Graph Description: Command test Is this a regression? Not known to be — this is the @angular/build:unit-test builder's default (jsdom) runner; I have no earlier version where this worked. Description Under the unit-t...

X Description: Command test Is this a regression? Not known to be — this is the @angular/build:unit-test builder's default (jsdom) runner; I have no earlier version where this worked. Description Under the un...

Opengraph URL: https://github.com/angular/angular-cli/issues/33728

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`@angular/build:unit-test`: with the default jsdom runner and zone.js, an export from a shared chunk is `undefined` when read during class-field initialisation from a spec with an async test","articleBody":"### Command\n\ntest\n\n### Is this a regression?\n\nNot known to be — this is the `@angular/build:unit-test` builder's default (jsdom) runner; I have no earlier version where this worked.\n\n### Description\n\nUnder the `unit-test` builder's default jsdom runner, a module that esbuild places in a chunk shared between spec entry points is wrapped in a lazy `__esm` initialiser, and a consumer in a *different* chunk reads its exports as `undefined` during class-field initialisation. The same specs pass when the runner is switched to browser mode with the same bundles, so this looks like the Node-side module evaluation path rather than a bundling fault.\n\nThe distinction that makes it precise:\n\n- a service reads the shared `const` **inside a method** → always correct;\n- a component reads the same `const` in a **class-field initialiser** → `undefined`.\n\nThe binding is live — replacing the fields with getters (reading the same import *later*) makes the failing test pass with no other change. So the value arrives; at construction time it is not yet visible to the importer, even though the emitted code calls `init_env_config()` earlier in the same module body and construction happens later still.\n\n**Trigger conditions** — each toggled on its own with everything else constant; all four are required:\n\n| # | Required condition | Evidence |\n|---|---|---|\n| 1 | ≥ 2 spec entries import the module (shared chunk, lazy `__esm` wrappers) | a single spec file inlines everything and passes |\n| 2 | a consumer in another chunk reads the export during class-field initialisation | getters pass |\n| 3 | the consuming spec file contains an **async test callback** | making that one test synchronous passes; `async` with **no** `await` still fails |\n| 4 | **zone.js** is in the unit-test polyfills | deleting `\"polyfills\": [\"zone.js\"]` from the unit-test build configuration makes the same suite pass; restoring it fails again |\n\nNot required (removed with the failure surviving): `TestBed.configureTestingModule()` / `compileComponents()` (a bare `TestBed.createComponent()` inside an async test fails), provider overrides, barrel files, `@angular/core` patch level (fails on 21.2.18 and 21.2.19).\n\nConditions 3 and 4 are one mechanism: with zone.js present the builder downlevels `async`/`await`, so a spec containing any async function imports the `__async` helper — and esbuild then emits that spec entry **CommonJS-wrapped**, with its entry-local ESM dependencies (the component module) as lazy `__esm` initialisers:\n\n```js\n// spec-…-lead-generator.container.js (dumped with ng test --dump-virtual-files)\nimport { DEALERS, LeadService, init_env_config, init_lead_service } from \"./chunk-N64URYIK.js\";\nimport { __async, __commonJS, __esm } from \"./chunk-EFV3TZQO.js\";\n\nvar LeadGeneratorContainer;\nvar init_lead_generator_container = __esm({\n  \"…/lead-generator.container.ts\"() {\n    init_services();\n    init_env_config();                       // runs before the class statement below\n    LeadGeneratorContainer = class _LeadGeneratorContainer {\n      leadService = inject(LeadService);\n      dealers = DEALERS;                     // undefined at construction time\n      dealerOptions = this.dealers.map(…);   // throws\n    };\n  }\n});\n\nvar require_lead_generator_container_spec = __commonJS({\n  \"…/lead-generator.container.spec.ts\"(exports) {\n    init_lead_generator_container();\n    describe(\"LeadGeneratorContainer\", () => { … });\n  }\n});\nexport default require_lead_generator_container_spec();\n```\n\nThe shared chunk assigns `DEALERS` inside `init_env_config()`'s `__esm` wrapper and exports the binding; the emitted code is valid ESM and runs correctly in browser mode.\n\nOne caveat for anyone building a paraphrased fixture: the failure is sensitive to inert content — adding a top-level `console.log` to either the shared or the importing module defuses it, and one hand-written structural clone of the same shape passes. The linked reproduction is the exact shape that fails deterministically.\n\n### Minimal Reproduction\n\n**https://github.com/jonmarozick/ng-shared-chunk-repro**\n\n```\nnpm install\nnpm test        # ng test --no-watch\n```\n\nExpected: 2 passed. Actual: `Test Files 1 failed | 1 passed (2)` — `lead-generator.container.spec.ts` fails, `lead.service.spec.ts` (the control reading the same const in a method) passes.\n\nNine source files, dependencies are only Angular 21.2.19 + Vitest 4 + jsdom, `package-lock.json` committed. The module graph:\n\n```\nsrc/environments/env-config.ts        exports `const DEALERS`\n  ├── lead.service.ts                 reads DEALERS in a method\n  │     ├── lead.service.spec.ts      ← spec entry 1 (passes)\n  │     └── lead-generator.container.ts\n  └── lead-generator.container.ts     reads DEALERS in a field initialiser\n        └── lead-generator.container.spec.ts   ← spec entry 2 (fails)\n```\n\nAlso reproduced by copying these source files unchanged into a fresh `ng new` workspace on CLI 21.2.19 (`@angular/core` 21.2.19) with `\"polyfills\": [\"zone.js\"]` added to the unit-test build configuration — so nothing about it depends on the original project. The emitted bundles can be inspected via `ng test --dump-virtual-files` (they land in `.angular/cache/\u003cversion>/\u003cproject>/unit-test/output-files/`).\n\n### Exception or Error\n\n```text\nTypeError: Cannot read properties of undefined (reading 'map')\n ❯ _LeadGeneratorContainer.\u003cinstance_members_initializer> src/app/features/lead-generator/lead-generator.container.ts:291:43\n ❯ new _LeadGeneratorContainer src/app/features/lead-generator/lead-generator.container.ts:336:5\n ❯ NodeInjectorFactory.LeadGeneratorContainer_Factory [as factory] spec-app-features-lead-generator-lead-generator.container.js:1138:16\n ❯ getNodeInjectable packages/core/src/render3/di.ts:785:37\n ❯ instantiateAllDirectives packages/core/src/render3/instructions/shared.ts:122:2\n ❯ createComponentRef packages/core/src/render3/component_ref.ts:301:20\n ❯ create packages/core/testing/src/test_bed.ts:695:44\n```\n\n### Your Environment\n\n```text\nAngular CLI: 21.2.19\nNode: 24.18.0\nPackage Manager: npm 11.16.0\nOS: win32 x64\n\n@angular/build         21.2.19\n@angular/cli           21.2.19\n@angular/core          21.2.18\n@angular/compiler-cli  21.2.18\ntypescript             5.9.3\nvitest                 4.1.10\nzone.js                0.16.2\njsdom                  (builder default)\n```\n\nAlso reproduced on Linux CI (ubuntu-latest, Node 24) and in a fresh `ng new` workspace with `@angular/core` 21.2.19.\n\n### Anything else relevant?\n\n- Not avoidable through runner configuration: `isolate` true/false, `pool` forks/threads/vmThreads, `fileParallelism: false`, and dropping `runnerConfig` entirely all still fail. Removing zone.js avoids it but is not available to a zone-based app, and \"don't write async tests\" is not a workaround.\n- The impact can be silent: in a sibling project on the same setup, jsdom reported 108 of 216 tests (three spec files never loaded) in half the wall-clock of browser mode — a faster jsdom run can mean less of the suite ran.\n- Not tested on 22.x (project fleet is pinned to v21 LTS); the two vitest-related 22.x changelog entries don't touch the module-interop path.\n- Possibly related open issues, none the same: #32252, #33047, #33570.\n- I have a verified fix (disabling code splitting for the unit-test build only, mirroring the polyfills-bundle precedent) and will open a PR referencing this issue.\n","author":{"url":"https://github.com/jonmarozick","@type":"Person","name":"jonmarozick"},"datePublished":"2026-08-02T19:07:23Z","url":"https://github.com/angular/angular-cli/issues/33728"}

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:925fe19b-80b2-f21c-f258-b5ca8736a6b3
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idAB16:16EED3:3479C6E:42E49A6:6B01E435
html-safe-nonce29fb0f3cc7c526a469be6a846a94a54e1dd79d1870b3f8f48a46451677d605d1
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBQjE2OjE2RUVEMzozNDc5QzZFOjQyRTQ5QTY6NkIwMUU0MzUiLCJ2aXNpdG9yX2lkIjoiNzMwNTA3Njc4NzY4NjUzMjE0OSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9
visitor-hmac812677d976baeba4dcbe9e50e05c69b4d259a07792ee73d5c5e950c99fa22689
hovercard-subject-tagissue:5044032510
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-cli/33728/issue_layout
twitter:imagehttps://opengraph.githubassets.com/d3270ff76c82e14e8b7fc26587c6833e4644faf3af4c9b888eb5357148ff0aa9/angular/angular-cli/issues/33728
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/d3270ff76c82e14e8b7fc26587c6833e4644faf3af4c9b888eb5357148ff0aa9/angular/angular-cli/issues/33728
og:image:altCommand test Is this a regression? Not known to be — this is the @angular/build:unit-test builder's default (jsdom) runner; I have no earlier version where this worked. Description Under the unit-t...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernamejonmarozick
hostnamegithub.com
expected-hostnamegithub.com
Nonecc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c
turbo-cache-controlno-preview
go-importgithub.com/angular/angular-cli git https://github.com/angular/angular-cli.git
octolytics-dimension-user_id139426
octolytics-dimension-user_loginangular
octolytics-dimension-repository_id36891867
octolytics-dimension-repository_nwoangular/angular-cli
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id36891867
octolytics-dimension-repository_network_root_nwoangular/angular-cli
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
release8c77c9e8439031ad54c75a250694842892f693e1
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/angular/angular-cli/issues/33728#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fangular%2Fangular-cli%2Fissues%2F33728
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-cli%2Fissues%2F33728
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-cli
Reloadhttps://github.com/angular/angular-cli/issues/33728
Reloadhttps://github.com/angular/angular-cli/issues/33728
Reloadhttps://github.com/angular/angular-cli/issues/33728
angularhttps://github.com/angular
angular-clihttps://github.com/angular/angular-cli
Codehttps://github.com/angular/angular-cli
Issues198 (198)https://github.com/angular/angular-cli/issues
Pull requests23 (23)https://github.com/angular/angular-cli/pulls
Actionshttps://github.com/angular/angular-cli/actions
Security and quality8 (8)https://github.com/angular/angular-cli/security
Insightshttps://github.com/angular/angular-cli/insights
https://github.com/angular/angular-cli
New issuehttps://github.com/login?return_to=https://github.com/angular/angular-cli/issues/33728
New issuehttps://github.com/login?return_to=https://github.com/angular/angular-cli/issues/33728
#33729https://github.com/angular/angular-cli/pull/33729
@angular/build:unit-test: with the default jsdom runner and zone.js, an export from a shared chunk is undefined when read during class-field initialisation from a spec with an async testhttps://github.com/angular/angular-cli/issues/33728#top
#33729https://github.com/angular/angular-cli/pull/33729
area: @angular/buildhttps://github.com/angular/angular-cli/issues?q=state%3Aopen%20label%3A%22area%3A%20%40angular%2Fbuild%22
gemini-triagedLabel noting that an issue has been triaged by geminihttps://github.com/angular/angular-cli/issues?q=state%3Aopen%20label%3A%22gemini-triaged%22
needsTriagehttps://github.com/angular/angular-cli/milestone/11
https://github.com/jonmarozick
jonmarozickhttps://github.com/jonmarozick
on Aug 2, 2026https://github.com/angular/angular-cli/issues/33728#issue-5044032510
https://github.com/jonmarozick/ng-shared-chunk-reprohttps://github.com/jonmarozick/ng-shared-chunk-repro
"No test suite found in file" error when running Vitest #32252https://github.com/angular/angular-cli/issues/32252
@angular/build:unit-test virtual init-testbed.js guards initTestEnvironment() behind a once-per-worker symbol → stale DomAdapter under vitest ≥4.0.5 + isolate: false #33047https://github.com/angular/angular-cli/issues/33047
unit-test (vitest): isolate:false default silently breaks cross-file vi.mock() of shared modules on low-CPU workers #33570https://github.com/angular/angular-cli/issues/33570
angular-robothttps://github.com/apps/angular-robot
area: @angular/buildhttps://github.com/angular/angular-cli/issues?q=state%3Aopen%20label%3A%22area%3A%20%40angular%2Fbuild%22
gemini-triagedLabel noting that an issue has been triaged by geminihttps://github.com/angular/angular-cli/issues?q=state%3Aopen%20label%3A%22gemini-triaged%22
on Aug 2, 2026https://github.com/angular/angular-cli/issues/33728#event-28855990290
angular-robothttps://github.com/apps/angular-robot
needsTriagehttps://github.com/angular/angular-cli/milestone/11
on Aug 2, 2026https://github.com/angular/angular-cli/issues/33728#event-28855990787
jonmarozickhttps://github.com/jonmarozick
on Aug 2, 2026https://github.com/angular/angular-cli/issues/33728#event-28856105307
Minimise the failing spec, and document the exact trigger sethttps://github.com/jonmarozick/ng-shared-chunk-repro/commit/1b0b28fa3b634c88f031ae84ae93ecb1a23c491d
1b0b28fhttps://github.com/jonmarozick/ng-shared-chunk-repro/commit/1b0b28fa3b634c88f031ae84ae93ecb1a23c491d
dgp1130https://github.com/dgp1130
completedhttps://github.com/angular/angular-cli/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Acompleted
#33729https://github.com/angular/angular-cli/pull/33729
on Aug 13, 2026https://github.com/angular/angular-cli/issues/33728#event-29415497231
alan-agius4https://github.com/alan-agius4
on Aug 27, 2026https://github.com/angular/angular-cli/issues/33728#event-30101525615
fix(@angular/build): re-enable code splitting for unit testshttps://github.com/alan-agius4/angular-cli/commit/8bce16a087cf803cebdfb382a868b2a561ac7a7d
8bce16ahttps://github.com/alan-agius4/angular-cli/commit/8bce16a087cf803cebdfb382a868b2a561ac7a7d
fix(@angular/build): re-enable code splitting for unit testshttps://github.com/alan-agius4/angular-cli/commit/cfaa501f20a3d37b16b59aa2fc99abe1146f529f
cfaa501https://github.com/alan-agius4/angular-cli/commit/cfaa501f20a3d37b16b59aa2fc99abe1146f529f
fix(@angular/build): re-enable code splitting for unit testshttps://github.com/alan-agius4/angular-cli/commit/2c03d17d2208e51d798ef49351b8830dfdca0555
2c03d17https://github.com/alan-agius4/angular-cli/commit/2c03d17d2208e51d798ef49351b8830dfdca0555
fix(@angular/build): re-enable code splitting for unit testshttps://github.com/alan-agius4/angular-cli/commit/f0f034f60d5f2e9cbc3a4b6f35dad12ab9ee6d2c
f0f034fhttps://github.com/alan-agius4/angular-cli/commit/f0f034f60d5f2e9cbc3a4b6f35dad12ab9ee6d2c
fix(@angular/build): re-enable code splitting for unit testshttps://github.com/alan-agius4/angular-cli/commit/3dd7aa11b0353e9a5ba221048f8da883b5ddb96d
3dd7aa1https://github.com/alan-agius4/angular-cli/commit/3dd7aa11b0353e9a5ba221048f8da883b5ddb96d
fix(@angular/build): re-enable code splitting for unit testshttps://github.com/alan-agius4/angular-cli/commit/c3cefba5021b1e5c649b6bcad1535d9272cd7d16
c3cefbahttps://github.com/alan-agius4/angular-cli/commit/c3cefba5021b1e5c649b6bcad1535d9272cd7d16
fix(@angular/build): re-enable code splitting for unit testshttps://github.com/alan-agius4/angular-cli/commit/78d8f1cfb73dfcad3679d3d5878792095213378a
78d8f1chttps://github.com/alan-agius4/angular-cli/commit/78d8f1cfb73dfcad3679d3d5878792095213378a
fix(@angular/build): re-enable code splitting for unit testshttps://github.com/alan-agius4/angular-cli/commit/ba0a2f01b69be88e3692cae8aaddff4a93c33715
ba0a2f0https://github.com/alan-agius4/angular-cli/commit/ba0a2f01b69be88e3692cae8aaddff4a93c33715
fix(@angular/build): re-enable code splitting for unit testshttps://github.com/alan-agius4/angular-cli/commit/18757a944860459012b88dac22fac9fbc5d2130b
18757a9https://github.com/alan-agius4/angular-cli/commit/18757a944860459012b88dac22fac9fbc5d2130b
reiklahttps://github.com/reikla
on Sep 2, 2026https://github.com/angular/angular-cli/issues/33728#event-30429550596
AB#5075 Chore: libraries hygiene — class-field getters, editorconfig …https://github.com/meshmakers/octo-frontend-libraries/commit/80e7fded4382fb299135b16e6d8d97833defa929
80e7fdehttps://github.com/meshmakers/octo-frontend-libraries/commit/80e7fded4382fb299135b16e6d8d97833defa929
https://github.com/apps/angular-automatic-lock-bot
angular-automatic-lock-bothttps://github.com/apps/angular-automatic-lock-bot
on Oct 19, 2026https://github.com/angular/angular-cli/issues/33728#issuecomment-6257038289
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 19, 2026https://github.com/angular/angular-cli/issues/33728#event-33599936776
Sign up for freehttps://github.com/signup?return_to=https://github.com/angular/angular-cli/issues/33728
Sign in to commenthttps://github.com/login?return_to=https://github.com/angular/angular-cli/issues/33728
area: @angular/buildhttps://github.com/angular/angular-cli/issues?q=state%3Aopen%20label%3A%22area%3A%20%40angular%2Fbuild%22
gemini-triagedLabel noting that an issue has been triaged by geminihttps://github.com/angular/angular-cli/issues?q=state%3Aopen%20label%3A%22gemini-triaged%22
needsTriageNo due datehttps://github.com/angular/angular-cli/milestone/11
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.