midudev/preguntas-entrevista-react: a Spanish React interview question bank built as an Astro site

What midudev/preguntas-entrevista-react actually is

This is a question bank, not a library. The README describes it as typical React questions for job interviews, with detailed answers in Spanish, and the index splits them into Principiante and Intermedio levels. The beginner block runs from "¿Qué es React?" through JSX, props, state, events, lists, and the hooks useState, useReducer, useEffect and useId. The intermediate block moves to custom hooks, the rules of hooks, useEffect against useLayoutEffect, hydration, Server Side Rendering, and controlled against uncontrolled components. A separate section covers the JavaScript needed before React, including ESModules, ternary operators, arrow functions, default parameters, template literals, destructuring, array methods, spread and rest syntax, and optional chaining.

The intended reader is someone preparing for a Spanish-language React interview, or a team that wants a shared question list for screening. The repository is not published as an installable package: package.json sets "private": true, so there is no npm artifact to pull into an application. The homepage is reactjs.wiki, and the README also points to a Twitch stream and a Discord community, which tells you where the project expects discussion to happen.

How the Markdown becomes the site: scripts, Astro and a conversion step

The architecture is a static site generator with a content pipeline in front of it. The repository root holds manuscript/, book/, src/, public/ and scripts/ alongside astro.config.mjs and vercel.json. Content lives as Markdown, and the build does not read it directly: the dev and build scripts both run node scripts/markdownToJson.mjs first, then hand the result to Astro.

That ordering matters more than it looks. If the conversion script fails or produces stale output, Astro will build the previous content without complaining about the Markdown you just edited. The same pattern appears in the other script names: markdown:lint runs scripts/lint.mjs, content runs the converter alone, and book runs scripts/exportBook.mjs, which is how the book/ directory is produced. Search is client-side and comes from fuse.js, with just-debounce-it smoothing input, so the whole index ships to the browser rather than living behind a query endpoint. Syntax highlighting is Prism, and the UI is React 19 components mounted through @astrojs/react on top of Astro 7, styled with Tailwind 4 through @tailwindcss/vite.

Installing it and running the site locally

There is no install step for consumers, because the package is private. To run or contribute to the site itself, package.json pins [email protected] as the package manager and Node 22.x under engines, so match both before doing anything else.

corepack enable
pnpm install
pnpm dev

The dev script chains the Markdown conversion and then starts Astro, so you do not need to run the converter by hand while editing. Astro prints a local URL in the terminal; open it and use the search box to confirm your question is indexed.

To reproduce what the deployment serves, run the build instead. This runs the same conversion first, then produces the static output that vercel.json points at.

pnpm build
pnpm preview

If you only want to check that a Markdown edit is well formed before committing, the lint script is the cheapest signal available.

pnpm markdown:lint

The book export is separate and produces the book/ directory rather than a web page.

pnpm book

The content pipeline is also the weakest link

The biggest practical limitation is that Markdown is not the source of truth the site reads. scripts/markdownToJson.mjs sits in the middle, and nothing in the README documents what happens when a question is malformed, duplicated or removed. A heading that does not match the converter's expectations can silently drop out of the generated JSON, and the site will build cleanly while the question is missing. For a repository whose whole value is the completeness of its question list, that is a real failure mode, and it is the kind of thing you only notice by opening the built site rather than by reading the diff.

There is a second boundary worth stating plainly. The README says the answers are in Spanish. If your interview loop is conducted in English, translating each answer is work you take on yourself, and the repository offers no parallel English manuscript. The same applies to the level taxonomy: only Principiante and Intermedio are listed in the index, so a candidate looking for staff-level architecture questions will not find a labelled tier for them. Finally, the project is a study resource. It does not verify that an answer matches your team's conventions, and it cannot tell you whether a candidate can apply the answer under pressure.

How it compares with GreatFrontEnd and the official React docs

The closest alternatives differ in shape rather than in topic coverage. GreatFrontEnd is a commercial interview preparation platform with practice problems and a paid tier; its questions are delivered through its own product, in English, and you cannot fork the content into your own repository. This project is the opposite: MIT licensed, plain Markdown, no accounts, no paywall, but also no grading, no spaced repetition and no progress tracking. You get the text and the site, and you bring your own study method.

The official React documentation is the other reference point, and the difference is intent. The docs explain how React works and are maintained by the React team; this repository explains how React is asked about in interviews, which is a different editorial job. The docs will be more accurate and more current on API behaviour. This repository is more useful for rehearsing the phrasing of an answer, and it carries the JavaScript prerequisites section that the docs assume you already have. If you want a Spanish-language React Native angle, the repository topics include react-native, but the index shown in the README is React-focused, so do not assume the mobile material is as deep.

Maintenance, licence and what a fork costs you

The last push was on 2026-09-17, and the repository is not archived, so the project is being touched. The dependency list is current rather than conservative: Astro 7.3.2, React 19.3.0, TypeScript 7.0.2, Tailwind 4.3.3 and oxlint 1.83.0. That is good for a site that wants modern tooling and bad for anyone who forks and then stops paying attention, because a major Astro release will eventually require changes in astro.config.mjs and the @astrojs/react integration. The lockfile is pnpm-lock.yaml with a pnpm-workspace.yaml beside it, so a fork should stay on pnpm rather than switching to npm and regenerating a second lockfile.

The licence is MIT, which is permissive: you can reuse and adapt the content with attribution and the licence text. That is a statement about the licence file, not legal advice, and it does not settle questions about the underlying React documentation or any third-party text quoted inside the answers. The upgrade cost for a reader is effectively zero, since nothing is installed. The upgrade cost for a contributor is the conversion script plus the Astro major-version cycle, and that is the number to weigh before you make a fork the home of your team's internal question bank.

Editorial conclusion

Adopt it if you are preparing for a React interview in Spanish and want the questions organised by level, from beginner through intermediate, with answers in the same repository. Do not adopt it as a runtime dependency, a component library or an English-language resource; the README states the answers are in Spanish. Before contributing, run pnpm dev locally and check that scripts/markdownToJson.mjs turns your Markdown into content, because that conversion step sits between the manuscript and the site.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. midudev/preguntas-entrevista-react on GitHub
4. Project website
5. README