Update the version number of figwheel-sidecar in the ProtoREPL instructions
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- clojure
- Domain
- documentation
Research direction
Start with the ProtoREPL instructions at the linked clojurescript.org/tools/atom#proto-repl entry point and inspect the dependencies section. Update the figwheel-sidecar version to the version described in the issue, then verify that the documented REPL command works with the updated instructions.
Written by the indexing model from the issue text.
Description
I followed the instructions at https://clojurescript.org/tools/atom#proto-repl and I encountered an issue running this command, as listed in the instructions:
(do (use 'figwheel-sidecar.repl-api) (start-figwheel!) (cljs-repl))
This threw a spec error, the same one shown here and here, and I couldn't run the REPL. Most likely one of my dependencies uses an older version of clojure.async that causes this problem.
I followed @bhauman's instructions from this comment, by bumping up the figwheel-sidecar dependency to 0.5.10. After that, I was able to run the clojurescript repl in the atom protorepl.
I propose at minimum updating the figwheel-sidecar version to 5.10 to prevent new users to the protoREPL from encountering this. The whole dependencies section could possibly use some updating, though.
I also tested this on a brand new app built using the template from "lein new figwheel ...". Everything worked as expected.
*Edit: this all occurred while running Clojure 1.9.0 and Clojurescript 1.10.238
- Dominant language
- Shell
- Stars
- 107
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from clojure/clojurescript-site
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
clojure/clojurescript-site#413 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
clojure/clojurescript-site#392 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
clojure/clojurescript-site#390 · 1 comment ·
-
clojure/clojurescript-site#388 · 4 comments · 1 assignee ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
clojure/clojurescript-site#387 · 3 comments ·
All issues in clojure/clojurescript-site
Similar issues
-
good-start
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
VilnaCRM-Org/user-service#497 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conda-forge/spacy-feedstock#177 ·
-
area:jail bug security severity:low track:open-source
Difficulty 1/5 Under an hour Newbie friendliness 75/100