BTW, path to CSS file in link tag is absolute:

<link href="/css/main.css" rel="stylesheet preload" type="text/css"  as="style" />

looks fine. note that :watch-dir currently only applies when the watch is started. so if you made adjustments while it was running they might not be active

oh wait

it needs to be rel="stylesheet". preload should be a separate tag? didn't even know you are allowed to combine them?

Oh, thank you! Removing preload fixed it. I'd never thought this was the problem

I don't know if it is valid too. This code is older than me in the company and I don't know the reason why it is there

yeah seems kinda redundant. I mean by the time the parser finds the tag it can load the css file directly. no need to first preload it?

Decided to remove preload. Really appreciate the help! ✌️

you can have multiple builds running at the same time yes. shadow-cljs watch app1 app2 app3 same for all other commands

release will not be parallel, watch will be

I mean releases - we have 6 apps from same source, it takes 10 min to build - want to speedup it

I made the default sequential since parallel was overloading some systems

you can make your own release function and run them in parallel

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

so just a function (defn release [& args] (shadow/release! :foo) (shadow/release! :bar) ...)

that would be sequential

you can use (future (shadow/release ...)) to start it in a thread

or use a thread pool

Thank you!

Interesting! As a hack, you could use one those CRA-patching libs to add a Define plugin to webpack, with process defined with whatever you need it to be, this will at least let it compile Though I'm very curious as to why it's not already defined and what that means for the evaluation of cljs_env.js

I could probably use craco to accomplish something like that, but I assume shadow-cljs needs values that are populated in there? It looks to be defined in cljs.core.async.js:

var process = (function (p__14390){...

I agree, it's curious that it's not already defined

Yes, craco was what I was referring to. This is most certainly not at all a fix, but perhaps an unblocker to investigate or debugger further, apologize if I implied otherwise, and also apologies if this was a useless suggestion! Please do update this with anything you find, would love to know wtf is going on. Is that cljs_env.js file imported or loaded in particular way? I am not sure how it is able to depend on a global reference that is undefined at runtime. I have not personally looked at shadow's source code. However, I wonder if: 1. This has something to do closure compiler/libs bespoke module loading system interacting weirdly with cra/webpack 2. This has something to do with your setup in particular. Is the example code you've posted actually the minimum reproducible source code - ie, what you've seen this issue come up in?

I can try craco next -- I'm certainly at a wall otherwise. But no apologies needed! 🙂 I'm very happy to receive all the help I can get. I have been suspecting that the interaction with webpack is somehow to blame here.. As far as the code, the only thing I haven't shared is the results of yarn create react-app. I can put together a small minimal reproduction and commit it somewhere if it would be of interest. To answer your first question, I have been going on https://shadow-cljs.github.io/docs/UsersGuide.html#target-npm-module. In part they read: > If you use the default :output-dir of "node_modules/shadow-cljs" you can access the declared namespaces by using require("shadow-cljs/demo.foo") in JS. I'm not quite doing that, as I have import statements instead. Doing import { hello } from "shadow-cljs/app" leads to the error because the compiled app file has a require('cljs_env.js')

Frankly, I can tell I'm going about this all wrong but I'm not yet sure on how to right it

:target :npm-module by default assumes a node runtime. so add :runtime :browser to the build config. that should remove that reference to process

I tried that as well, unfortunately the reference to process is still there

I have a minimal reproduction here: https://github.com/jorge-barreto/cljs-in-cra.git The build config now reads:

;; ;; shadow-cljs configuration
{:source-paths ["src"]
 :dependencies []
 :builds {:code {:target :npm-module
                 :runtime :browser
                 :output-dir "node_modules/shadow-cljs"
                 :entries []}}}

FWIW :target :esm is probably a better choice these days regarding interop. https://clojureverse.org/t/generating-es-modules-browser-deno/6116

I'll check your repro later though

if you are integrating with CRA add :js-options {:js-provider :import} to the build config

There's no rush! I really appreciate the time. I tried adding the :js-provider to no avail. I'll try :target :esm next

:js-provider was meant for :target :esm sorry

Ok, I can confirm that :target :esm works, but only when run as shadow-cljs release . build and watch produce many build errors for webpack. I'll push soon to a branch on the repo

what kind of error?

couple thousand lines across many files, looking like this:

src/generated/cljs-runtime/cljs.core.async.impl.buffers.js
  Line 2:1:      'goog' is not defined  no-undef
  Line 3:1:      'cljs' is not defined  no-undef

hmm odd. I'll take a look if you push that to the repo

you can take a look in the target-esm-dev branch: git clone -b target-esm-dev

ugh just checked. guess webpack got a lot stricter since the last time I tested this

it doesn't recognize that these are things on globalThis and actually do exist

this looks like a linter error though. maybe that can be turned off?

the code is actually fine

yes! nice catch -- that works

i updated the repo w/ the working code. i really appreciate the help with this!

hi. I’m following along on this thread since I’m trying to embed an existing cljs app into a react container. I’m successful in releasing the app with :target :esm but I get errors when I try to import it in the react app. I’ve tried including :js-options {:js-provider :import} but the compilation process fails when I do claiming the namespace react is not available when required by reagent/core.cljs. Have any of you encountered a similar error by any chance?