With latest shadow-cljs (`2.8.29`), I am getting this on shadow-cljs watch:

/home/manuel/7bridges/code/cinvat-explorer/.shadow-cljs/babel-worker/babel-worker.js:3497                                                                                                                            
!0,Hg.Ya="cljs.core.async.impl.ioc-helpers/t_cljs$core$async$impl$ioc_helpers243717",Hg.Hb=function(b){return Vb(b,"cljs.core.async.impl.ioc-helpers/t_cljs$core$async$impl$ioc_helpers243717")};return new Hg(a,oe)$
function Oi(a){try{var b=a[0];return b.l?b.l(a):b.call(null,a)}catch(c){if(c instanceof Object)throw b=c,a[6].qb(null),b;throw c;}}function Pi(a,b){b=Hi(b,Ni(function(c){a[2]=c;a[1]=4;return Oi(a)}));return z(b)?(
a[2]=H(b),a[1]=4,vh):null}                                                                                                                                                                                           
                                                                                                                                                                                                                     
                                                                                               ^                                                                                                                     
                                                                                                                                                                                                                     
TypeError: Invalid value used as weak map key                                                                                                                                                                        
    at WeakMap.set (native)                                                                                                                                                                                          
    at d (/home/manuel/7bridges/code/cinvat-explorer/.shadow-cljs/babel-worker/babel-worker.js:1790:192)                                                                                                             
    at /home/manuel/7bridges/code/cinvat-explorer/.shadow-cljs/babel-worker/babel-worker.js:1795:282                                                                                                                 
    at Array.map (<anonymous>)                                                                                                                                                                                       
    at /home/manuel/7bridges/code/cinvat-explorer/.shadow-cljs/babel-worker/babel-worker.js:1795:259                                                                                                                 
    at /home/manuel/7bridges/code/cinvat-explorer/.shadow-cljs/babel-worker/babel-worker.js:1700:229                                                                                                                 
    at presets (/home/manuel/7bridges/code/cinvat-explorer/.shadow-cljs/babel-worker/babel-worker.js:1794:267)                                                                                                       
    at z (/home/manuel/7bridges/code/cinvat-explorer/.shadow-cljs/babel-worker/babel-worker.js:1826:376)                                                                                                             
    at /home/manuel/7bridges/code/cinvat-explorer/.shadow-cljs/babel-worker/babel-worker.js:1825:87                                                                                                                  
    at e.buildRootChain (/home/manuel/7bridges/code/cinvat-explorer/.shadow-cljs/babel-worker/babel-worker.js:1830:93) 

what the heck is that 😛

😄

still trying to figure it out

I updated the babel stuff to the "new" babel7

but the used API is kinda tiny so not a clue

probably doesn't like something you do in the code?

does it tell you which file it failed to convert? it should?

no worries. I trashed the node_modules directory in the root of my project and re-installed the dependencies I need via npm. It works just fine as usual now. Sorry for the noise.

Hi, does someone can get airbnb react-dates(latest version) work with reagent ?

@ouvasam the general way should work? (:require ["react-dates" :as rd]) then in reagent [:> rd/Thing {:foo "bar"} ...]

Hi @thheller, no i can't make it work. It ssems that something change from version 13 and it use react-with-styles I did already try sometimes ago but went with another lib, but i really want to be able to use it.

"As of v13.0.0 of react-dates, this project relies on react-with-styles. If you want to continue using CSS stylesheets and classes, there is a little bit of extra set-up required to get things going. As such, you need to import react-dates/initialize to set up class names on our components. This import should go at the top of your application as you won't be able to import any react-dates components without it."

and what does that produce?

looks correct to me?

Something like this but it doesn't open selector or nothing

that looks like css is missing?

maybe it is opening just not anywhere visible because of missing styles?

Normally css should be included via import 'react-dates/lib/css/_datepicker.css'; But i included it in the html with a link tag. When focusing on a field the dom should change, but it is not the case for me

well in your example you have hardcoded :start-date and :end-date?

Yes but nothing change even if i use r/atom

do the callbacks trigger?

:on-dates-change #(println "on date change")?

The handler is never called since i cannot change the date

the handler is the thing changing the date so it should be called?

using the :chrome-extension target, I’m not sure how to setup my background script

my build config:

{:target :chrome-extension
   :extension-dir "extension"
   :manifest-file "extension/manifest.edn"
   :outputs
   {:devtools {:output-type :chrome/shared
               :init-fn punk.ui.chrome.devtools/init!}
    :background {:output-type :chrome/shared
               :init-fn punk.ui.chrome.background/init!}
    :panel {:output-type :chrome/shared
            :init-fn punk.ui.chrome.panel/init!}
    }}

relevant manifest.edn:

:background {:persistent false
              :scripts ["out/background.js"]}

ah. I need the bg-shared

:background {:output-type :chrome/background

oo fancy

are there docs for :chrome-extension yet?

no

OK I see my script loaded in the background page, but I don’t see any output

ex I currently have this in my background ns:

(defn init! []
  (log "bg init"))

build config is now:

:background {:output-type :chrome/background
                 :init-fn punk.ui.chrome.background/init!}

IIRC log output from background page is in the original devtools

not the nested ones

or the other way .. its weird

o_O

I have 3 devtools open lol

might need to open the background page

I can't remember really

yeah, I have the background page open (I think)

background page console is empty

my devtools page is where all my REPL output seems to go

and the console for the page I’m inspecting is blank

does :type :chrome/background take an :init-fn or something else?

I don’t actually see my namespace even loaded

maybe only supports :entries not actually sure

its been a while since I worked on that

do I need to include any of the other .js files like shared.js or bg-shared.js?

you don't include either?

for the background script, I’m just include background.js atm

you have html for your background page? shouldn't have?

chrome docs say I can just give it a JS file and I think it generates an HTML page for me

:background {:persistent false
              :scripts ["out/background.js"]}

uhm wait you have your own manifest?

right .. don't do scripts

☝️ that’s what I wrote in my manifest.edn

just leave that out completely

k, trying

:chrome/background takes care of it

hmm, lots of errors now

sorry I don't have time to look at that further now

np

dig into the shadow/build/targets/chrome-extension.clj file

maybe that makes sense and you can figure it out

FWIW I restarted my shadow-cljs process. I’m now getting errors about websockets. it looks like the background page is trying to connect to the shadow-cljs process

ah no, it’s still the old errors preventing it. nvm. I’ll dig into it

see https://github.com/fulcrologic/fulcro-inspect/blob/master/shells/chrome/manifest.edn#L11-L18

sigh. I’m sorry thheller. I cleared out my .shadow-cljs and it started working 😞

that should absolutely NEVER be necessary

if it is its a bug

I really need to figure out why is happening for you guys .. I have never had a problem where deleting anything was necessary

the next time I see the startsWith error, I’ll zip up my builds folder and send it your way

I already identified that problem with the code Wilker sent me, just can't explain how it happens

yeah super strange. I thought it had something to do with switching between diff versions of the closure library

since it was occurring so frequently when we would switch between branches with different shadow-cljs versions

yes that would cause such a problem but the file that triggers the bad behavior should be written correctly always

but in this project, I’ve only ever used latest shadow-cljs. I was modifying shadow-cljs.edn and the manifest.edn, and my new background page exhibited the same behavior

yeah dunno .. can't concentrate on this now .. gotta fix other work stuff

👍

is there any way to change the CLOSURE_BASE_PATH output by a browser compilation? I’d like it to output a relative path but it’s prepending a /, making it an absolute path and breaking dep resolution

set :asset-path in your config

for some reason, in my background script i have a namespace that won’t load unless I trigger it to compile that namespace

it loads in my :browser target fine

(ns punk.ui.encode
  (:require [cljs.reader :as reader]))

(defn write [x]
  (prn-str x))

(defn read [x]
  (reader/read-string x))

sounds like the other issue again. please check the background.js

there should be some load instructions

it might be missing that file?

hm. right off hand, I don’t see the load instructions

anything I can CTRL-F for?

punk.ui.encode

that’s definitely not anywhere in background.js

ah no wait .. nvm

but I don’t see any other load instructions so I might be looking in the wrong place

it is using chrome for loading

need to reload the chrome ext probably

ahhh

since the manifest changed

so I’ll need to do that anytime I add a new ns?

currently yes

👍

Can someone translate to a noob what this means and what I should do instead?

[:app] Configuring build.
[:app] Compiling ...
[:app] Build failure:
------ ERROR -------------------------------------------------------------------
 File: /Users/d4hines/repos/rectangles/src/rectangles/view.cljs:14:20
--------------------------------------------------------------------------------
  11 | (prn fps-div)
  12 | (add-watch fps :fps
  13 |            (fn [k r o n]
  14 |              (set! (.-innerHtml fps-div (str "<p>" n "<p>")))))
--------------------------^-----------------------------------------------------
Error in phase :compilation
dot prop access with args
{:form (. fps-div -innerHtml (str "<p>" n "<p>"))}
ExceptionInfo: dot prop access with args

I have no idea, but my best guess would be it doesn’t like you passing arguments when trying to access the innerHtml?

maybe possibly it’s like this (set! (.-innerHtml fps-div) (str "<p>" n "<p>"))

(def fps-div (. js/document -getElementById "fps"))

Also fails the same way.

:thinking_face:

maybe (def fps-div (.getElementById js/document "fps"))

IIRC the .-something was to access a property, and method calls were just (.whatever whatever-you’re-calling-it-on arguments)

I found this on stack overflow, it seems like what you’re trying to attempt. :man-shrugging: I dunno.

@d4hines that’s invalid syntax

what Mno is saying is correct

I’m giving myself a gold star ⭐

Aha! Thanks guys.

your first example would be (. fps-div innerHtml (str “<p>” n “<p>”)) for proper syntax. but also, I’m not sure you can call node.innerHtml as a function?