crxjs.dev valid
CRXJS Documentation
Build cross-browser extensions with native HMR, zero-config setup, and Vite 8 support.
- Authority
- 46 reach 0 · trust 10 · quality 21 · freshness 15
- Tier
- listed
- llms.txt
- https://crxjs.dev/llms.txt
- Sections
- 4
- Links
- 13
- Size
- 1708 bytes
- Registered
- 2021-11-09
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-23T18:34:54.468Z
- Last checked
- 2026-10-23T18:34:57.387Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-23T18:34:54.471Z. Cached copy · Source on crxjs.dev
# CRXJS Documentation
> Build cross-browser extensions with native HMR, zero-config setup, and Vite 8 support.
## Documentation Sets
- [CRXJS Documentation](https://crxjs.dev//llms-full.txt): Build cross-browser extensions with native HMR, zero-config setup, and Vite 8 support.
## Getting Started
Learn how to set up and use CRXJS
- [Introduction](/guide/introduction): Overview of CRXJS features and capabilities
- [Quick Start with create-crxjs](/guide/installation/create-crxjs): Create a new project using the official starter template
- [Manual Setup](/guide/installation/from-scratch): Step-by-step guide for manual installation
- [Loading Extensions](/guide/installation/loading): How to load and test your extension in Chrome
- [Building for Production](/guide/installation/packaging): Prepare your extension for distribution
## Core Concepts
Key concepts for CRXJS development
- [Manifest Configuration](/concepts/manifest): Understanding the manifest.json file structure
- [Background Scripts](/concepts/background): Working with extension background processes
- [Content Scripts](/concepts/content): Injecting scripts into web pages
- [Extension Pages](/concepts/pages): Creating popup and options pages
## Demos
Example extension fixtures and contributor playgrounds
- [Demos](/demos): Browse CRXJS demo fixtures and contributor playgrounds
- [E2E Demo Fixtures](https://github.com/crxjs/chrome-extension-tools/tree/main/packages/vite-plugin/tests/e2e): Tested extension examples for framework integrations and Manifest V3 behavior
- [Contributor Playgrounds](https://github.com/crxjs/chrome-extension-tools/tree/main/playgrounds): Runnable playground projects for CRXJS contributorsMachine-readable: GET /v1/resolve?q=crxjs.dev · GET /v1/domain/crxjs.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage crxjs.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for crxjs.dev:
1. POST https://agentwebmap.com/v1/sites/crxjs.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://crxjs.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/crxjs.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/crxjs.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.