I recently removed project.clj and starting using only shadow-cljs.edn for my project. Since then, whenever I create a new test deftest I need to delete .shadow-cljs and restart shadow-cljs otherwise my new test is not detected. Any idea what's up with that? I'm using karma for my tests.

Is npm/node strictly needed to start a shadow build?

(Trying to run a release build on a CI server, would like to not install node just to kick-start shadow-cljs if it’s avoidable)

Though I guess I have to do npm install anyway right? So probably never mind 🙂

@orestis if you don't have any JS deps you can get away without node/npm. otherwise you'll need it

@caleb.macdonaldblack that sounds odd and I doubt that you really actually need to delete the .shadow-cljs folder and for the record DON'T delete the folder

otherwise its impossible to track down what was wrong

if I could make the folder undeleteable I would

if you walk me through what you are doing I can maybe help?

@thheller I really liked your post "What shadow-cljs is and isn't" 🙂. I think it would be good for newcomers and users a post about shadow cljs & figwheel. The latter is well known for clojurescript development but it might confuses people when choosing tools & solutions

@romain yeah I've been meaning to write a post like that but I have never used figwheel myself so I don't feel qualified to talk about it 😛

I'm planning to write a couple more posts on that front though, just busy with other stuff currently

@thheller Haha ok 🙂. When I wanted to do cljs after a long period, I saw shadow-cljs but I was wondering "eeh what about my figwheel? I don't understand how it will plug into" whereas shadow is a different entry in cljs world

well yeah the next post I sort of started writing is "hot-reload in shadow-cljs"

that'll certainly contain a section comparing to figwheel

and hopefully make it clear that hot-reload is possible without figwheel 😉

I should dive into shadow someday ^^'

Does anyone know what X Compilation failed. means, in regards to an imported npm project (`@ionic/react`)?

depends on the rest of the error?

it's followed by errors in file: /Users/robin/Code/my-project/node_modules/@ionic/core/dist/esm/es5/ionic.core.js

I think thats using dynamic import which is not currently supported

ahaaa, yes - I believe it does.

are there any known workarounds?

I guess you have to use webpack

Ok! Thanks for the quick response, and for your work on shadow-cljs :thumbsup: !

hi, I;m running into an issue with the “fannypack” react lib.

[:main] Build failure:
The required JS dependency "reakit/styled" is not available, it was required by "node_modules/fannypack/lib/styled/index.js".

Searched in:/Users/erichkoliphant/Dropbox/projects/fannypack-app/node_modules

You probably need to run:
  npm install reakit/styled
...
; the call in in the index.js file that's causing the issue

Object.defineProperty(exports, '__esModule', { value: true });

function _interopDefault (ex) { return (ex && (typeof ex === 'object') && 'default' in ex) ? ex['default'] : ex; }

var selector = require('./selector.js');
var space = require('./space.js');
var styled = require('reakit/styled');

@eoliphant I don't understand? thats a normal commonjs require. nothing special about it? do you have reakit installed? and made sure its the correct version?

yeah, after you walked through a few issues, with some other libs, I was looking for some of the more common things that pop up. But that “looks” ok. Yeah, reakit is installed, so I dunno, if there’s somethign else that’s hinky with their packaging, and I can do say ["reakit" :refer (styled)] in my code with no problem

check node_modules/reakit/package.json version and see if that matches the version fannypack expects

I'm guessing it doesn't

["reakit" :refer (styled)] is not require("reakit/styled"). it would be ["reakit/styled" :as styled]

ah right.. will check it out

quick question, is it possible to work with "local" jars with shadow-cljs

I am splitting some work between two projects, and am publishing to clojars, but want to develop locally

on the libs

if you mean :local/root then you need deps.edn for that

let me search for this in the docs

I believe that will do the trick, thanks @thheller!

I placed a deps.edn in my project root, and restarted the shadow-cljs process, it seems to still point to my .m2 directory. Doing something wrong? I have also defined the lib in de :dependencies section.

[io.monetashi/yesod "0.1.1"] in :dependencies

`{:deps {io.monetashi.yesod {:local/root "~/Sites/clojure/libs/io.monetashi.yesod"}}}` in deps.edn

@deplect if you have :deps in your shadow-cljs.edn config then :dependencies and :source-paths in shadow-cljs.edn have no effect

if you just add a deps.edn that will have no effect. you need to tell shadow-cljs to actually use it.

so either :deps true or :deps {:aliases [:cljs]} or so if you want to use a deps.edn profile.

ok, thank you again