@eliascotto94 move it to a foo.config namespace that you can reference everywhere. the problem is having this in foo.core so just move it out. I personally have a my.app.env namespace in every app for such purposes

otherwise a circular reference is not allowed

hey guys, I have run into a really weird issue, and am not able to figure out the root cause. In my setup, I'm importing a js source file (compiled to commonjs), directly inside my CLJS source. Th error is that a required module is not defined:

var s = _interopRequireWildcard(require("@solana/web3.js"));

so you mean you have this fine on the classpath imported via (:require ["/some/thing.js" :as x])? ie. not a file in node_modules

re the problem I had yesterday, I tested more and got EXTREMELY confusing results, they seem to imply the existence of shadow-cljs (or connected js tooling) global state outside of "yarn link" elements (which are in ~/.config/yarn/link/...). The only global state I can think of are global shadow-cljs installs and globally installed NPM modules but maybe there is more?

in my case, I'm being naughty and sym linked a js package source to my project root. and then started requiring it in my cljs source 🤐

shadow-cljs doesn't use globally installed npm modules. it just uses whatever is in node_modules in your project

if yarn puts something global in there it is no longer global

jar: 2.16.12 cli: 2.16.12 deps: 1.3.2 config-version: 2.16.12 Does the "deps" here refer to the version specified in "deps.edn"?

no

when using deps.edn nothing in info matters basically

deps.edn overrides all of it

shadow-cljs doesn't use globally installed npm modules you say, is there still a "global" state in terms of whether shadow-cljs is "globally" installed

no, no global state ever

the global shadow-cljs install is just the actual shadow-cljs CLI tool. you can just remove it, it won't affect compilation in any way

only trouble it can cause is using a global install that is out of sync with the local install too much

ie. global install v1 but project install v2

basically I recommend to not use the global install but I do so myself because of the convenience 😉

hahaha I respect that

the reason I started thinking "global state" was because two disconnected projects both failled and then succeed simultaneously when only one of them was having commands run/being modified

define failed?

strange errors, the one I got above where I got a stack overflow in shadow.umd_helper.js was the initial problem, then after hacking away there was a point where compile was succeeding but the exports when "required" through vanilla nodejs cli were undefined

then after much hacking away config and dependencies to try and find the problem, it started working, but extremely weirdly the original project (I'd made a copy) also started working

> I got a stack overflow in shadow.umd_helper.js

got a stack overflow where? in what context? part of the compilation? part of running shadow-cljs?

I used yarn link which I thought was the problem but I purged all traces of it and got the same error later, unless it had snuck state into something, AFAIK the only shadow-cljs "state" is .shadow-cljs and .cpcache

shadow-cljs only .shadow-cljs yes

when importing the node-library build using javascript in a node repl, when accessing a property of the defined module, got a stack overflow

so compile etc worked

.cpcache is not something shadow-cljs ever looks at or uses

it really is much easier if you give me stack traces and full errors

ie. in the node-repl no JS is compiled by shadow-cljs and it just emits require("whatever") if you use a node library

and where, that's the name of some file that shadow-cljs generated, which seems to play a part in exports when making a node-library, full name is shadow.umd_helper.js, location in ($out_dir/cljs-runtime)

so was that a node stack overflow?

node library, not node repl

the node part implies the same, unless you override :js-provider

it was a node stack overflow when importing the file generated by shadow-cljs compile and then attempting to access one of the exported functions

yeah sorry I can't help with this without more accurate errors

happy to look at traces and stuff but this is going nowhere 😛

sorry for my poor communication, the error itself has mysteriously disappeared

probably I will accidentally summon it in a minute

projects don't share any state ever. excepts maybe if you link the same npm dependency in the local node_modules

then they share that npm dependency and if you modify that then all bets are off

but they still won't share caches or whatever but if that package is doing something crazy then both projects will be affected by it

umd_helper is just the wrapper for the :node-library output, so it'll be on the stacktrace but itself it doesn't do anything that matters

the stacktrace was all umd_helper though, whatever I'd done, there was some sort of circular reference being created inside it, otherwise how can you get a stacktrace like:

backend.test_file_store
Thrown:
RangeError: Maximum call stack size exceeded
    at Object.get [as test_file_store] (/home/zimablue/projects/kangrok-ui/.shadow-cljs/builds/node/dev/out/cljs-runtime/shadow.umd_helper.js:5:16)
    at Object.get [as test_file_store] (/home/zimablue/projects/kangrok-ui/.shadow-cljs/builds/node/dev/out/cljs-runtime/shadow.umd_helper.js:5:16)
    at Object.get [as test_file_store] (/home/zimablue/projects/kangrok-ui/.shadow-cljs/builds/node/dev/out/cljs-runtime/shadow.umd_helper.js:5:16)
    at Object.get [as test_file_store] (/home/zimablue/projects/kangrok-ui/.shadow-cljs/builds/node/dev/out/cljs-runtime/shadow.umd_helper.js:5:16)
    at Object.get [as test_file_store] (/home/zimablue/projects/kangrok-ui/.shadow-cljs/builds/node/dev/out/cljs-runtime/shadow.umd_helper.js:5:16)
    at Object.get [as test_file_store] (/home/zimablue/projects/kangrok-ui/.shadow-cljs/builds/node/dev/out/cljs-runtime/shadow.umd_helper.js:5:16)
    at Object.get [as test_file_store] (/home/zimablue/projects/kangrok-ui/.shadow-cljs/builds/node/dev/out/cljs-runtime/shadow.umd_helper.js:5:16)
    at Object.get [as test_file_store] (/home/zimablue/projects/kangrok-ui/.shadow-cljs/builds/node/dev/out/cljs-runtime/shadow.umd_helper.js:5:16)
    at Object.get [as test_file_store] (/home/zimablue/projects/kangrok-ui/.shadow-cljs/builds/node/dev/out/cljs-runtime/shadow.umd_helper.js:5:16)
    at Object.get [as test_file_store] (/home/zimablue/projects/kangrok-ui/.shadow-cljs/builds/node/dev/out/cljs-runtime/shadow.umd_helper.js:4:114)

(found it)

and what is in /home/zimablue/projects/kangrok-ui/.shadow-cljs/builds/node/dev/out/cljs-runtime/shadow.umd_helper.js?

that should be an extremely simple file. I don't see how this could possible generate a stackoverflow?

oh are you maybe trying to setup some :exports that exports itself?

like setup npm packages in a way where (:require ["something"]) would be referring to itself?

that's not what I was trying to do, I was just trying to make a cljs with exports, the reason this all gets funky is that there's a stack of typescript depending on clojurescript depending on typescript

which is why I was trying to use "yarn link" in the first place, to eliminate some shell scripting parts of the build

if you want deep integration use :npm-module

:node-library is really meant to create a standalone actual node library

if you setup circular stuff then there is nothing to prevent that

Stumbled upon https://github.com/funcool/promesa/issues/86 and decided to investigate for a bit. Could reproduce it only with shadow-cljs (at least on 2.16.12). This is enough to trigger the error:

(defprotocol P
  (a [_]))

(a (throw ""))

------ WARNING #1 - :undeclared-var --------------------------------------------
 File: /home/p-himik/tmp/cljs-compiler-bug/src/a/b.cljs:6:1
--------------------------------------------------------------------------------
   3 | (defprotocol P
   4 |   (a [_]))
   5 | 
   6 | (a (throw ""))
-------^------------------------------------------------------------------------
 Use of undeclared Var a.b/ignore
--------------------------------------------------------------------------------

teh fuck is that? 😛

why would the symbol ignore be in that set?

I don't have a clue where that ignore is coming from?

can you share the repro? I'm curious

I’m getting an error running npx shadow-cljs release app

The required JS dependency "buffer" is not available, it was required by "node_modules/amplitude-js/amplitude.umd.js".

Dependency Trace:
	viderahealth/events/common_test.cljs
	viderahealth/events/common.cljs
	viderahealth/amplitude.cljs
	node_modules/amplitude-js/amplitude.umd.js

Searched for npm packages in:
	/Users/mitchellharris/src/patient-fe/node_modules

See: 

npm install buffer? it should already be installed but I guess its not?

should I expect using a string with a absolute path in a :require (edited) to work? Assert failed: (symbol? sym)

@skelter in shadow-cljs yes. everywhere else no. also assuming by absolute path you mean this https://shadow-cljs.github.io/docs/UsersGuide.html#classpath-js

Hi there, I'm attempting to do some code splitting, but it seems like the loader is trying to load a module that I didn't specify. I have a configuration and source files similar to the below:

;; shadow-cljs.edn
{:builds {:client {:target     :browser
                   :module-loader true
                   :modules    {:client {:entries [my-app.client]}
                                :room {:entries [my-app.components.room]
                                       :depends-on #{:client}}}}}}

;; my-app.client
(require-lazy '[my-app.components.room :refer [Room])

what's the best way of feeding custom options (declared in shadow-cljs.edn) into the app, that can be read using cljs.env - http://github.com/clojure/clojurescript/blob/master/src/main/clojure/cljs/env.cljc

@rahx1t namespace names don't matter to modules, so no there is no such thing as a parent components module. I don't know what require-lazy is though? if that is emitting a module load for components then that is out of shadow-cljs control

@ag I don't know what you mean by that. if you are building a self-hosted build then there is no way to feed anything from shadow-cljs.edn into that. what are you trying to get there?