@mel.collins I removed the forced override in master. will probably make a release later.

I’ve got my build into a state where whenever I restart it, I get a message: server pid exists but server appears to be dead, proceeding without server, and then my build hangs when compiling. Is there an easy way to just reset everything and force a clean build?

@cfleming unlikely that fixes anything but you can delete .shadow-cljs/builds. does it actually hang completely? does it max out cpu?

I've had weird reports of "hangs" when using incompatible core.async versions? did you maybe change versions?

No, I’m not using core.async (well, some of the machinery via promesa, but not directly)

check for dependency conflicts in case you are using project.clj/deps.edn

Ok, I’ll do that. I’m using a project.clj but perhaps I should just switch to a pom.

or maybe a macro going wild 😛

doesn't really matter what you use if its not shadow-cljs.edn

Deleting that didn’t seem to help.

Where does it find the pid? Can I delete that?

since only shadow-cljs.edn can somewhat ensure you get the correct deps

pid doesn't matter. it is just telling you that the server probably did shut down cleanly

.shadow-cljs/server.pid but that doesn't mean anything

So I should implement direct shadow importing, is what you’re saying 😛

Ok, I’ll look - I don’t think I’ve changed anything along those lines.

hehe. its fine to use the others. just need to ensure you get the correct deps manually and dependency issues are the most common problem people run into

since we must get the correct mix of dependencies or things break 😞

https://shadow-cljs.github.io/docs/UsersGuide.html#failed-to-load

usually they fail on start, sometimes they fail in weirder ways 😞

also shadow-cljs compile app --verbose might help

see where it gets stuck

If someone is using shadow-cljs + deps, what's the normal way to package something as a library?

I see the docs regarding leiningen ...

Trying to use something like depstar results in a jar that's 34mb. Heh.

what's in the jar?

Everything you can imagine of every kind of dependency. It's just an uberjar. So it has compiled clj .class files etc.

I assume there must be common ways people do this stuff, but this deployment piece of the deps ecosystem sucks a little bit.

Maybe I'm answering the wrong question - I have the impression that the cljs library should just literally contain the .cljs files (or .cljc) as well as its dependency info.

Ya, like if you're packaging your cljs/cljc files for other shadow-cljs projects to use. I've been using pack.pack-alpha for that

;; jar creation from juxt
  :pack {:extra-deps {pack/pack.alpha {:git/url ""
                                       :sha "d9023b24c3d589ba6ebc66c5a25c0826ed28ead5"}}
         :main-opts ["-m" "mach.pack.alpha.skinny" "--no-libs" "--project-path" "api-cljs.jar"]}

(but this is not an uberjar)

and possibly you can share your .cljs/cljc files via :git/url and not use a jar at all.

@slimslenderslacks Thank you - I just happened to run across a cljs library packaged just like that. Awesome!

Ya, it's quite nice when you first realize that you might not need a jar at all - strange feeling

Yeah that is blowing my mind a little bit. I still can't quite wrap my head around it.

What exactly does --no-libs do?

I wonder what I'm doing wrong. Pack worked perfectly fine (I think) but when I run shadow-cljs and depend on these things directly (whereas before I was using them as local artifacts) I get a bunch of provide conflicts.

So I think the problem was, pack was including my old js build products. However, when I clean those up and make a new minimal jar, shadow-cljs can't find the classes in it, or says effectively "required namespace x.y.z is not available".

So something about how I'm packaging it with pack is wrong for shadow-cljs.

@pmooser I don't know anything about pack or anything deps.edn packaging related for that matter. I just use lein since it is by far the easiest and straightforward.

you .jar file should only contain the relevant sources. you can check via jar -tvf your.jar whats in it.

Yes, I understand, I don't use lein anymore, but what I'm a little more interested in is, how would you debug the issue of shadow-cljs saying something isn't available? I can unpack the jar and look in it ... what does shadow-cljs expect to see, for just a normal cljs library? What directory layout?

Yeah, my namespace hierarchy is basically foo.bar.baz/file.cljs and if unpack the jar, I see directories foo/bar/baz/file.cljs ...

I'm just not sure if there's something else or another level of structure that shadow-cljs expects to see, or what.

please give concrete examples ... the filename must match the ns ... that is it. like any other clojure(script) lib or tool. nothing special regarding shadow-cljs.

foo.bar.baz/file.cljs is not valid so please don't add confusing examples.

Hold on, let me find "real" names and replace proprietary components.

The error is like:

The required namespace "jett.hyperbase.client" is not available, it was required by "jett/hypercell/actions.cljs".

And if I unpack the jar of the library, it looks like:

so there should be a jett/hyberbase/clients.cljs in the jar

please use jar -tvf. I don't care about the unpacked result.

(yes, it's there)

nothing ever unpacks the .jar during compilation

0 Wed Jul 08 18:49:46 CEST 2020 jett/hyperbase/
     0 Wed Jul 08 18:49:46 CEST 2020 jett/
 11489 Fri Jun 26 00:13:24 CEST 2020 jett/hyperbase/core.clj
   484 Mon May 04 11:56:40 CEST 2020 jett/hyperbase/transit.clj
   378 Mon May 18 19:47:00 CEST 2020 dev.clj
  5419 Fri Jun 05 11:57:08 CEST 2020 jett/hyperbase/order_util.cljc
  6375 Tue Jun 02 09:44:34 CEST 2020 jett/hyperbase/id_util.cljc
     0 Wed Jul 08 18:49:46 CEST 2020 jett/gavel/
  1612 Fri May 08 13:05:20 CEST 2020 jett/gavel/core.cljs
  5526 Thu Jun 11 13:06:34 CEST 2020 jett/gavel/message_center.cljs
 10888 Mon Jun 08 19:26:02 CEST 2020 jett/hyperbase/sample_application.cljs
   549 Mon Apr 20 10:26:56 CEST 2020 jett/hyperbase/diff.cljs
   403 Mon Jun 08 19:25:30 CEST 2020 jett/hyperbase/util.cljs
 21608 Mon Jul 06 15:47:08 CEST 2020 jett/hyperbase/itom.cljs
 16470 Fri Jun 26 14:36:42 CEST 2020 jett/hyperbase/client.cljs
   979 Wed Jun 17 12:20:18 CEST 2020 jett/hyperbase/ui.cljs
  5338 Tue Jun 09 13:00:06 CEST 2020 jett/hyperbase/core.cljs
   576 Wed May 13 12:14:12 CEST 2020 jett/hyperbase/user.cljs
     0 Wed Jul 08 18:49:46 CEST 2020 web/
   240 Tue Apr 07 17:34:08 CEST 2020 web/index.html
     0 Wed Jul 08 18:49:46 CEST 2020 web/css/
  7313 Mon May 18 12:06:08 CEST 2020 web/css/site.css

ok the dev.clj and web/ files probably shouldn't be in there but otherwise the file seems to be present?

Yes, I knew the web and dev things aren't useful but I couldn't figure out how they would be harmful.

and that jar is part of your dependencies?

I mean it needs to be on the classpath to be found?

Yes, the jar is in my deps.edn.

and you restarted shadow after adding it?

Yes, several times.

I can depend on this stuff if I use local coordinates or git coordinates (in deps)

It's just something about I'm packaging the library that must be messed up.

In any case, it sounds like from your point of view, it looks correctly structured, so I'm not sure we should take more of your time trying to figure it out.

try shadow-cljs clj-repl and ( "jett/hyperbase/client.cljs")

if thats not nil maybe the file is corrupted in some way?

Ok, let me try.

try (slurp *1) and see if there are some funky chars in the beginning.

It returns nil. So presumably it doesn't find it.

yeah but thats not shadow-cljs trying to find it. thats the JVM. so something is wrong with either your dependency on being on the classpath or the .jar itself

Ok, I'm sure it's the jar. I'll take a look. Thank you for your help!

if jar -tvf works that the jar seems to be valid

I don't see any manifest information in the jar, but I'm not sure what exactly is supposed to be there.

I'm not doing anything especially weird with pack, but maybe there's another argument I'm supposed to use. And to be clear, I don't care about pack. I just am trying to figure out the right way to package a cljs library using deps. We used to do this with lein trivially all the time and deploy to an internal maven server. I just can't quite figure out how to build an artifact with deps that works along with shadow-cljs.

(or probably anything else)

all I can say is ... just use lein. even if its just to bundle stuff. I cannot help you with anything deps.edn related since I have not used anything.

shadow-cljs requires absolutely nothing special from the bundling and is not involved in it in any way

Sure, maybe I will go that route. Thank you again.

whatever you are doing is also wrong with any other tool. it has nothing to do with shadow-cljs.

For packaging a library, there aren't even supposed to be any build products from shadow-cljs or anything in it right?

libraries just have cljs files in it, no compiled artifacts

for my libs, I do use lein just for that. I would reach out to whatever deps.edn script you’re using if you want help with releasing a CLJS lib

Ok, thanks.