Clojurians Log v2

@jaime.sangcap see the link above. seems to be picking the wrong IP too

hey I’m getting

[2021-02-03 16:09:28.301 - INFO] :shadow.build.npm/js-invalid-requires - {:resource-name "node_modules/@aws-amplify/ui-components/dist/cjs/index-e94df828.js", :requires [{:line 1632, :column 73}]}

(:require ["@aws-amplify/ui-react" :refer [AmplifyAuthenticator AmplifySignOut]]...

return Promise.resolve().then(function () {
    return _interopNamespace(require(`./${bundleId}.entry.js${ ''}`)); }).then(importedModule => {...}, consoleError);

no luck. that pattern is not supported. it is webpack specific. if you must use that lib you can follow option 2 https://code.thheller.com/blog/shadow-cljs/2020/05/08/how-about-webpack-now.html

Makes sense, thanks a lot! Maybe it’s not that easy but if you linked to that article or even put the error you get into the article so it comes up when someone Google’s it that might save you some time answering silly questions like this

But it’s been a while since I switched to shadow and this is the first speedbump I’ve ran into which is a vast improvement on other tools so thanks in general!

yeah it is rare but some libs expect you to use webpack and really aren't happy with anything else

Is there somewhere a rough description of how the watch algorithm decides what to recompile and what to read from the cache? At first I thought that it was systematically recompiling any child namespace (makes sense). But it isn't always true around the entry namespace of a module from what I see with --verbose and it puzzles me.

the namespace you changed and all namespaces that directly require it by default

also all namespaces with warnings since they are never cached

and all namespaces marked with :dev/always and all namespaces blocked for caching by :cache-blockers

So the entry namespace of my main and only module should always recompile? Because all I see is:

-> Flush: meloview/comp/root.cljs
<- Flush: meloview/comp/root.cljs (5 ms)

Oh, when you say "directly", do you imply that in A requires B which requires C, A might not recompile when C changes but B always will?

yes. the logic is that if you change C (eg. remove a def, add a def, change defn signature, etc) then B should be recompiled because it may now have warnings/errors but A cannot

Hallo. I am looking for an idea how to get a string which is generated in the browser into a specific file in my project directory. My usecase: My code is pure cljs, not cljc. I have a kind of model driven application. So inside the browser I can collect information about it's internals and generate documentation metadata. I want this documentation data into a file, as soon as compilation completes and a callback hook in the browser is called. Since shadow-cljs which runs on the filesystem already communicates with the browser, I thougt there might by a way to do the trick. Any suggestions?

I don't understand. you need some kind of server you POST the data to or so

Having something like (shadow-cljs.browser-tools/write-file "target/info.txt" "file content here") would be optimal.

shadow-cljs does not handle server code for you. you'll have to write that.

No, I need this thing to only work during development. When a shadow-cljs hook is called in the browser. I would like to be able to call some magic function from shadow-cljs which sends the data back to the shadow-cljs server which writes it to a file.

I repeat. no shadow-cljs does not handle such a case for you. you do have to write it yourself.

you may use a custom http handler from the :dev-http server

Great, that explains it all. I was under the false assumption the whole tree would recompile. Many thanks!

How does a test reporting tool do this? When the tests run in the browser, how do the results get to a file on the server? Or don't they?

they don't. at least in shadow-cljs :browser-test

@thheller thank you anyway!

@witek it may not be obvious but what you are asking is about 5 lines of code with a custom :handler. so I do not see the point in shadow-cljs providing such a thing.

I have no server in my project. It's pure JavaScript for Google Firebase.

but you have shadow-cljs running and use :dev-http? https://shadow-cljs.github.io/docs/UsersGuide.html#dev-http

You are right, thank you! I tinkered with macros for a half day. :man-facepalming:

@witek set :dev-http {3000 {:root "public" :handler my.handler/handle}} and

(ns my.handler
  (:require [shadow.http.push-state :as push-state]
            [<http://clojure.java.io|clojure.java.io> :as io]))

(defn handle [{:keys [uri] :as req}]
  (if (not= uri "/save-me")
    (push-state/handle req)
    (do (spit (io/file "somewhere" "foo.txt") (slurp (:body req)))
        {:status 201
         :body ""})))

then from the browser side just send a post request to /save-me

or something like that. didn't test the above but should be ok.

no, that gets rather slow in larger projects and isn't usually required.

Hi! Is there a way to add in my shadow-cljs.edn a "build step" to execute an external command every time I run the build? For example to run postcss input.css -o out/out.css`` . Ideally with a watch function, so it runs that command only when the input.css changes?

@elisescu see :build-hooks in the docs. fair warning though this is almost always a bad idea since it will slow down you CLJS recompile cycle

Got it. Any suggestion of how to do something like that better? Or I should leave it completely out of the shadowcljs build process? And thanks a lot for the very quick reply.

I just run things like that separately. sometimes with something like https://www.npmjs.com/package/foreman or alternatives

:thumbsup:

howdy all--i recently have been playing around with using shadow cljs to emit ecmascript modules (esm) for denojs--i'm not sure if this is a newish thing, but since deno defines a global window object, a particular line of code in the shadow.dom package is causing an error

i.e. the code defining shadow.dom/transition-supported? which looks like

shadow.dom.transition_supported_QMARK_ = (((typeof window !== 'undefined'))?goog.style.transition.isSupported():null);

you probably forgot to configure :runtime in the build config. that defaults to browser. for :deno you'll need :runtime :custom since I have not implemented hot-reload for it at all.

as mentioned here https://clojureverse.org/t/generating-es-modules-browser-deno/6116 only compile and release kinda work for now.

huzzah! thank you friend 🙂