javascript-code-challenges: modern JavaScript interview challenges, published on Vercel

The challenge index lives on Vercel, not in the repository

The top level of this repository holds seven entries: .github/, CODE_OF_CONDUCT.md, LICENSE, README.md, contributing.md, usageGuide.md and web/. The README states that all challenges can be found at https://jscodechallenges.vercel.app/, so the repository is the source and the deployed site is the reading interface.

A README built from HTML with four empty badge anchors

The README is not written in prose. It is a centered HTML div holding a link to the site, an h1 reading JavaScript Code Challenges, an h3 describing modern interview code challenges on JavaScript, and an h4 listing Interviewees, Interviewers, Knowledge test and Practice. Inside that block sit four named anchors: stars, forks, contributions and license. The repository's primary language is recorded as MDX.

One subtitle, four intended readers

Serving four roles from one problem set is the real design decision in that h4 line, and it changes what the content has to be. A practice list only needs a correct answer. A question bank for an interviewer needs a prompt that can be asked out loud and judged without running anything. A knowledge test needs a fixed difficulty.

Nothing at the root tells you how to run the site

To get the sources, clone the repository:

git clone https://github.com/sadanandpai/javascript-code-challenges
cd javascript-code-challenges

After that, the top level is exactly this:

.github/
CODE_OF_CONDUCT.md
LICENSE
README.md
contributing.md
usageGuide.md
web/

There is no package.json and no lockfile at the root, so the dependency set behind the Vercel deployment is not visible from what you just cloned. The README gives no local run command either. Its only instruction is to check the Contributing Guide if you want to contribute, improve or suggest changes, and the one online resource it names is the deployed site. The gap that leaves is concrete: working through the challenges offline, or adding one, means inferring the tooling from web/ by hand, because the Node version, the framework and the build step are all absent from the root.

usageGuide.md and contributing.md carry the whole manual

Two prose documents carry the documentation, and both are lowercase in filename while README.md, LICENSE and CODE_OF_CONDUCT.md are uppercase. contributing.md is the one the README points at for contributions, improvements and suggestions. usageGuide.md is not linked from the README at all; it sits at the top level and nothing on the front page advertises it. With the challenge list hosted on Vercel, those two files are effectively the repository's entire manual. A reader who lands on the repository front page has to find one of them by browsing the file list, and the README's only other call to action asks for a star.

No releases and no tags, so you cannot pin what you studied

There are no GitHub releases and no changelog in the top-level list. The last push was on 2026-04-01. For a collection of interview questions this costs more than it would for a library. Nobody depends on these files at build time, so nothing breaks when they change, but a candidate who memorised a solution last month has no way to tell whether a problem was rewritten, an expected answer corrected, or an edge case added. If a challenge feels wrong, the only ground truth left is the commit history, one file at a time.

MIT covers the words, and nothing says otherwise

The repository states that it is MIT licensed and ships a LICENSE file at the root. That is the whole licensing story, and it is short. What the repository does not do is break the licence down. There is no separate note saying whether the challenge prompts, the expected solutions and the MDX site source fall under the same terms. For a set of interview questions written for practice that matters more than it would for a tool, because the text is the entire product. Reading LICENSE is the only step the README asks for, and it asks for it in one line.

The beginners-to-experts range is asserted, never itemised

The repository description says the challenges suit beginners to experts, and the subtitle repeats the intent for interviewees and interviewers. The top-level entries include no difficulty index, so check the published site for how challenges are grouped. Whoever picks a question has to judge the level.

Editorial conclusion

Use javascript-code-challenges when you want a running list of modern JavaScript interview questions, either to practise or to ask candidates, and accept that the README points to jscodechallenges.vercel.app for the full list. Leave it when you need the challenges offline or need to track which version you studied, because there is no package manifest at the root, no releases and no changelog. Before you rely on any single problem, open usageGuide.md and check that file's last commit in the history.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. Project website
4. README
5. sadanandpai/javascript-code-challenges on GitHub