This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-16
Channels
- # announcements (1)
- # babashka (23)
- # beginners (157)
- # boot (3)
- # calva (2)
- # chlorine-clover (12)
- # cider (14)
- # clara (5)
- # clj-kondo (6)
- # cljs-dev (61)
- # cljsrn (30)
- # clojure (65)
- # clojure-argentina (8)
- # clojure-berlin (2)
- # clojure-europe (13)
- # clojure-france (9)
- # clojure-germany (2)
- # clojure-italy (4)
- # clojure-nl (6)
- # clojure-portugal (2)
- # clojure-romania (2)
- # clojure-uk (76)
- # clojurescript (56)
- # conjure (52)
- # core-async (37)
- # datomic (209)
- # duct (17)
- # emacs (17)
- # exercism (1)
- # fulcro (26)
- # graalvm (5)
- # instaparse (2)
- # jackdaw (9)
- # jobs-discuss (27)
- # joker (2)
- # juxt (23)
- # leiningen (4)
- # malli (11)
- # midje (3)
- # pedestal (2)
- # quil (2)
- # re-frame (78)
- # reagent (8)
- # reitit (18)
- # remote-jobs (1)
- # ring (2)
- # ring-swagger (1)
- # shadow-cljs (29)
- # sql (11)
- # test-check (12)
- # tools-deps (5)
- # xtdb (16)
- # yada (4)
Any ideas what could cause parse errors with Node modules? In this case I'm having problems with Openlayers 6. I also had to remove .shadow-cljs/builds
to even get Shadow-cljs to use the new sources.
------ WARNING #1 - -----------------------------------------------------------
Resource: node_modules/ol/Feature.js:107:20
Parse error. name not recognized due to syntax error.
--------------------------------------------------------------------------------
------ WARNING #2 - -----------------------------------------------------------
Resource: node_modules/ol/layer/BaseVector.js:106:20
Parse error. name not recognized due to syntax error.
--------------------------------------------------------------------------------
------ WARNING #3 - -----------------------------------------------------------
Resource: node_modules/ol/layer/Layer.js:131:20
Parse error. name not recognized due to syntax error.
--------------------------------------------------------------------------------
------ WARNING #4 - -----------------------------------------------------------
Resource: node_modules/ol/renderer/Layer.js:52:20
Parse error. name not recognized due to syntax error.
--------------------------------------------------------------------------------
------ WARNING #5 - -----------------------------------------------------------
Resource: node_modules/ol/renderer/canvas/Layer.js:57:20
Parse error. name not recognized due to syntax error.
--------------------------------------------------------------------------------
------ WARNING #6 - -----------------------------------------------------------
Resource: node_modules/ol/renderer/webgl/Layer.js:87:20
Parse error. name not recognized due to syntax error.
--------------------------------------------------------------------------------
------ WARNING #7 - -----------------------------------------------------------
Resource: node_modules/ol/source/Vector.js:89:20
Parse error. name not recognized due to syntax error.
--------------------------------------------------------------------------------
------ WARNING #8 - -----------------------------------------------------------
Resource: node_modules/ol/source/Vector.js:216:20
Parse error. name not recognized due to syntax error.
--------------------------------------------------------------------------------
https://unpkg.com/browse/[email protected]/Feature.js
line 107
_this.geometryChangeKey_ = null;
What is parsing the files? Closure?
Yeah, I'm having some problems with OL but could be unrelated to these warnings.
I'm doing something slightly weird, but I'm wondering if anyone can help me resolve an inference issue. The short version is, I just enabled :infer-externs
, and I am getting a warning from anything in my code that implements reagent.ratom.IReactiveAtom
, which is just a methodless tag interface. The error looks like: Cannot infer target type in expression (. (. Example -prototype) -reagent$ratom$IReactiveAtom$)
@pmooser try (:require [reagent.ratom :as ratom])
and (deftype Example [] ratom/IReactiveAtom)
@thheller I tried that with the same result. For now I've just turned off the inference feature, since it seems to work fine without it.
Has anyone seen this with shadow-clj 2.8.95? It appears to be a misalignment between the assertion and the message keys.
Hello, I am trying to configure https://github.com/borkdude/clj-kondo to work with my shadow-cljs project. To configure it, I need to get the classpath. Other build tools have commands like lein classpath
or clojure -Spath
but I could not find something similar for shadow-cljs. Any tips on getting the classpath for a shadow-cljs project?