Types and coercion
Primitives, objects, == versus ===, and JSON-safe values.
JavaScript fundamentals means the language as it runs in engines today: types, scope, functions, this, prototypes, modules, asynchronous code, and the DOM if you are targeting the browser. It is not a framework course and not a CompTIA exam.
You need a working model of coercion, equality, lexical scope, closures, prototypes versus class syntax, and how promises and async/await schedule work. ES modules, iterators, and common array methods belong here. React or Node APIs belong in a later deck.
Assessments — a class exam, a hiring screen, or a certification module — usually ask what a snippet logs or how to fix a bug. Cards should store that behavior, then you prove it in a console the same day.
Primitives, objects, == versus ===, and JSON-safe values.
let/const/var, lexical scope, and a closure you can draw.
The event loop at a practical level, promises, and async/await error handling.
Prototypes, class syntax, destructuring, and ES module exports.
For someone who has written a little JavaScript. If you are brand new, add a week of syntax before closures.
Weeks 1–2
Card what a snippet logs. After each card, run a one-line experiment. Delete any card you cannot prove.
Weeks 3–4
Closures, this, prototypes, and modules. Write a tiny function that uses each idea instead of only flipping cards.
Weeks 5–6
Promises, async/await, and a simple DOM or fetch example if you need the browser. Mixed snippet drills.
A JavaScript card that you never run becomes folklore. The front should be a short snippet or a behavior question. The back should be the result and the one-sentence why. Then run it.
Spaced repetition is useful because coercion, this, and promise order feel familiar until they are not. Keep the deck small enough that you still write code most days.
Predict the output, flip, then paste the snippet into a console.
Change let to var, or == to ===, and card the new result.
Ask what an unhandled rejection or a missing await does.
180 behavior cards at 20 minutes a day for six weeks. Console time is extra and required.
Estimate: 30 seconds per new card, 10 seconds per review. Fixed review gaps, not FSRS or a recall prediction.
Your calculator inputs stay in this browser tab. No uploads, email or signup needed.
No. It is the language. Add a framework deck later so reviews stay specific.
Card the methods you still confuse (map/filter/reduce, slice/splice). The rest come back when you write code.
Security+ tests cybersecurity operations. JavaScript fundamentals tests language behavior. They share almost no cards.
Yes. Edit generated cards into snippets you can run. Delete slides that only say “JavaScript is versatile.”
Open the web app to turn your sources into editable flashcards and quizzes. There is no permanent free tier; current prices live in the app. iOS and Android app updates are coming soon.