Quick answer
Astro builds the pages. React runs interactive interfaces. TypeScript checks code types. Playwright and Vitest test selected browser flows and logic. Tesseract.js and Transformers.js power specific OCR and AI tools. The Ask route can call Ollama's hosted API when its parser cannot identify a supported request.
These are different jobs. A passing type check does not prove a formula is correct, and a successful browser test does not prove that every visitor can use a page. The stack gives the project repeatable checks, with limits that still need human judgment.
What is actually used, and where
The dependency lockfile reviewed on October 5, 2026 contains Astro 7.2.8, React 19.2.8, TypeScript 7.0.2 and 6.0.2, Playwright 1.62.0, Vitest 4.1.11, Tesseract.js 7.0.0, and Transformers.js 4.2.0. Ollama is a separate hosted API connection, not a model bundled into the website. These version numbers describe this project snapshot, not the latest release of every upstream project.
| Job | Projects | What they do here |
|---|---|---|
| Build and interface | Astro, React, TypeScript | Render pages, run interactive tools, and check code types. |
| Quality checks | Playwright, Vitest | Check selected layouts, accessibility rules, interactions, and calculation logic. |
| AI and OCR | Tesseract.js, Transformers.js, Ollama | Recognize images and run browser models; optionally send Ask questions through a cloud router. |
Astro 7 builds content and server routes
Sources: Astro 7and the Node adapter
Access Free Tools has hundreds of calculator, converter, guide, category, gallery, sitemap, and API routes. Astro renders the content as HTML and supports server routes for functions such as Ask. This project uses the Node adapter in standalone mode and requires Node 24. The October 5 published build marker also reported Node 24.
The title, explanation, links, and examples exist in rendered HTML. A crawler does not need to press a button to read those parts. Sitemap and canonical rules still need separate checks. Rendering HTML does not promise search visibility or approval by an advertising network.
React 19 runs the parts people touch
Source: React documentation
The page around a calculator can stay plain HTML, while React handles the inputs, modes, results, undo buttons, and live status inside the tool. Someone can read the formula and example before JavaScript finishes loading, then use the interactive part when it is ready.
The project checks JavaScript budgets and loads larger OCR and model assets only for the matching tool action. That keeps the work associated with the feature that needs it. A mortgage calculation does not need a speech model to produce its answer.
TypeScript 7 checks types; examples check the math
Source: Microsoft's TypeScript 7 announcement
A calculator result can look believable even when one field is wired to the wrong unit. TypeScript can catch mismatched types and missing cases before code reaches the browser. The project uses TypeScript 7's native command-line checker and keeps the TypeScript 6 compatibility package. Microsoft documents this dual-package setup; the project's scripts offer both tsc and tsc6 checks.
Types cannot prove an interest formula uses the right assumption. Result tests must also check known inputs and outputs. For example, 15% of 80 must give 12 whether the request comes from the percentage calculator or its deterministic API runner.
Playwright checks browser flows; Vitest checks logic
Sources: Playwrightand Vitest
Vitest checks small units of logic, such as a legal Four in a Row move, a routing decision, or an indexation rule. Playwright opens pages and exercises interactions. It can detect layout problems that a calculation test would never see.
Layout checks at different widths can catch overlaps, clipped tables, and horizontal overflow. They cover the browser and states tested, rather than every phone or assistive technology. Playwright's accessibility guidancerecommends manual assessment and inclusive user testing alongside automated checks. An axe scan cannot replace those steps.
Tesseract.js and Transformers.js serve specific tools
Sources: Tesseract.jsand Transformers.js
The Image to Text OCR Tool starts a self-hosted Tesseract.js worker, core, and selected language data when someone presses Read text. Transformers.js is imported when a matching browser model is requested. Downloading a model is separate from uploading a user's input for inference.
Tesseract's image-quality guideexplains why resolution, contrast, skew, and borders affect recognition. Check names, totals, dates, and anything important against the original. The browser AI privacy guideexplains the separate model-download, input-processing, and analytics routes.
Ollama provides optional cloud routing, not calculator math
Sources: Ollama on GitHuband its API routes
Ask Access Free Tools sends a visitor's question to the site's server. Its parser tries to identify a supported tool first. If that fails and cloud routing is configured, the server can send the question to https://ollama.com/api/chat. This is cloud AI, not a model running on the visitor's computer.
Ollama's job is to select a tool and its inputs. The final arithmetic and answer come from the deterministic runner. A recognized parser question does not need the Ollama call; an unrecognized question may fail if that service is unavailable. Using an open-source project through a hosted service does not make the service local or automatically free.
Other projects are not production dependencies
Sources: Ladybird,Lightpanda, andOpen WebUI
Ladybird is building an independent browser engine. Lightpanda targets headless automation. Open WebUI provides a self-hosted interface for local and cloud model workflows. They offer useful comparisons, but none appears as a production dependency in this site's reviewed package files. Their presence in a roundup does not show that they power this website.
Continue's official sitesays it was acquired by Cursor, as checked on October 5, 2026. Ownership, maintenance, licensing, and hosting can change. Before adding any project, check its current source and the exact job it would do. The GitHub project checklistcovers that next step.
Sources
These primary project pages and official documentation support the technical explanations in this article.
- Astro 7 release
- Astro Node adapter
- React documentation
- Microsoft: Announcing TypeScript 7.0
- Playwright documentation
- Playwright: accessibility testing limits
- Vitest documentation
- Tesseract.js on GitHub
- Tesseract: image quality limits
- Transformers.js documentation
- Ollama on GitHub
- Ollama local and cloud API routes
- Ladybird browser project
- Lightpanda browser project
- Open WebUI on GitHub
- Continue project status
Access Free Tools is owned by Brendan Chambers. This article was revised with AI-assisted research and editing. Technical explanations were checked against linked primary sources and the current project code where applicable.
