midudev/jscamp: the JSCamp InfoJobs bootcamp repository, module by module

What midudev/jscamp actually is, and who it is built for

JSCamp InfoJobs is an intensive JavaScript and full-stack web development bootcamp taught in Spanish by midudev. The repository is the code half of that bootcamp: folders of exercises and project steps that follow the video modules. The README describes the goal as taking a learner from fundamentals to the more advanced parts of the JavaScript ecosystem, naming HTML, CSS, JavaScript, TypeScript, Node.js, SQL, CI/CD and Docker.

The audience is narrow and specific. You need to be comfortable reading Spanish, because the README, the module listing and the stated objectives are all written in it. You also need to accept that the repository is not the course. The README points to jscamp.dev for the videos and content, says registration there is free, and notes that videos and materials are uploaded gradually as the bootcamp progresses. So the repository is a set of working files that assumes you are watching along, not a self-contained textbook.

One detail worth reading carefully: the README describes an optional paid certificate tier that bundles a digital certificate, exercise review, an exclusive Discord channel, exclusive live sessions, CV review and guaranteed entry to in-person workshops in Barcelona and Madrid. That tier is separate from the repository. Cloning the repo does not grant any of it.

The module layout: ten numbered folders from HTML to Docker

The top-level directory listing is the clearest map of the curriculum. Folders are numbered, and the numbering is the intended order: 00-html-css, 01-javascript, 02-react-cdn-version, 02-react, 03-router-and-zustand, 04-express, 04-node, 05-testing, 06-typescript, 07-inteligencia-artificial, 08-sql, 09-ci-cd and 10-docker.

Two things stand out. First, there are duplicate numbers with different content: 02-react-cdn-version and 02-react, then 04-express and 04-node. That is a deliberate split rather than a mistake, and it tells you the React module is taught twice, once through a CDN approach and once as a normal project, while the Node module separates raw Node from Express. Second, the folder list is longer than the README's module list. The README lists ten items ending at Docker; the repository also carries 05-testing and 07-inteligencia-artificial, which the README folds into other headings or omits. If you plan by the README alone, you will miss the testing folder.

The practical consequence is that you should browse the directory tree before trusting either list. The README is a summary written for a landing page; the folders are what you actually get.

Installing nothing: cloning the repo and starting the first module

There is no package to install and no CLI to set up. The README's start section is a clone and a cd, and that is the whole onboarding. The command below is copied from the README, including the SSH remote, so you need a GitHub SSH key configured; if you do not have one, substitute the HTTPS URL yourself.

git clone [email protected]:midudev/jscamp.git

cd jscamp/00-html-css

After the cd you land in the HTML and CSS module. The README says each module contains practical exercises and real projects and that you should navigate to the relevant folder and follow the instructions inside it. It does not describe a build step, a dev server or a test command for that folder, so what you see next depends entirely on the files in it.

The README also lists prerequisites before you start: a current Chrome, Firefox, Edge or Safari, Visual Studio Code as the recommended editor, the Live Preview extension for viewing HTML and CSS, Node.js version 20 or higher, Git, Docker for the Docker module, and Warp as the recommended terminal. Only Node.js 20+ and Docker are hard requirements for specific modules; the rest are tooling preferences stated as requirements.

The CI badge, and what the repository does not tell you

The README opens with a GitHub Actions badge for a workflow file at .github/workflows/05-ci.yml. That is the only automated check visible from the outside, and its name ties it to the CI/CD module rather than to the whole repository. Nothing in the README states that exercises are validated on push, that a test suite runs across modules, or that a failing workflow blocks anything. Treat the badge as evidence that a pipeline exists for one module, not as a quality signal for the curriculum.

The bigger gap is licensing. The repository metadata carries no licence identifier, and the README does not name one. For a project whose README explicitly offers a paid certificate tier and in-person workshops, the absence of a stated licence matters: you cannot tell whether reuse of the exercise code in your own teaching or product is permitted. That is a question for the repository owner, not something to infer.

Releases are also absent. No releases are listed, so there is no versioned artefact to pin to. Your reference point is a commit on main.

Where the repository stops: no grading, no English, no package

The clearest limitation is that the repository cannot teach you on its own. The README directs learners to jscamp.dev for videos and content and says materials are uploaded gradually. If a module folder is thin, the explanation lives in a video you have to watch, and the README does not document a fallback for that.

Language is the second boundary. Everything in the repository is Spanish. If you cannot follow Spanish instruction, the folders will give you code to read but not the reasoning behind it, and there is no stated English track.

Third, the feedback loop is paid. The README describes exercise tracking, correction and review as part of the optional paid certificate. Without it, you write code and get no external check. There is no test harness described in the README that would grade your work automatically.

Fourth, this is the wrong tool if you want a dependency you can install. It is not published as a library or a scaffold; it is a set of folders. If you want a starter template for a React or Express app, this repository gives you a reference implementation to read rather than something to run as a generator.

How it compares with freeCodeCamp's curriculum

freeCodeCamp is the obvious alternative, and the difference is structural rather than a matter of quality. freeCodeCamp runs inside the browser: you read a prompt, write code in an embedded editor, and an automated test suite tells you whether you passed. Progress is tracked by the platform. The repository model here is the opposite. You clone files, run them locally in your own editor, and nothing tells you whether your answer is right unless you pay for review or find someone to check it.

That trade-off cuts both ways. The browser model gives immediate feedback and a defined path, but it keeps you inside someone else's editor and test harness. The JSCamp model puts you in VS Code with Git and Docker installed, which is closer to how you would actually work, and the curriculum reaches into CI/CD and containerisation in a way that a browser sandbox struggles to replicate. What you give up is the automatic check.

A second difference is language and authorship. freeCodeCamp's core curriculum is English-first with a large translation effort. JSCamp is Spanish-first, taught by one instructor, midudev, whose teaching style is the reason many learners are there in the first place. If you are choosing between them, the deciding question is whether you want a graded path or a working environment.

Maintenance, upgrade cost and licence questions

The last push to the repository was on 2026-07-02. That is recent enough that the repository is not abandoned, but the README's own wording, that videos and materials are uploaded gradually as the bootcamp advances, means the contents move with the cohort rather than on a fixed release schedule. There are no releases to upgrade between, so there is no migration cost in the usual sense. The cost is re-reading folders after a pull, since module contents can change under you.

Upgrade cost is therefore low and mostly manual: git pull, then re-read the module you are on. Nothing in the README describes a lockfile, a versioned dependency set or a compatibility matrix, so if a module pins a Node version, that information lives in the module folder rather than the README.

On licensing, no licence identifier is given for the repository, and the README does not state terms for reusing the exercise code. If you intend to reuse any of it in your own course, product or internal training, ask the author directly rather than assuming permission. This is a factual gap, not a legal conclusion.

Editorial conclusion

Adopt midudev/jscamp if you already follow midudev's Spanish-language teaching and want the exercise folders that pair with the jscamp.dev videos; the repository is a companion, not a standalone course. Skip it if you need English narration, graded feedback, or an installable package, since none of those are in the repo. Before committing time, open the module folder you care about and confirm it contains instructions you can follow without the paid tier, and check the licence file, which the repository does not appear to ship.

Frequently asked questions

Official sources

1. Issues
2. midudev/jscamp on GitHub
3. Project website
4. README