Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Quick Start mentions stack trace which no longer appears

Open
  • Is something wrong?
#305 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
clojure
Domain
documentation

Research direction

Start in the Quick Start section containing the (ffirst [1]) example and compare its stated output with the current ClojureScript REPL output shown in the issue. Update the example's description so it accurately reflects the stack trace behavior, then review the rendered Quick Start page.

Written by the indexing model from the issue text.

Description

minor

In Quick Start:

Let’s make a mistake. Try evaluating (ffirst [1]). You should get a source mapped stack trace ...

But with recent changes stack traces are no longer printed by default:

ClojureScript 1.10.516
cljs.user=> (ffirst [1])
Execution error (Error) at (<cljs repl>:1).
1 is not ISeqable
Dominant language
Shell
Stars
107
Forks
130
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from clojure/clojurescript-site

All issues in clojure/clojurescript-site

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.