Can somebody provide me with example how can I create simple node-script project and start repl sesstion so that I can connect from nvim to it?

npx create-cljs-project foo then cd foo npx shadow-cljs node-repl

dunno about nvim though

Yes that’s exactly what I did

when I try to execute some form in nvim i get Fireplace: no default ClojureScript REPL

I tried to call :Piggieback :app but no results

did you connect to the shadow-cljs server?

via :Connect

?

yes

no clue. I have never used vim-fireplace

If you are starting nREPL some other way, run :FireplaceConnect host:port.

yes

it is connected to nrepl

dunno. if you used shadow-cljs node-repl you'd do :Piggieback :node-repl

Tried that too, doesn’t work, can’t execute anything from within the nvim

Do I need to add what ever special to config, like dependency, ports, whatever. Or should it work just out of the box ?

depends. how did you connect? do you use lein/deps.edn?

I created project using npx create-cljs-project hello-node

created one cljs file

and how did you connect? the default random port printed on startup?

yes it is connected for sure

I did manually typed host:port

I don't know. if I look at this error you might not have provided enough args? https://github.com/tpope/vim-fireplace/blob/master/autoload/fireplace.vim#L512

maybe try :Piggieback (cider.piggieback/cljs-repl :node-repl)?

can't quite decipher what the vim script is doing

Ok I started shadow-cljs node-repl, Connected, Runned Piggieback :node-repl and tried to run Eval (+ 1 1) and got Fireplace: session closed

The same with :Piggieback (cider.piggieback/cljs-repl :node-repl)

no clue what that means

I don’t see nvim section in Editor Section in docs, maybe it is not supposed to work at all

several people use it and it is definitely supported

I just don't know anything about it so I can't add it to the docs

I definitely connected to nrepl, I can execute clj, but not cljs

no clue how to debug the fireplace side sorry. does it have a log of some kind?

ok, finally

CljEval (shadow/repl :node-repl)

And it works now

🚀

weird because thats what :Piggieback :node-repl should end up calling

i love and hate clj so much 🤯

I loaded successfully BlueprintJS with shadowjs. Works at many cases, maybe my poor react knowledge.. could you help me what I forget or how to rewrite to cljs? https://blueprintjs.com/docs/#core/components/popover.dark-theme

(defn PopOver []
 [:> bp/Popover {:content  [:div 
                            [:> bp/Menu {:large false}
                             [:> bp/MenuItem {:text "test1"}]
                             [:> bp/MenuItem {:text "test2"}]
                             [:> bp/MenuItem {:text "Test3"}]]]
                 :enforceFocus false
                 ;:position "Position.BOTTOM_LEFT" ;;error
                 :interactionKind "HOVER"}
  [:> Button {:variant "info"}  "hello"]]
)

original code https://github.com/palantir/blueprint/blob/develop/packages/docs-app/src/examples/core-examples/popoverInteractionKindExample.tsx

:content expects a react element but you are passing a cljs vector

do a (reagent/as-element [:div ...])

@thheller thanks!!

:position bp/Position.BOTTOM_LEFT

thanks!!

Works fine, thank you very much 🍻

I'm new to ClojureScript and trying to get my head around how the front-end is set up. We're using ClojureScript, shadow-cljs, Leiningen and Reagent. I am just a bit confused about the dependencies around React. We're using Leiningen for our dependencies and have Reagent and shadow-cljs as dependencies. Do I still need to require React in the package.json file?

yes

JS dependencies are manage by package.json and npm yes

Ok, so in layman terms, there is one version of React used in the app and it's required in one place, package.json

"required" isn't the word I would use, it is only installed based on package.json

what is used in the build is defined by your code

you can have thousands of things in package.json but that wouldn't mean they are actually included in a build

We have some :exclusions in the project.clj file - cljsjs/react etc - I think it's the cljsjs part I don't understand - basically how it's all connected. I come from React/Vue background and am used to just having one package listed

(closure compiler is 👍 about dead code elimination)

those exclusions don't really do much so you can remove them or keep them

shadow-cljs doesn't use them regardless

package.json managed JS dependencies, project.clj managed CLJ/CLJS dependencies

Ok. So if we didn't use shadow-cljs (for example) and just reagent - where would that be pulling React from?

cljsjs

Ok, I thought shadow-cljs replaced cljsjs

it does. but you asked about what happens if you didn't use it

So we can run just Reagent and shadow-cljsjs - I think I was getting confused as we run

[thheller/shadow-cljs "2.8.52"]
                 [thheller/shadow-cljsjs "0.0.20"]

[thheller/shadow-cljsjs "0.0.20"] this you don't include at all

cljsjs is npm packages pre-packed as MAVEN dependencies

CLJS uses maven by default

shadow-cljs skips cljsjs and accesses npm directly

Ok great. So ideal basic setup would be

[reagent "0.9.0-rc1"]
     [thheller/shadow-cljs "2.8.52"]

"dependencies": {
        "react": "^16.9.0",
        "react-dom": "^16.9.0",
    }

yes

Perfect

Then I can remove all the :exclusions for cljsjs

shadow-cljsjs is about providing compatibility with packages that assume you don't have direct access to npm. described here https://shadow-cljs.github.io/docs/UsersGuide.html#cljsjs

shadow-cljs brings that in by default, you never need it manually

basically don't worry about those at all unless you run into specific problems

you can keep the exclusions or remove them. shadow-cljs doesn't care

if you keep them the dependencies won't be downloaded

Cool. So how does having reagent in lein then access the packages in json - is that what shadow-cljs is taking care of?

if you don't they are only downloaded once and then cached so no big overhead at all

yes

Sorry, my last question, in the documents say it's recommended to run shadow-cljs as a standalone NPM version - but it doesn't say why that is recommended?

more streamlined setup for CLJS

lein is built for clojure and does a lot of stuff CLJS doesn't need

but if you need lein for other reasons that is totally fine

So would be advisable to remove from lein and add to package.json?

We have a lot of stuff in lein - I'm just trying to strip down the front end as it's a bit of a mess

uhm no thats not how that works

you declare CLJS dependencies in project.clj

but you can also declare them in shadow-cljs.edn directly (and skip using project.clj completely)

it is only about :dependencies and :source-paths

we are still managing 2 separate package managers. there is npm for JS and maven for CLJ/CLJS

Ok, makes sense. So for a new project, probably declare it in shadow, but we have quite a few depends in lein so probably best to keep it there for the moment

one is controlled by package.json the othe other by shadow-cljs.edn or project.clj or deps.edn

shadow-cljs uses the exact same dependency resolution library as lein so moving them over would be easy

but you can keep project.clj if its working for you

Ah, OK - well better to have 2 scripts than 3!

Thank you very much for the help - a lot clearer now!

Is it possible to make shadow-cljs build a release mode in dev with hot code reload? I’m trying to investigate an issue I only see in the release mode.

no thats technically impossible

yeah i figured

whats the issue?

a component breaks my app in one particular context but not another, I’m on a beta release of fulcro, so it could very well be a bug in fulcro 3, trying to figure out what’s going wrong

this component is loosing it’s dynamically bound variables

shadow-cljs release app --debug or shadow-cljs release --pseudo-names might provide clues if you are not using that yet

yup using those, very handy

shadow-cljs check app might be useful but has a lot of false positives

so often more noise than actual help. but maybe 😉

now that i think about it, i wonder if react’s async render stuff is not compatible with the way fulcro binds dynamic vars

i’ll check thanks

if you use lazy seqs in render that can be a problem yes

in dev they are "forced" by react's validation stuff but that isn't active in release builds

so lazy seqs aren't eval'd at the correct time