Hi everyone. May I please get some advice on how to debug an AssertionError Assert failed: (rc/valid-resource-id? src-id) shadow.cljs.devtools.server.worker.impl/eval17300/fn--17303/fn--17306 (impl.clj:808) error? :shadow.cljs.devtools.server.util/handle-ex reports {:msg {:op :cljs-load-sources, :sources [[:shadow.build.classpath/resource "common/lists.cljc"]... and :sources seems to include a nil which I presume is causing the problem. Unfortunately I can't quite work out what's causing the nil.

(The error happens when I try to evaluate anything once connected to the browser cljs repl)

@clojure475 what are you trying to eval? and please do not shorten errors. I need the full stacktrace to make sense of it

In my project, I'm doing a normal + bootstrap build, and when I first launch shadow-cljs, I get a bunch of warnings about a provide conflict between the normal and bootstrap builds, like this:

[2020-09-29 09:40:52.675 - WARNING] provide conflict for #{goog.structs.Set} provided by web/js/bootstrap/js/goog.structs.set.js and {"/goog/structs/set.js" #{goog.structs.Set}}

Does this represent an error on my part, that can be avoided?

don't have the output of a build on the classpath 😛

although I thought I had fixed the filtering that should take care of this

guess it doesn't account for bootstrap builds

So that's inferred or generated based on what, exactly? outdir-dir ? or asset-path ? I see no explicit classpath in my shadow-cljs.edn.

What I am doing seems to follow more or less the tutorials that exist.

So I don't find that advice of "don't do that" very easy to follow, unfortunately.

https://shadow-cljs.github.io/docs/UsersGuide.html#_important_concepts

by classpath I'm referring to your :source-paths and the :output-dir being on said source path

My :source-paths have my output dir on them - but if I remove it from source-paths and restart shadow-cljs, I get the same error.

Let's see ...

Ok, perfect.

So I ended up having that same issue in a project I was importing, which maybe seems to have been the source of the error.

Thanks for that - I'm not sure why my output dir was in the source paths to begin with.

Probably an artifact of something dumb I was doing long ago!

well it is supposed to be filtered and ignored but it looks like it just doesn't filter bootstrap builds

since the filtering is based on the cljs-runtime dir which bootstrap doesn't have

Ok, well, thank you for the insight in any case. I prefer having no warnings coming from the build if I can!

Intro and context: We are reusing some code between our web app and our react-native app and for that we need to do some runtime checks. Unfortunately we also need to convince the compiler to play along. For web it’s easy to stub out dependencies by using :js-options :resolve with :target :global. So here comes the question: If we want to use :target :global on react-native what is the best way to populate global? In our web app we can execute JS before the app runs, but on mobile I didn’t find a way to do so.

@ullrich.schaefer do you have an example of what you are stubbing out this way?

I made this example a while ago https://gist.github.com/thheller/fa044450a6470fdd1afdbcf3f37a65e3

it isn't fully explained but I hope the idea is somewhat understandable

point is that you don't do any "replacements" of the requires this way

A good example is Quill-js which is used in the main app to edit text. The mobile app is not concerned with editing text, but is including some namespaces that eventually end up importing quill. Also our main app is still build without shadow in production so we’re restricted in how we can import namespaces. There we use :global-exports in deps.edn. We use shadow for dev though so we can just do :js-options {:resolve {"quill" {:target :global :global "quill"}}} . Quill is just one of many examples and it would be great not to have to restructure all code around those dependencies, but find a solution at build tool level.

I don't get it. where does quill come from?

you might want to look into :js-provider :external if thats coming from webpack or so? only desribed here currently https://code.thheller.com/blog/shadow-cljs/2020/05/08/how-about-webpack-now.html#option-2-js-provider-external

as far as I understand for the react-native issue though you can probably just set :js-options {:resolve {"quill" false}}

that will make it just ignore that dependency entirely? not sure if you need the actual global?

I'm assuming that the code using the result isn't called at all?

otherwise (:require ["quill" :as q]) the q will be false

Yes, that’s actually what we’re looking for. We’ll try that and I’ll report back to you. Sorry, but our setup is a bit complicated and grew a bit over the years 😄 Our dependencies on web are loaded using an outdated approach called doublebundle, described https://presumably.de/double-bundle-integrating-npm-dependencis-into-clojurescript-projects.html. Certainly something we need to transition away from at some point. A lot of good things happened to the CLJS ecosystem over the last years. Shadow being one of them 🙏 🙇

look into the :external stuff maybe

thats basically a half-automated double-bundle

Having some problems with my project after installing some npm dependencies Uncaught TypeError: Cannot read property 'hydrate' of undefined

(ns pwa.core
  (:require [react-dom :as react-dom]
            [reagent.core :as r]))

Why would react-dom be undefined here?

Is the reagent dependency somehow conflicting with the react/react-dom in package.json?

@danielstockton there is no use of hydrate in the code you pasted so no clue how you are using it?

Sorry, just using it like this

(ns ^:figwheel-hooks pwa.core
  (:require [pwa.shared :as shared]
            [react-dom :as react-dom]
            [reagent.core :as r]))

(defn mount [el]
  (react-dom/hydrate (r/as-element [shared/root]) el))

looks fine

check if your node_modules/react-dom is empty for some reason

sometimes that can happen with npm

Yeah, these problems started after i installed html-react-parser for the server side part, which meant i also had to install react and react-dom with npm. Have tried clearing node_modules completely and reinstalling multiple times, npm installing the same version as reagent (16.13.0)

ls node_modules/react-dom/
build-info.json  index.js  package.json  README.md          server.js       test-utils.js  unstable-fizz.browser.js  unstable-fizz.node.js
cjs              LICENSE   profiling.js  server.browser.js  server.node.js  umd            unstable-fizz.js          unstable-native-dependencies.js

react-dom folder not empty

if you haven't restarted shadow-cljs after running npm install or so maybe try doing that

I've been banging my head against Calva and VSCode with shadow all day and I'm spent... anyone know why when I eval a namespace nothing seems to get loaded?

here's my shadow-cljs.edn:

{:source-paths ["src"]
 :dependencies [[cljs-ajax "0.8.0"]
                [org.clojure/core.async "1.3.610"] ; ignored by shadow-cljs (embedded)
                [funcool/cuerdas "2.2.0"]
                [clojusc/defun "0.4.0"]
                [frankiesardo/linked "1.3.0"]
                [jamesmacaulay/cljs-promises "0.1.0"] ; FIXME: When batching cartography files: uncomment and `shadow-cljs pom`
                ;;[cider/cider-nrepl "0.23.0"] ; for Calva + Shadow-cljs 
                [net.cgrand/xforms "0.19.2"]]
 :nrepl        {:port 3333}
 :builds       {:lib {:target           :node-library
                      :output-dir       "public/census"
                      :output-to        "public/census/census.js"
                      :compiler-options {:optimizations :advanced
                                         :source-map-include-sources-content false}
                      :exports-var      census.core/census}
                :geo {:target           :node-library
                      :output-dir       "public/geo"
                      :output-to        "public/geo/batch_convert.js"
                      :compiler-options {:optimizations :simple}
                      :exports-var      configs.geojson.core/batch_convert}}}

... here's what I'm trying to load:

(ns configs.geojson.core
  (:require
   [cljs.core.async           :refer [>! <! chan promise-chan close! take! put! pipeline-async]
    :refer-macros [go go-loop]]
   [cuerdas.core              :refer [join]
    :as s]
   [clojure.set               :refer [map-invert]]
   [defun.core                :refer-macros [defun]]
   [cljs-promises.async       :refer [value-port]] ;; Fixme: Need this dependecy -< move configs to separate project
   [census.utils.core         :refer [map-target error err-type]]
   [configs.utils.core        :refer [read-edn FileSaver]]
   [configs.geojson.filepaths2018 :refer [paths]]
   [clojure.reader :refer [read-string]]
   ["fs" :as fs]
   ["shpjs" :as shpjs]
   ["mkdirp" :as mkdirp]))

(def geoKeyMap (read-edn "./src/configs/geojson/index.edn"))

and here's what's eval'd:

clj::shadow.user=> 
; Creating cljs repl session...
; Connecting cljs repl: shadow-cljs...
;   The Calva Connection Log might have more connection progress information.
; Connected session: cljs, repl: node-repl
; TIPS: You can choose which REPL to use (clj or cljs):
;    *Calva: Toggle REPL connection*
;    (There is a button in the status bar for this)
cljs::cljs.user=> 
; Evaluating file: core.cljs
; ------ WARNING - :redef --------------------------------------------------------
;  Resource: <eval>:16:1
 resolve already refers to: cljs.core/resolve being replaced by: cljs-promises.core/resolve
--------------------------------------------------------------------------------

nil
cljs::configs.geojson.core=> 
#object[TypeError TypeError: Cannot read property 'core' of undefined]
cljs::configs.geojson.core=> 

I've tried using a remote session and a straight "jack-in" workflow both using a build id as well as just a node-repl I get the same no matter

@loganpowell the problem might be the warning

I can't see what the REPL is actually doing (like what was eval'd) so I can't tell

might be that the warning skips loading the code

let me try without defun

defun? the warning is from cljs-promises? no clue what defun is?

sorry, that's what I meant

Q: has anyone ever done aws interop to implement x-ray tracing for the entire SDK as documented here https://docs.aws.amazon.com/xray/latest/devguide/xray-sdk-nodejs-awssdkclients.html ? I can’t figure out the incantation for Shadow style interop

what incantation?

can't tell from the page since either example is missing code to understand what any of it means

I agree. That’s part of my problem. I’m experimenting with it now, looking at the generated js to try and match it up. I’ll report back if/when I get it working

(sorry, by “incantation”, I meant “interop form”. that’s me being too clever)

yes but which form do you mean?

var AWS = AWSXRay.captureAWS(require('aws-sdk')); that example doesn't explain where AWSXRay is coming from

var ddb = AWSXRay.captureAWSClient(new AWS.DynamoDB()); that doesn't explain where AWS is coming from

so I can't tell how this is supposed to be used

unless its supposed to be used together

var AWSXRay = require('aws-xray-sdk');
    var AWS = AWSXRay.captureAWS(require('aws-sdk'));
    var ddb = AWSXRay.captureAWSClient(new AWS.DynamoDB());

in which case the documentation is just plain weird

but which part do you have an issue with?

(ns foo.bar
  (:require
    ["aws-xray-sdk" :as aws-xray]
    ["aws-sdk" :as aws-sdk]))

(def aws (aws-xray/captureAWS aws-sdk))
(def ddb (aws-xray/captureAWSClient (aws.DynamoDB.)))

maybe that helps. no clue what any of it does but that would be the translation

yep, resolve already refers to: cljs.core/resolve being replaced by: cljs-promises.core/resolve is the issue, when I remove that, smooth sailing. Is there a way to alias a function within a dependency like this?

thanks @thheller I figured it out. the confusing part was around calling the “new” which is not very lispy. And yes, the AWS doc is not clear at all

the solution is…. use these 2 requires

["aws-sdk" :as aws-sdk-clean]                   ; clean means without x-ray
          ["aws-xray-sdk" :as aws-xray-sdk]
          

(let [capture-full-sdk (j/get aws-xray-sdk :captureAWS)]
  (capture-full-sdk aws-sdk-clean))

[s3-client (j/get aws-sdk :S3)
      s3 (new s3-client)]

was not obvious but this works