xabierlameiro.com valid

Xabier Lameiro

Personal site and technical blog of Xabier Lameiro, a software architect from Galicia (Spain)

For agents: Personal technical blog and portfolio of software architect Xabier Lameiro; Next.js CLI tools (next-leak, next-coverage) and npm/yarn error fix articles.

nextjsmemory-leaksnpm-errorssoftware-architecttechnical-blog

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T12:56:41.508Z. Cached copy · Source on xabierlameiro.com

# Xabier Lameiro

> Personal site and technical blog of Xabier Lameiro, a software architect from Galicia (Spain)
> specialised in web development with React, Next.js and TypeScript. Posts are practical,
> first-hand guides about errors, testing, CI/CD and web tooling, available in English,
> Spanish (/es) and Galician (/gl). English URLs below are canonical.

## Pages

- [Home](https://xabierlameiro.com): Who Xabier Lameiro is — bio, experience, stack and contact details
- [next-leak](https://xabierlameiro.com/next-leak): CLI that measures Next.js memory leaks per route — verdict, retainer chain and the real Next.js issues it was verified against
- [next-coverage](https://xabierlameiro.com/next-coverage): CLI that reads a Next.js App Router project and sorts the framework's APIs into used, would apply, not applicable and not evaluated

## Blog: Error

- [Fix "Failed to replace env in config: ${NPM_TOKEN}" in npm and yarn](https://xabierlameiro.com/blog/error/npm-token-solution-error): How to fix the npm/yarn error "Failed to replace env in config: ${NPM_TOKEN}" in one minute: define the missing environment variable that your .npmrc expects, or remove the stale entry.
- [Address already in use fix: free the port (EADDRINUSE)](https://xabierlameiro.com/blog/error/solve-address-in-use-error): Address already in use fix for Node.js, Python, Docker, netcat and Playwright: find and kill the process holding the port on macOS, Linux and Windows.
- [How to fix Minified React error #425 (hydration mismatch)](https://xabierlameiro.com/blog/error/uncaught-error-minified-react-error): Fix Minified React error #425 ("Text content does not match server-rendered HTML"): every common cause of a hydration mismatch — dates, random values, locale formatting, browser-only APIs, invalid HTML — and the right fix for each, with Next.js examples.

## Blog: Javascript

- [Lighthouse report automation](https://xabierlameiro.com/blog/javascript/lighthouse-reporting-automation): Automation of Lighthouse reporting using playwright and the lightouse api on a deployed website in a real example

## Blog: Nextjs

- [Continuous Integration with Github Actions workflow](https://xabierlameiro.com/blog/nextjs/continuous-integration-with-github-actions-workflow): Set up CI/CD for a Next.js project with GitHub Actions: lint, test and build on every push, then deploy to Vercel. The workflow YAML explained step by step.
- [Get a GitHub repo's star count without hitting rate limits](https://xabierlameiro.com/blog/nextjs/counter-for-github-stars-repository): Read a GitHub repository's star count from stargazers_count, understand the 60 vs 5,000 requests-per-hour limits, and cache the call so a live counter costs one API request an hour.
- [Dark mode in Next.js without the flash of the wrong theme](https://xabierlameiro.com/blog/nextjs/dark-theme): Dark mode in Next.js with CSS variables: resolve the theme before the first paint, persist the choice, and set color-scheme so scrollbars and f
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=xabierlameiro.com · GET /v1/domain/xabierlameiro.com · 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.

Claim my listing on Agent Web Map for xabierlameiro.com:
1. POST https://agentwebmap.com/v1/sites/xabierlameiro.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://xabierlameiro.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/xabierlameiro.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/xabierlameiro.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.