Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2023-06-22

Channels

#shadow-cljs
<
2023-06-22
>
Nim Sadeh00:06:16

hello, is there a way to find and kill orphaned process (short of restarting the machine)? I keep getting ExceptionInfo: already started when trying to jack-in on VSCode.

Nim Sadeh00:06:07

Also I get the following error trying to connect to the REPL: 

The nREPL server does not support cider-nrepl `info` op, which indicates troubles ahead. You need to start the REPL with cider-nrepl dependencies met.

Ben Lieberman01:06:57

This is something you can ignore as far as I know. I get it in Calva which I suppose you are using. No issues with it so far.

Nim Sadeh01:06:43

Thanks! It actually wasn't working for a while and I had to restart the :app process

Ben Lieberman01:06:02

Hmm, I've never had it interfere with a watch before. Might be worth checking in with the Calva maintainers about, I think this is originating there.

Ben Lieberman01:06:11

The default jack-in sequence for shadow on Calva should bring in the necessary deps. Do you start the watch manually or do you use the built-in one?

Nim Sadeh01:06:24

The built in one. I just ran npm start then connected on Calva

Nim Sadeh01:06:32

But it must have been a fluke, it's working now

2
Dmitri Akatov17:06:55

Hello, when following https://shadow-cljs.github.io/docs/UsersGuide.html#_access_cljs_from_js, I only seem to have success when the imported cljs namespace has no dashes: For instance, the following setup src/my_namespace.cljs 

(ns my-namespace)
and src/user.js 
import myNamespace from "goog:my_namespace";
and src/core.cljs 
(ns core (:require ["/user"]))
gives me the following error when running the shadow compiler: 
The required namespace "my_namespace" is not available, it was required by "user.js".
However, if I replace my-namespace with mynamespace and rename the cljs file accordingly, everything works just fine. Am I missing something here?

Dmitri Akatov20:06:56

As a workaround, I created a namespaces without dashes that I use to “proxy” to any definitions from other namespace(s) (with dashes) that may be required by my JS file.