Clojurians Log v2

Hi! Is there any documentation / articles about usage of :js-options {:babel-preset-config { ... }}? I'm trying to enable polyfills for IE11.

this only affects npm packages that are actually transpiled by babel. which is only a very small percentage. so much so that this option is mostly useless.

what kind of polyfills is it not detecting already? this is usually controlled by setting :compiler-options {:output-feature-set :es5} (which is the default)

you can try :es3

Oh, I see. Looks like I should be using :compiler-options, instead of :babel-preset-config, because my project probably don't have such npm packages. Thanks for your answer, I'll try it.

also note that watch/compile builds may not work in IE11 regardless of polyfill status

best to test that with release only

Got it, thanks!

Hello, everyone! I'm having a go at spinning up a Lambda function with Clojurescript via Shadow CLJS, and I'm running into a strange error that returns three results via Google. 🙂

$ yarn run shadow-cljs compile lambda --verbose
shadow-cljs - config: /home/jcf/code/example/shadow-cljs.edn
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
[:lambda] Compiling ...
-> build target: :node-library stage: :configure
<- build target: :node-library stage: :configure (3 ms)
-> Resolving Module: :main

The required namespace "example.lambda" is not available, it was required by "shadow/umd_helper.cljs".

{:builds
 {:lambda
  {:deps             {:aliases [:lambda]}
   :output-to        "amplify/backend/function/example/src/index.js"
   :target           :node-library
   :exports          {:handler example.lambda/handler}
   :devtools         {:enabled false}
   :compiler-options {:infer-externs :auto
                      :source-map    true}}}}

In my deps.edn I have an alias that sets :paths ["src"]…

If anyone has a working example of generating a :node-library that I can package up with ncc I'd be extremely grateful.

Definitely scratching my head on this one. :thinking_face:

https://github.com/thheller/shadow-cljs/issues/418

https://github.com/vercel/ncc

Relevant links above, with two archived Slack convos coming right up…

https://clojurians-log.clojureverse.org/shadow-cljs/2018-06-26

https://clojurians-log.clojureverse.org/clojurescript/2020-09-04

I think tomorrow I might create a little repo to see if I can reproduce outside of my codebase. If so, I can open a decent issue on GitHub.

Hello, for my information, why do you build a "node-library" and not a "node-script" or "esm" (https://clojureverse.org/t/generating-es-modules-browser-deno/6116)? Moreover, shadow-cljs will generate one js file: why do you need ncc for?

@mandimby.raveloarinja see this GitHub issue and its conclusion: https://github.com/thheller/shadow-cljs/issues/290#issuecomment-539087352

@jcf the file is supposed to be /home/jcf/code/example/src/example/lambda.cljs. make sure it actually exists. the :deps inside :builds is incorrect. it is supposed to be at the top level

can't see your :paths though

assuming :paths ["src"] in deps.edn is set correctly

indeed I just did a small test. The target "node-lib" needs the node_modules to be bundled with the js; The target "esm" bundles everything in one js natively. However, the version of node on lambda is node 12 that does not support esm without the flag "--experimental-modules" (http://2ality.com/2019/04/nodejs-esm-impl.html#using-es-modules-on-nodejs)

I wasn’t sure if :deps could be nested. I want to use different dependencies for different builds, and went for :aliases…

I think I’ve done all of the above, but will double check after a good night’s rest. Thanks, thheller. 🙇

this is not supported and also usually quite useless. see https://code.thheller.com/blog/shadow-cljs/2018/02/08/problem-solved-source-paths.html

Is that post related to isolating dependencies declared using tools.deps’ :deps or is it to do with source paths (e.g. src/cljs)? I was trying to include a different set of third-party dependencies (my Lambda doesn’t need Rum) and have all my Clojure-like source collocated.

I’ll have a proper read in the morning to make sure I’m understanding it. Thanks, thheller! You’re work as always is appreciated. 🙇

Is there an issue with shadow and macros, perhaps in the context of .cljc? I define…

(defmacro deftags [& tags]
  `(do ~@(for [tag tags]
           `(deftag ~tag))))

(ns mxweb.tag
  (:require
    [mxweb.gen :as gen]))

(gen/deftags a abbr acronym ...etc..)

------ WARNING #1 - :undeclared-var --------------------------------------------
 Resource: mxweb/tag.cljc:5:2
 Use of undeclared Var mxweb.gen/deftags