I'm haveing diffuculty connecting to a node based nrepl in cider

shadow.user> (shadow.cljs.devtools.api/watch :node)
:already-watching
shadow.user> (shadow.cljs.devtools.api/nrepl-select :node)
To quit, type: :cljs/quit
[:selected :node]
cljs.user> :a
No application has connected to the REPL server. Make sure your JS environment has loaded your compiled ClojureScript code.
cljs.user> (shadow.cljs.devtools.api/nrepl-select :node)
No application has connected to the REPL server. Make sure your JS environment has loaded your compiled ClojureScript code.
cljs.user> 

@hlolli You've only started the build. You need to run the compiled code before you can evaluate cljs. Do $ node <your-build.js> and then try evaling again.

@oscar boom thanks!

amazing how fast things change, this is not how I did things in the old days (6-8 weeks ago) 😛

There is also a node-repl command directly

@richiardiandrea of course, and that's how I did things in "the old days". That brain cell must have gotten erased on some berlin dancefloor.

Ah ah ok ;)

Yeah well I have to say that I prefer to work at the REPL too and have a shadow server always on

yeh, for a website that I did recently, I got into this rythm, so the environment is the browser when it's opened, so this all makes sense.

@hlolli do you have completions in emacs + shadow? I think I see them intermittently

yes, at a quick glance, company-mode is doing its job correctly

Cool thanks so I will try to check if my config is broken somehow

 * I have this symbols instead of * for required fields in material ui

I found this https://github.com/mui-org/material-ui/issues/10494

Is it possible to solve it in some way in shadow-cljs?

Not sure what is the right solution here

@kwladyka you probably just need to set the correct charset for your html <meta charset="utf-8">

Has anyone figured out how to get cider to run (shadow.cljs.devtools.api/repl :app) after connecting?

I’m doing it manually now

@thheller how do you suggest including dependencies from private maven repos? Currently, I use lein and an s3 wagon to handle it, but hoping to move off of lein entirely

@colindresj I have never used a private maven repo so I don't know what setup is involved. if it just requires a :repository entry you can do that in shadow-cljs.edn just like lein

So something like:

:repositories
 [["private-maven"
   {:url "",
    :snapshots false,
    :sign-releases false,
    :username :env/aws_access_key_id,
    :password :env/aws_secret_access_key}]]

I get a shadow-cljs - dependency update failed - Vector arg to map conj must be a pair with that

I think that should be a map

{"private-maven" {...}}

Oh ok

dunno about the :env/ stuff. that might be something lein does?

Yeah that’s for reading env variables

:username #shadow/env "aws_access_key_id"

Ah cool didn’t know there was a reader tag for env vars with shadow

That’s sweet

Do I have to specify maven central and clojars in the repositories map as well, or will shadow merge my map with defaults?

will be merged

https://github.com/thheller/shadow-cljs/blob/master/packages/shadow-cljs-jar/src/shadow/cljs/npm/deps.clj#L36

Cool thank you

question about new :exports

I have :exports-var in my config

but I receive:

should contain keys: :exports, :exports-fn, :exports-sym

|          key | spec |
|--------------+------|
|     :exports |  nil |
|  :exports-fn |  nil |
| :exports-sym |  nil |

cli version: 2.3.36

I see the code has :exports-var in there, so maybe it has not been deployed yet?

oh, no I think there is a bug, let me fix it

oh yeah the spec is invalid

opened a PR

oh ... already fixed it 🙂

lol kk no problem 😉

does :output-to in a :release map?

ah yes it works

(ns material-ui.colors
  (:require ["@material-ui/core/colors/deepPurple" :default deepPurple]
            ["@material-ui/core/colors/green" :default green]
            ["@material-ui/core/colors/blue" :default blue]))

(def deepPurple deepPurple)
(def green green)
(def blue blue)

Sure I can name all colours cblue or something like that, but it would be so ugly

so the (def deepPurple deepPurple) is basically a self-reference

you can do :default mui-deepPurple

(def deepPurple mui-deepPurple)

no shortcut to list all colours and def all of them?

don't ask me ... ask the insane JS people making a file per color 😛

(def deepPurple (js->clj mui-deepPurple)) - how compiler work? Will it be count in the browser or during compile?

heh 🙂

this one too?

(def deepPurple (js->clj mui-deepPurple)) whats this supposed to do?

isn't it a string?

now I have to get value like that (aget colors/blue "A400")

ah its a JS object

well honestly I would just make a function

or maybe it is just stupid to use this colours objects hmm

I want to avoid performance waste to count all colour in the web browser

(defn color [x y] ...) so you can do (color :blue 400)

this energy could be use for cyrptocurrency instead of counting colours 😛 😉

hmm

It will work 🙂

but if js->clj in this situation will be optimised during build code it will be even better

the js->clj is at runtime

you could just take the color codes and port them to CLJS

DCE will actually remove the colors you don't use then

hmm

not sure how material-ui uses the colors internally though?

I guess they sometimes take the color object as arguments somewhere?

It can be use to make a them for example:

(def theme (mui/create-mui-theme
             (clj->js
               {:palette {:primary {:main (aget colors/blue "A400")}
                          :secondary {:main (aget colors/deepPurple "500")}}
                :overrides {:MuiAppBar {:root {
                                               ;:color "#00ff00"
                                               ;:background-color "white"
                                               }}
                            :MuiButton {:root {:text-transform "none"}}}})))

so you use it only once ever?

I wanted use it in view components also, for example to set colour of the button

then seriously just :palette {:primary {:main "#42a5f5" ...

but I start to think maybe it is stupid idea to use this objects…

https://material-ui.com/style/color/#color-palette

exactly

I can rewrite values from there instead

just I am not a graphic designer and this pallet of colours help me a little 🙂

yeah the palette is great

but just copying the colors you want seems like a much better solution that dealing with those JS objects

its not like the color blue is suddenly going to change its color code

probably you are right. This is the trap of using ready solutions. Start to turn off brain and use it 🙂

maybe I will write macro one day or something for that 🙂

is there a way to add dev folder to shadow's classpath?

:source-paths ["src" "dev"]?

if you want to replace files: no, that is not possible

yep ok, sorry should have asked better...only in dev mode, not for :release

will need to drop to deps.edn or lein for that

I consider it a horrible anti-pattern so I won't add support for that

you can do it fine via lein or deps.edn though

@thheller so my next q. would be, is there :aliases in :release

I see it global only

yes classpath applies globally

shadow-cljs -A:release --force-spawn release your-app

so if it is an antipattern, maybe I can ask if there a better way to do the following 😄

I have the classic my-org.dev namespace that uses the dotenv library to load environment variables only when using the REPL

I don't wont to use it in :release, so I added:

(when goog.DEBUG
  (dev/load-env-vars!))

but I see that I have to require it...which indeed feels like an anti-pattern

it is kind of a :preload

dev stuff you can easily load via :preloads

yeah maybe I should do that

I should really write down my recommended way to inject "runtime" config

definitely

browser app?

no, node server app

ah thats probably the easier solution of them all

(defn main [config-path] (let [config (-> (fs/readFileSync config-path) str (reader/read-string))] ...))

I use env vars, I just need to load them from somewhere

yeah...i do something similar

then call with node server.js dev-config.edn

or node server.js prod-config.edn ...

we prefer env vars here 😄

no nasty env vars in your compiler output

but I see your point

but with node you can easily access env vars? why include them at compile time?

yes I can, I just need to load them at runtime for REPL dev

I think :preloads is fine

but the dev folder will need to always be on the classpath

I don't understand, why do you need to load them at runtime for REPL dev?

because I need them for running 😄

like DB connection and all that

assuming you are using :target :node-script?

at the moment it is :node-library

same thing ... you are starting the node process do you not?

or are you using (shadow/node-repl)?

I am starting it with node-repl

or similar thing 😄

so would (shadow/node-repl {:node-env {"hello" "world"}}) help? (adding extra env vars to the node process so js/process.env.hello works?

something like that would definitely help...but dotenv is kind of nice because it automagically reads from .env the variables

(shadow/node-repl {:node-env (read-from-dotenv)})?

never heard of dotenv

ah ah 😄

yeah I mean it's a JS thing right?

I don't know? what is it?

https://github.com/rentpath/clj-dotenv has a big fat [DEPRECATED]?

uhm

probably shadow should have its own way of loading vars and I can use that instead, I can drop dotenv actually. it could be env.edn or something

I'm still trying to understand what problem you are actually trying to solve though

ok so

I still have no idea what the actual problem is

my server has to connect to the db

at runtime in production, env vars will be set for it

at runtime in the repl, I need a way to load env vars

so your code uses something like js/process.env.DB?

yep

we don't like config files here for now 😄

don't ask me why 😉

you do ... they are just config files for bash or something like that

gotta be written down somewhere 😉

ok assuming that dotenv is just a npm lib I think :preloads is the best option

yeah, so again the problem would be that that code should not leak to production

that is why normal clj/cljs you would use an clj alias

:preloads are never included in release builds?

oh cool

and i guess the namespace will be trimmed

if not required

if its not required anywhere (besides :preloads) then it won't even be compiled in release

awesome

{:target :node-library :exports .... :devtools {:preloads [my-org.dev]}}

perfect sorry if it took so long 😉

https://code.thheller.com/blog/shadow-cljs/2018/02/08/problem-solved-source-paths.html

I understand why you want to use separate :source-paths in CLJS usually

but that is not an issue in shadow-cljs since it won't just randomly include stuff just because its on the classpath

oh that's exactly what I need 😄

no random mess

Other q. 😄 I connected to a REPL with nrepl-select in emacs, and I have a server in another window that compiles. Is there a way to stop receiving the compilation logs in the nrepl-select-ed buffer?

well the watch messages appear wherever the watch was started

nrepl-select has nothing to do with those messages

I think cider is just setup to always do watch+select

No I am doing it manually

I have a watch in the terminal

Then I connected with a nrepl-select

The messages are visible in the buffer in emacs

So you are saying it is not expected?

which messages are we talking about?

it is not expected to get random messages no?

I receive watch messages in my buffer

please give me an example of a message you get

Watch was started in a terminal

there are a gazillion messages, no idea what you mean by watch messages

Oh ok right so compilation warnings

please just paste one example 😛

Kk I was afk let me go and do it

user> (do (require '[shadow.cljs.devtools.api :as shadow]) (shadow/watch :init-store)(shadow/nrepl-select :init-store))
To quit, type: :cljs/quit
[:selected :init-store]
JS runtime disconnected.
JS runtime connected.
JS runtime disconnected.
JS runtime connected.
JS runtime disconnected.
JS runtime connected.
[:init-store] Compiling ...
[:init-store] Build failure:
------ ERROR -------------------------------------------------------------------
 File: /home/arichiardi/git/laputa/lambda-cqrs/src/ep_cloud/init_store.cljs:23:3
--------------------------------------------------------------------------------
  20 | 
  21 |   This function is idempotent, you can call it multiple times."
  22 |   [ctx request]
  23 |   (let [azure-callback
---------^----------------------------------------------------------------------
Call to cljs.core/let did not conform to spec
-- Spec failed --------------------

  ([... ... (partial ... ...) ... ... ... ...] ... ...)
             ^^^^^^^

should satisfy

  vector?
...

I very clearly see a (shadow/watch :init-store) there?

Oh crap lol

I was sure I did not use it :(

Sorry for the noise ;)

so is there a "watch test" mode in shadow by any chance?

I have a problem cause the tests are there but it does not seem to pick them up