Hi! Has anyone used weavejester/impi with shadow-cljs? I’m a little lost about the setup of pixi.js

Also something I’m confused about but maybe not related to shadowcljs: impi depends on [weavejester/pixi "4.2.3-0"], which I think should be from cljsjs, but why it’s a separate package in clojars? I mean, there’s already a cljsjs/pixi on clojars, then why do we need another weavejester/pixi?

maybe @weavejester would know? ☝️

Ah I found out how to!

@markx https://shadow-cljs.github.io/docs/UsersGuide.html#cljsjs

Is there a way to get shadow-cljs to only update dependencies and not run anything?

shadow-cljs classpath should do the trick in newer versions

How new? 😃

2.8.53+

Haha, I had 52. Thanks! Will try now.

Awesome. Seems to be exactly what I needed.

Hello! Is it possible to generate a NPM library with exports with shadow?

https://shadow-cljs.github.io/docs/UsersGuide.html#target-node-library

I’m having a strange issue where I get Unresolved var p/alet (https://github.com/funcool/promesa/blob/3.0.0/src/promesa/core.cljc) in one build but in another build where I’m also using that macro there is no warning.

maybe a different promesa version?

😅 indeed …. wrong branch, that didn’t have the newest version

@thheller any idea why cljs.nodejs.require = require; would appear in a compiled file when the target is :karma?

nm i figured it out

thats the cljs.nodejs ns