Clojurians Log v2

hello all, beginner question here. How do people go about authoring styles in cljs projects? Coming from JS-land I've enjoyed preprocessors and css-in-js. I'm doing some googling, but if anyone has recommendations I'd love to hear

These are the projects that I know of, in no particular order: - https://github.com/clj-commons/cljss - https://github.com/roosta/herb - https://github.com/khmelevskii/emotion-cljs - https://github.com/dvingo/cljs-emotion - https://github.com/noprompt/garden

Thank you!

Would the feedback on how similar one set of css styles was to another on your application be useful for people? I'm thinking something that reads any styles you have and provides you with a list of "very close" results. This could be used to Prevent style drift if the styles were supposed to be the same but weren't shared data

Hey all, a bit of non-standard question here: how do you usually use an HTTP client in ClojureScript with Node.js target? ‘Clojure-http’ isn’t an option since it uses XMLHTTPRequest under the hood. Maybe someone has a decent example? Only need to make a simple POST with some qparams. 🙇

I have tried using interop and the axios library, but I get an import error:

(ns main.lambda
  (:require ["axios" :as axios]))

"Error: Cannot find module 'axios'\nRequire stack:\n- /var/task/index.js\n- /var/runtime/UserFunction.js\n- /var/runtime/index.js",

I’ve used this in my current project https://github.com/Jarzka/stylefy

Hi @thedanpetrov How do you run ClojureScript ? Shadow-CLJS, Figwheel or vanilla CLJS ?

Hey, shadow

my shadow-cljs.edn looks something like this:

{
 :lein false

 :source-paths ["src"]
 :dependencies
 []

 :builds
 {:lambda {:target :node-library
           :output-to "./dist/lambda/index.js"
           :exports {:handler main.lambda/handler}
           :compiler-options {:infer-externs :auto}
           }
  :node {:target :node-script
         :output-to "./dist/node/index.js"
         :main main.lambda/start
         :devtools {:after-load main.lambda/reload}}
  :test {:target :node-test
         :output-to "./build/test.js"}
  }}

It works for me. And your package.json file?

{
  "name": "yuno",
  "description": "",
  "version": "0.1.0",
  "private": true,
  "devDependencies": {
    "shadow-cljs": "2.10.19"
  },
  "dependencies": {
    "axios": "^0.20.0"
  },
  "scripts": {
    "build": "shadow-cljs release :lambda --debug",
    "predeploy": "npm run build",
    "deploy": "cd dist/lambda &amp;&amp; zip lambda.zip index.js &amp;&amp; aws lambda update-function-code --profile cvi-aws-admin --function-name yuno --zip-file <fileb://lambda.zip>",
    "clean": "rm -rf dist"
  }
}

I don’t think too much out of the ordinary here

Thanks. This Garden projects seems to be quite popular seeing as it's used by multiple two of these other projects

This is a very strange warning, anyone have a clue to what it means: > WARNING: The org.clojure/core.async dependency in shadow-cljs.edn was ignored. Default version is used and override is not allowed to ensure compatibility.

@cattabanks it means that you should not include core.async in dependencies for shadow-cljs

Any reason why?

https://github.com/thheller/shadow-cljs/commit/06015e1c4d5d8b0127b27abb5b7112dc0d760af6

things break badly when using an incompatible core.async version since shadow-cljs uses core.async directly itself

so core.async is always available

Got you

I made a simple repo who works perfect for me, maybe it can help: https://github.com/PrestanceDesign/cljs-node-axios