Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Adds a new `browser` ecosystem identifier for projects that use headless Chrome, Puppeteer, or Playwright for integration testing. The ecosystem includes the Google and Chrome-specific domains that are requested by the Chrome browser during initialization and testing. Domains added: - *.google.com (accounts, OAuth, Google services) - *.googleapis.com (Google APIs used by Chrome) - *.gvt1.com (Chrome redirect/update service) - fresh.deno.dev (Deno Fresh framework) The `browser` entry is placed after `java` in the ecosystem priority list to ensure that more-specific Google domains in existing ecosystems (java: maven.google.com/dl.google.com, fonts: fonts.googleapis.com, defaults: packages.cloud.google.com) continue to resolve correctly. Fixes #<issue>" Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add browser/chrome ecosystem domain group for testing
Add Mar 18, 2026
browser ecosystem domain group for headless Chrome/Puppeteer/Playwright testing
Contributor
|
@copilot rename browser to chrome, add deno domains to deno set |
- Rename `browser` ecosystem to `chrome` (Google/Chrome-specific domains) - Remove `fresh.deno.dev` from `chrome` ecosystem - Add new `deno` ecosystem with Deno-specific domains: deno.land, jsr.io, *.jsr.io, googleapis.deno.dev, fresh.deno.dev - Update ecosystemPriority: add `deno` before `node` for correct resolution - Update tests and docs to reflect renamed and new ecosystems Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Contributor
Author
Copilot
AI
changed the title
Add
Add Mar 18, 2026
browser ecosystem domain group for headless Chrome/Puppeteer/Playwright testingchrome and deno ecosystem domain groups for headless Chrome/Puppeteer and Deno testing
Contributor
There was a problem hiding this comment.
Pull request overview
Adds two new network ecosystem identifiers (chrome, deno) to reduce blocked network requests during headless Chrome/Puppeteer and Deno/Fresh testing, plus updates priority resolution, tests, and docs.
Changes:
- Add
chromeanddenoecosystem domain groups to the embeddedecosystem_domains.json. - Update ecosystem resolution priority ordering to ensure existing more-specific mappings win over broad Google wildcards.
- Add/extend tests and update the network reference docs to document the new identifiers.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| pkg/workflow/domains.go | Documents new ecosystems and updates ecosystemPriority ordering for deterministic ecosystem resolution. |
| pkg/workflow/domains_test.go | Adds test cases for chrome/deno ecosystem resolution and allowlist expansion. |
| pkg/workflow/data/ecosystem_domains.json | Introduces the chrome and deno ecosystem domain lists. |
| docs/src/content/docs/reference/network.md | Documents chrome and deno in the ecosystem identifier reference table. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Removed duplicate entry for 'bazel' in ecosystem_domains.json.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Projects using headless Chrome for integration tests (e.g. deno/fresh) have 80+ requests blocked because Chrome's initialization touches Google/gvt1 domains not covered by any existing ecosystem group.
Changes
chromeecosystem inecosystem_domains.json:*.google.com,*.googleapis.com,*.gvt1.com— Google and Chrome-specific domains needed by headless Chrome/Puppeteerdenoecosystem inecosystem_domains.json:deno.land,jsr.io,*.jsr.io,googleapis.deno.dev,fresh.deno.dev— Deno runtime and Fresh framework domainsecosystemPriority:denoplaced beforenode(Deno-specific domains resolve todenorather thannode);chromeplaced afterjavaandfontsso existing more-specific Google domain entries (maven.google.com→java,fonts.googleapis.com→fonts,packages.cloud.google.com→defaults) continue to resolve correctlychromeanddenorows to ecosystem reference tableUsage
📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.