It might depend on the build tool that you're using. Shadow-cljs should handle it just fine. Also check what that module actually says in the "main" key in its package.json. If that doesn't provide any clues, you can always use a full path relative to node_modules.

Check what useMagicLink is with js/console.log. Sometimes it's not what it's supposed to be.

ha it’s undefined

Try using :as instead and see what it outputs then.

yeah changing to as works, which seems like a #shadow-cljs bug

It's not a bug, it's well documented: https://shadow-cljs.github.io/docs/UsersGuide.html#_using_npm_packages

the cljs looks correct I think. maybe you need to init thing first? e.g. const res = await magic.oauth.getRedirectResult();

#js reader tag is not recursive.

is it being printed in that order? I would expect it to print in the opposite order either way there's no explicit order dependency between the reset! and the _ (js/console.log "social logged in " @!social-logged-in).

maybe try something like:

(defn login []
  (let [
        magic (new-magic)
        !social-logged-in (atom nil)
        _ (go (js/console.log "is logged in " (<p! (.. magic -user (isLoggedIn))
                                                   )))
        reset-ch (go (reset! !social-logged-in
                      (<p! (.. magic -user (isLoggedIn))
                           )))
        _ (go
            (<! reset-ch)
            (js/console.log "social logged in " @!social-logged-in))
        
        ]
   ))

is <! valid in cljs?

yes they are printed in that order

yes, <! is valid in cljs. it's <!! that doesn't work

yeah that does print true for both, but why is <! required?

you want to print the result after the reset! has been run

but how will this fit into the rest of the code? this is what follows the let bindings:

[:div
     (if @!social-logged-in
       [:div {:style {:cursor :pointer}
              :on-click #(.. magic -user (logout))} "Logout"]
       [:div {:style {:display :flex :flex-direction :row}}
        [:img
         {:on-click (fn [event]
                      (go
                        (<p! (.. magic -oauth
                                (loginWithRedirect
                                 #js {:provider "facebook"
                                      :redirectURI
                                      (.. js/window -location -origin)})))))
          :src ""
          :style {:cursor :pointer :height 50}}]])]

what UI library are you using?

reagent

is the atom an r/atom or the built in one?

built in

it should be an r/atom so that it will rerender when the value is updated

Because you used >! not in a go block?

The last line in your code.

heh ok. total newbee here... thanks man!!

I’m not sure what you mean here. Emit to where? If it’s the output stream then non strings can be converted, can’t they? Or am I missing something important here?

For instance, I have code in a defrecord that emits the object as tagged data (specifically to emit in edn):

IPrintWithWriter 
  (-pr-writer [this writer _] (-write writer (str this)))

Or, are you wanting to emit some kind of byte serialization?

@U051N6TTC I have my own *print-fn*, that can handle non-string values. I'd just like to send them through the println function if possible.

So, what am I missing with using IPrintWithWriter?

Doesn't str emit a string?

If so, I don't want non-strings to be converted to strings. I want my custom *print-fn* function to get non-strings and embed them in the DOM.

Although I could be missing something. There seems to be a lack of documentation for the -pr-writer function. 😞

str emits a string, yes. That’s what I sent to the -write function in my version of -pr-writer, but what else do you want to send to -write? Do you want to serialize something else into bytes?

In my case, I have an object which wraps a number, and the string form is #a/n[1234]. By extending the object to IPrintWithWriter and having it call -write with the string form, then I get it printing properly at the repl, etc. I’m still trying to understand what you want to do, sorry

No worries. Ultimately, I would like to write out a DOM node.

For context, I'm making this for clojurescript: https://www.youtube.com/watch?v=8htgAxJuK5c

And by that, I don't mean a serialization of the dom node. I'd like to print out the dom node itself. (If I have to pass through a serialize/deserialize layer than oh well. I'll get around to it later.)

But what do you mean by “print out the dom node”? Because if you’re printing it, then it’s a string, right?

Nope. Consider a web browser's console. When you print a DOM node to the console using console.log, you get a live object of that DOM node.

Its not just a string, its the data structure itself.

actually, I did not know that. I thought that once it hit the console that it was a static snapshot rendered as a string

Though, with immutable objects then it does this

Ah, nope. It actually is a thing that initially throws off a lot of devs, because javascript objects are mutable.

And if the object gets mutated after its printed out to the console, the object in the console changes.

So if you want a static render, you need to stringify and reparse it. (Per the MDN page anyway)

https://developer.mozilla.org/en-US/docs/Web/API/Console/log#logging_objects

Yes, I got that. So you want to be sending DOM objects through -write?

Ideally yes.

If that's not possible I'll eventually set up a mechanism to do the serialize/deserialize trick.

I don’t know the implementation of the writer, so I don’t know if it can take objects?

It doesn't seem to be able to. 😞 (Hence my original question.)

Anyway though, thanks for the suggestion. 🙂

I don’t know… maybe it does? It lets you send objects to it

I don’t know if it’s only converting them to strings as it renders to my repl though 🙂

I don’t have a repl in a browser to test it

(deftype MyData [data]
  IPrintWithWriter
  (-pr-writer [this writer _] (-write writer {:data data})))

=> (MyData. 5)
{:data 5}

But my repl is based on Node, since I don’t usually work in a browser

OOHH, this might be exactly what I want. I'll take a look at it. Thanks.

@U051N6TTC Ah, sadly it looks like it does cast it to a string. Oh well. Thanks again. 🙂

Where are you wanting your data to go? To the console?

If not, then does it need to be a standard protocol? Would it be possible to create your own, and then extend desired types to it? (Extending object for the default case)

@U051N6TTC Ultimately,, it's going into a <div> in the DOM that's meant to look like a console.

But ya, it doesn't have to use a standard protocol. I had just hoped to be able to, that way users don't have to add :refer-clojure :eexclude [println ...]).

But that seems like it would only be necessary if you’re trying to insert a printed version into the DOM? Couldn’t you allow the standard printing to take place elsewhere, and then use your protocol for DOM insertion? I’m sorry. I keep feeling like I’m missing obvious things when we’re talking on this.

No worries, let me try to back up:

I am building an IDE in the browser using cljs.js. In this IDE, users both write and run their code directly in the browser.

In addition to supporting vanilla clojurescript, the IDE needs to support VISRs, which are mix of a macro, combined with a renderer, and some state (probably using deftype).

Users can print a VISr like any other object, but when they do, I want it to show up in the repl as a rich object, and not just its textual representation.

And I would ideally let users do the printing with standard print functions (`print`, println,`pprint`,etc.)

Does that make any more sense @U051N6TTC?