This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-02-05
Channels
- # arachne (7)
- # architecture (3)
- # beginners (106)
- # cider (22)
- # clara (2)
- # cljs-dev (14)
- # cljsrn (12)
- # clojure (121)
- # clojure-china (1)
- # clojure-italy (2)
- # clojure-spec (22)
- # clojure-uk (32)
- # clojurescript (38)
- # community-development (45)
- # cursive (15)
- # datascript (6)
- # datomic (12)
- # defnpodcast (2)
- # emacs (8)
- # events (1)
- # fulcro (14)
- # immutant (6)
- # jobs (3)
- # jobs-discuss (6)
- # jobs-rus (3)
- # keechma (4)
- # keyboards (4)
- # leiningen (8)
- # luminus (1)
- # off-topic (91)
- # onyx (13)
- # parinfer (36)
- # re-frame (12)
- # reagent (23)
- # remote-jobs (1)
- # ring-swagger (3)
- # shadow-cljs (57)
- # specter (11)
- # sql (9)
- # uncomplicate (4)
- # vim (2)
- # yada (15)
@mihaelkonjevic Do you know how to get source-mappings working with pipeline controllers? Currently, when a pipeline controller throws an exception (i.e. in a promise), I get a long stack trace, but the line numbers do not correspond with the cljs code. I'm using shadow-cljs, so not sure if this is a common problem, but was just wondering whether it is something I'm doing wrong or just the way things are.
@mjmeintjes This is a tricky one, but I did find a solution. First, there are some changes in Keechma Toolbox that will be pushed in the next release. This will get us half way there - it will report the correct error location in the built JS file. Second part of the solution is https://www.npmjs.com/package/source-map-support which needs to be installed in the app so it applies source maps to the stacktrace
this is how the stack trace looks then:
I’ll push the new version of Keechma Toolbox this week