JavaScript Racer in browser

Game files

No own files requested before acceleration

Controls

Keyboard controls

Account

No sign-in in checked entry

Mobile gameplay

Not tested

Full session

Not tested

HTTP link check

HTTP 200; 0 redirects (2026-10-21)

Basis: project instructions and limited desktop entry observation. Observations: Oct 21, 2026. Conditions organized: October 21, 2026.

Up acceleration raised displayed speed to 20 mph and changed road landmarks; later readings fell during coasting. No own files or sign-in preceded it. Steering, laps, tuning, saved times and mobile were not tested.

Project type: Native browser game

Jake Gordon's repository identifies an original HTML5/JavaScript pseudo-3D racing teaching demo and links the final build. It is not an official OutRun port, a Genesis emulator or four separate projects.

Classification organized October 21, 2026 from the recorded source and check notes; not a new gameplay test.

This JavaScript Racer browser guide covers the final demonstration linked by Jake Gordon's original repository. It is a pseudo-3D racing teaching project, not an official OutRun release or an emulator running a separate commercial game. The page rendered a red car, traffic, roadside scenery and a speed display, with instructions to use arrow keys. Holding Up briefly increased the displayed speed and changed the road landmarks. This provides an actual acceleration observation rather than treating a source screenshot or a canvas fallback message as proof that the game ran.

Our source review and desktop input check are dated October 21, 2026. The first short Up hold produced a visible 20 mph reading; a subsequent page reading showed 15 mph while the car coasted. A later acceleration also showed 20 mph, and the saved screenshot records a later moment after key release. Those changing numbers belong to the same running demo, not a speed or frame-rate benchmark. The straight, curves and hills links describe earlier stages of this project; we checked only the final version and count it once in the directory.

Guide published 2026-10-21. Source reviewed 2026-10-21. Author release-page publication: Not established. The source describes a historical four-part teaching project, but the first-publication day of the current final-demo deployment was not established.

Game files

The final demo did not ask for a ROM, disc image, owned-game folder, upload or local archive before displaying the road and responding to acceleration. It loaded its own online resources. We did not install an engine, build the repository or open a local copy of the game. A browser entry without an own-file prompt is not a claim that nothing is downloaded, that a disconnected visit works or that all media may be redistributed. This guide points to the creator's destination and uses its own observation screenshot rather than copying the game, music or sprite files into a replacement playable page.

Controls

The live page explicitly says to drive with arrow keys. We held Up for 1000 milliseconds and observed 20 mph and changed road landmarks. After release, a later reading showed 15 mph, and the car eventually slowed further. This supports a checked acceleration input, not verified steering, braking, overtaking or a complete driving scheme. We did not change the visible resolution, lane count, road-width, camera, distance, field-of-view or fog controls. Their presence is useful context for the demonstration, but it is not evidence that each setting was tested or that a particular configuration performs best.

Account

No sign-in, email, player-name field, account creation or payment preceded the road scene and acceleration. We did not publish a lap time, connect a profile or send a result to another service. The visible fastest-lap number was already present before the input check; it is not proof that our visit set a record, recovered a stored result or retrieved another player's score. This account observation concerns the tested final-demo path, not every destination linked in the article or repository. The directory's bookmark saves only this guide's identifier, not an external lap, vehicle position or personal racing record.

Mobile gameplay

Not tested. We used a desktop browser and an Up-key hold, not a touchscreen, virtual steering control, mobile keyboard or phone orientation change. The repository includes historical performance discussion, but old browser versions and dated mobile remarks are not current compatibility measurements. We did not compare devices, browser engines, frame timing or input latency. Even a readable phone-width guide does not show that the external canvas has practical phone controls. Treat the visible performance label and counter as part of the demo's interface rather than a verified benchmark for a visitor's own hardware or a guarantee of smooth mobile racing.

Full session

A road scene and a speed response were verified, but no lap was completed. We did not establish the finish-line behavior, traffic collision rules, a winning condition, best-time persistence or recovery after closing the browser. The timer kept advancing during inspection while the car could slow after input release, so elapsed time alone does not demonstrate continuous driving or useful distance covered. We did not use the other teaching stages, alter the tuning panel or compare race settings. A screenshot containing a fastest-lap value should not be described as our achieved result, a saved record or evidence of full-session completion.

HTTP link check

An independent HTTPS request to jakesgordon.com/games/racer/ returned HTTP 200 with zero redirects on October 21, 2026. Certificate checks remained enabled. The original repository's final-demo link identifies that exact destination. The transport result is recorded separately from the road rendering and Up response; neither a successful document request nor visible fallback text would establish gameplay by itself. It also does not verify every traffic resource, another teaching stage or a future visit. We did not bypass a warning, switch to an unofficial mirror or modify the game's speed through injected code to produce the observation.

The author presents the project as a teaching demonstration rather than a finished commercial release. The earlier road stages are context for that single project, not three additional games to inflate this directory's count. Only the final entry was opened and exercised. Its source-code license should not be assumed to cover every media file in the same way, and we did not copy a music track or graphics bundle. A road view with recognizable racing imagery does not establish official OutRun affiliation, a Genesis emulator or a verified original-console edition. The untouched tuning panel, running timer and pre-existing fastest-lap value are visible interface states, not our tested settings or achievements. When comparing a later visit, identify the final stage and note whether a speed reading was taken during input or after coasting. A value falling from twenty to fifteen after release is not, by itself, evidence of an error.