Has anyone run into problems using node mjs files on Clojure Script?

I keep hitting this ecma6 import vs require... And I feel like I keep crashing into a wall

ok, heads up… there’s an issue with the latest node 14, typescript, not recognizing .ts files when you enable Ecma6 modules… I have the intuition this will affect clojurescript being able to load npm modules, until they fix it…

so don’t get your hopes up about using the latest node version, ts, and ecma6 together

Quick tip for new users of the :target :bundle feature: Some JS libraries may require certain objects to be available in global scope. Some CLJSJS libs have done that for you. With bundle target, depending only on package.json you no longer get globals. You can solve that with the following webpack config, where reactstrap is a plain NPM module from your package.json . It makes the global GlobalReactstrap available to all other modules.

const webpack = require('webpack');

module.exports = {
   plugins: [
     new webpack.ProvidePlugin({      
       GlobalReactstrap: 'reactstrap'
     })
   ]   
}

How define new var in library. In clojure I would do:

(in-ns 'some-library) 
(def new-symbol-in-library "X")

you can't really do that

Ok good to know

Hello, mongodb can run javascript code for map reduce,or in filter using javascript using $where, is it possible to use Clojurescript instead? thank you

So I have a custom literal tag defined in a data_readers.cljc:

{
 lstr ont-app.vocabulary.lstr/read-LangStr
}

> (def x (read-LangStr "gaol@en-GB"))
> x
#lstr "gaol@en-GB"
> (type x)
ont-app.vocabulary.lstr/LangStr

Attempting to call unbound fn: #'ont-app.vocabulary.lstr/read-LangStr

you need to ensure that the ont-app.vocabulary.lstr namespace is loaded before whatever namespace that uses the reader tag

the CLJS compiler does not guarantee this by default

I'm including this namespace in the require section of the testing module, and requiring it in the repls. Is that not enough?

the requires are pulled in in order, so the one asking for the implementation of the tag must be before all the ones that use it

alternatively, you could require the implementation ns for the reader function in every ns that uses that tag

I thought I was doing that. My require within my test module contains [ont-app.vocabulary.lstr].

Is there a way in lein/cljsbuild to specify that the lstr module is fully loaded before evaluating the data_readers.cljc file?

clojure never does parallel loading

well, I guess you could do something weird and force it to, but it won't do it via normal require forms

the next require never happens until the previous succeeds

it’s hard for us to infer exactly what you mean by > my require within my test module the idea is that in your dependency graph, ont-app.vocabulary.lstr must be loaded before any code that uses it so if you do e.g.:

(ns module.a
  (:require [ont-app.vocabulary.lstr]
            [module.b]))

(ns module.b)

#lstr "foo"

ont-app.vocabulary.lstr
         /
module.a
         \
           module.b

No, the problem is happening here:

(ns ont-app.vocabulary.core-test
  (:require
   [ont-app.vocabulary.lstr :as lstr]
   ))

Then

(test yadda yadda #lstr "blah@en")

that’s surprising

A 'fix' is

(read-string "#lstr \"asdf@en\"")]

where read-string is cljs.reader/read-string

So it appears that the tag-table that informs the execution env uses a tag table with fully resolved function, but the compiler of the source only knows about the mapping, but not the definition of the function.

@eric.d.scott Not sure if this helps, but if I'm understanding you, I've solved that problem in this example by using -i to cause the definitions to be available to the ClojureScript compiler before the compiler runs: https://github.com/mfikes/precise (see the use of clj -i)

Am I correct in the impression that I'd need to switch from lein to deps to do this?

Perhaps there is a way to do the same with lein

Thanks @mfikes, I'll poke around a bit with this idea.

What's the meaning of this error?:

router.cljc:204 Uncaught Error: [object Promise] is not ISeqable
    at Object.cljs$core$seq [as seq] (core.cljs:1226)
    at re_frame$fx$do_fx_after (fx.cljc:74)
    at Object.re_frame$interceptor$invoke_interceptor_fn [as invoke_interceptor_fn] (interceptor.cljc:71)
    at Object.re_frame$interceptor$invoke_interceptors [as invoke_interceptors] (interceptor.cljc:109)
    at Object.re_frame$interceptor$execute [as execute] (interceptor.cljc:204)
    at Object.re_frame$events$handle [as handle] (events.cljc:65)
    at Object.eval [as re_frame$router$IEventQueue$_process_1st_event_in_queue$arity$1] (router.cljc:179)
    at Object.eval [as re_frame$router$IEventQueue$_run_queue$arity$1] (router.cljc:198)
    at eval (router.cljc:146)
    at Object.eval [as re_frame$router$IEventQueue$_fsm_trigger$arity$3] (router.cljc:169)

happening for these lines:

(let [create-token (.createToken stripe card-element)]
            (.then create-token
                   (fn [result]
                     (prn "result is" (.-token result)))))

you are passing a Promise to something that expects a CLJS seq

.then expects a cljs seq?

any cljs collection. vector probably.

what does this error mean:

react-dom.development.js:11366 Uncaught TypeError: lastCallbackNode is not a function
    at flushFirstCallback (scheduler.development.js:108)
    at flushImmediateWork (scheduler.development.js:170)
    at exports.unstable_runWithPriority (scheduler.development.js:262)
    at runWithPriority$2 (react-dom.development.js:11306)
    at flushSyncCallbackQueueImpl (react-dom.development.js:11350)
    at flushSyncCallbackQueue (react-dom.development.js:11339)
    at scheduleWork (react-dom.development.js:21432)
    at Object.enqueueForceUpdate (react-dom.development.js:13146)
    at cmp.Component.forceUpdate (react.development.js:354)
    at Object.reagent$impl$batching$run_queue [as run_queue] (batching.cljs:38)

you are passing something that is not a function to something that expects a function

how do I find which line this is happening?

reagent$impl$batching$run_queue so something you passed to reagent at some point I guess. if you use chrome you can use "pause on uncaught exception" and look at the value in lastCallbackNode. maybe that has a clue for what you passed.

@thheller that lands me to:

try {
    continuationCallback = callback();
  } finally {
    currentPriorityLevel = previousPriorityLevel;
    currentExpirationTime = previousExpirationTime;
  }

I'm pretty sure the error is in my events.cljs, but not about which line

don't look at the code, that doesn't matter.

look at the variables on the side

what are the variables supposed to tell me and which ones do I look at?

I have no clue. lastCallbackNode is the name you are looking for. sorry I can't really explain how to use the debugger in more detail. bottom line is that you are probably passing an incorrect value into something somewhere

can't help more than that, going to bed now. good luck 😛