This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-27
Channels
- # adventofcode (1)
- # announcements (4)
- # beginners (120)
- # calva (5)
- # cider (12)
- # clara (3)
- # cljdoc (48)
- # cljs-dev (33)
- # cljsrn (4)
- # clojure (124)
- # clojure-dev (43)
- # clojure-europe (2)
- # clojure-italy (168)
- # clojure-nl (2)
- # clojure-spec (7)
- # clojure-uk (79)
- # clojurescript (50)
- # core-logic (6)
- # cursive (12)
- # datascript (1)
- # datomic (8)
- # devcards (2)
- # emacs (5)
- # events (2)
- # figwheel-main (6)
- # fulcro (18)
- # graphql (42)
- # hyperfiddle (3)
- # jobs (1)
- # luminus (2)
- # nrepl (5)
- # off-topic (59)
- # onyx (5)
- # parinfer (2)
- # pathom (10)
- # pedestal (2)
- # portkey (3)
- # re-frame (24)
- # reagent (6)
- # reitit (54)
- # remote-jobs (1)
- # ring (5)
- # shadow-cljs (75)
- # spacemacs (35)
- # sql (22)
- # tools-deps (16)
- # unrepl (10)
i have a reagent view that i use for debugging. it lives in its own namespace and basically just looks like this: (defn debug [x] [:pre (with-out-str (pprint data))])
closure doesn't remove defmulti/defmethod
so as soon as that is used you are out of luck
fun times in npm
land. https://twitter.com/garybernhardt/status/1067111872225136640
It steals your cryptocurrency wallet.
> he emailed me and said he wanted to maintain the module, so I gave it to him. I don't get any thing from maintaining this module, and I don't even use it anymore, and havn't for years.
That is AWESOME! https://gifyu.com/image/Tr8i
I know this must have come up before, but I can't find a definitive answer. I've been using https://github.com/thheller/lumifoo as a guide to integrate shadow-cljs into a luminus project. However every time the watch socket updates the browser I get a an error "Target container is not a dom element" - what do I need to change to remedy this? thanks! - to clarify I'm just running this repo for testing with a couple of non-breaking dependency bumps and npm for react/dom etc
hi thanks for the example repo, I checked before asking and it's all fine. I think it might have something to do with the way the history is working with the page routing. I'll probably just move on and try to adapt a more recent version of the luminus template and see how I go. cheers!
actually, is there any other full stack frameworks that you could suggest that work well with shadow-cljs?
I don't program full time, just occasionally as a tool for work, so I can't really try everything out. I've used luminus as it has has good documentation and covers all the bases with sensible defaults but I'd be open to changing things up.
thanks, i did give it a go a while back but it wasn't quite so easy to get into. Also om next seemed quite daunting compared to reagent
http://book.fulcrologic.com <---- I'm pretty sure this didn't exist back then. looks great
Crytpocurrency finally made malware stop trying to steal WoW account credentials.
hey guys, I ran into an issue, where I was trying to use a local version of an npm lib, that was installed via npm install <pkg dir>
. During the release build it throws a “ExceptionInfo: files outside the project are not allowed: ” Have the same issue if you try an npm link
yeah @jcb Fulcro is a bit more to get into up front, especially compared to say reagent, etc. But, I’ve found more than once, that by the time you get done pulling in other libs, and creating some of your own utilities, etc etc you end up with a good subset of what Fulcro gives you out of the box.
also fulcro tooling has been evolving a lot lately, that's a big thing to do if you are trying to make your own stuff, IMO (disclaimer: I wrote some of those) Fulcro has top grade tools for web development (db inspector, transaction log, network log, query running built-in, tracer if used with pathom...)
@eoliphant symlinks or npm link should be allowed depending on the version you are on. forgot which version I add that though, might need to upgrade?
From the docs (:require ["module-name" :refer (export)])
- why does :refer
block is not in square brackets as usual?
@achikin it doesn't matter. use what you prefer. I prefer a list for :refer
. vector or even sets are fine too
@eoliphant are you sure its linked properly and wasn't installed nested somewhere
so I have a failure in my release
functions:
[2018-11-27T23:26:20.408Z] INFO: scrutinize-event-fn/10976 on RD28187871EEEA: interceptor error (function=scrutinize-event-fn, :namespace=cljs.user, :level=info, retry-counter=0, trace-id=3
aa0f630-2610-4cb4-9f51-8000fda9a3b8, error={})
Error: [object Object] is not ISeqable
at Object.cljs.core.seq (D:\home\site\wwwroot\cljs\shared.js:6731:9)
at Function.cljs.core.seq_reduce.cljs$core$IFn$_invoke$arity$3 (D:\home\site\wwwroot\cljs\shared.js:8386:25)
at Function.cljs.core.reduce.cljs$core$IFn$_invoke$arity$3 (D:\home\site\wwwroot\cljs\shared.js:8463:136)
at Object.cljs.core.vec (D:\home\site\wwwroot\cljs\shared.js:15652:235)
at Function.cljs.core.async.map.cljs$core$IFn$_invoke$arity$3 (D:\home\site\wwwroot\cljs\shared.js:59880:19)
at Function.cljs.core.async.map.cljs$core$IFn$_invoke$arity$2 (D:\home\site\wwwroot\cljs\shared.js:59877:30)
at Object.laputa.scrutinize_fn.fx.command_commit_event_BANG_ (D:\home\site\wwwroot\cljs\shared.js:65920:120)
at laputa.scrutinize_fn.interceptor.commit_event_BANG_ (D:\home\site\wwwroot\cljs\shared.js:66027:34)
at Object.sieppari.core.try_f (D:\home\site\wwwroot\cljs\shared.js:55118:89)
at sieppari.core.leave (D:\home\site\wwwroot\cljs\shared.js:55133:202)
I was wondering how can I see the source mapped version with release
?yep I am running simple at the moment, I did not know I needed a switch, I do have :source-maps true
yep I have:
:release {:compiler-options {:optimizations :simple
:variable-renaming :off
:property-renaming :off
:pretty-print true
:source-map true}
:autorun false}
I will double check if source-map-support
is in the deployed node_modules
together with the .map
may I ask why? the vanilla compiler does that IIRC, is there any performance impact?
yeah well I am not in control of what is passed to node
it seems like it is required, I can add it manually for sure - maybe I can open an issue and actually contribute it
right, for a second I remembered differently
I have a build like so:
:browser-tests {:target :browser-test
:test-dir "target/browser-tests/"
:module-loader true
:ns-regexp "-test"
:runner-ns runner.core
:devtools {:http-port 8021
:http-root "target/browser-tests/"}}
for some reason, this works perfectly fine on my computer but not on my coworkers. I'm using macOS and she is using Windows, though I don't think that's the issue