Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error thrown on new cljs REPL in fresh project #201

Open
eggsyntax opened this issue Nov 6, 2017 · 1 comment
Open

Error thrown on new cljs REPL in fresh project #201

eggsyntax opened this issue Nov 6, 2017 · 1 comment

Comments

@eggsyntax
Copy link

eggsyntax commented Nov 6, 2017

Hi,

If I create a luminus project with the +cljs option, as soon as I open clj & cljs REPLs, I get an error thrown (pasted below).

It looks like this is maybe an issue with cljs 1.9.946, as suggested here and here. Adding an explicit dependency on tools.reader 1.1.0 to the project.clj of the created project eliminates the error. Dropping the cljs version to 1.9.908 also prevents it.

This isn't in my way at all (I was just creating a luminus project to test out another project), just wanted to let you know. Also, despite the error, at least basic functionality (eg (+ 1 1)) continues to work in both clj and cljs repl, so I don't know whether it's actually breaking anything.

   No reader function for tag Inf
   {:type :reader-exception,
    :line 988,
    :column 14,
    :file
    "file:/home/egg/.m2/repository/org/clojure/clojurescript/1.9.946/clojurescript-1.9.946.jar!/cljs/core.cljs"}

                  core.clj: 4617  clojure.core/ex-info
                  core.clj: 4617  clojure.core/ex-info
          reader_types.clj:  391  clojure.tools.reader.reader-types/reader-error
          reader_types.clj:  387  clojure.tools.reader.reader-types/reader-error
               RestFn.java:  439  clojure.lang.RestFn/invoke
                reader.clj:  824  clojure.tools.reader/read-tagged
@yogthos
Copy link
Member

yogthos commented Nov 6, 2017

Ah thanks for the heads up, I guess adding tools.reader explicitly for now would be the way to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants