that is currently not possible with hooks. the closure compiler supports stripping by namespace so it could remove everything starting with cljs.pprint. the option for that however is not exposed since its kind of a footgun and easy to destroy your entire build using it

so I just released 2.7.11 which exposes those options. I'll just document with a warning but basically you can now add :compiler-options {:strip-type-prefixes #{"cljs.pprint"}}

that will remove everything cljs.pprint related, which also includes every USE of cljs.pprint so beware 😉

this only applies to :release builds though

https://shadow-cljs.github.io/docs/UsersGuide.html#_code_stripping

this is amazing

thanks 🙂

More info: I'm compiling for node and running on AWS lambda. This is the execution error I get:

{
  "errorMessage": "Cannot find module 'bluebird'",
  "errorType": "Error",
  "stackTrace": [
    "require (internal/module.js:11:18)",
    "/var/task/main.js:494:240",
    "shadow$umd$export (/var/task/main.js:5:22)",
    "Object.<anonymous> (/var/task/main.js:9:3)",
    "Module._compile (module.js:652:30)",
    "Object.Module._extensions..js (module.js:663:10)",
    "Module.load (module.js:565:32)"
  ]
}

"errorMessage": "Cannot find module 'bluebird'"

thats the actual error I guess

try npm install bluebird

ah thanks, i'm learning about npm as i go. i take it those deps aren't pulled in by leiningen?

no npm stuff is not covered by leiningen

ok cool. can you recommend somewhere i can read about how to use the npm dependencies once i've done npm install bluebird (i've done yarn add bluebird, which i'm hoping does the same thing)?

yes thats the same

so in my case i'm trying to work out how to get these npm deps into AWS lambda, they don't seem to go into the target folder which is what i'm sending to AWS

yeah I think you need to include the node_modules folder in your upload

I don't know much about AWS

ah ok, thanks

your help is much appreciated, and i'm writing a blog post about how to do this so hopefully it'll go a little further yet!

someone wrote an article not too long ago

https://dev.to/royalaid/cljs-s-lambda-697

maybe that helps?

yeah that's what i've been following but it doesn't seem to cover npm deps

ah ok

just out of interest, when developing with shadow-cljs, how do you know which npm deps you need to install?

well typically they are installed automatically

for example, you add a clojurescript library, and when it runs it'll throw errors for all the missing npm libraries until you install them, right?

but you are most likely affected by the cljsjs compatibility stuff

so i'm going through one by one, but it feels like i'm missing something simple

those can't install the deps automatically since the cljsjs deps don't declare their npm dependencies

what's the workflow you would usually use for this?

it is unfortunate that most cljs libs don't declare their npm dependencies properly

there typically is not workflow involved

oh so it's a problem that can be resolved only in the libraries themselves

ok thanks!

when using anything react related you probably just do yarn add react react-dom create-react-class

bluebird is most likely coming from promesa

good to know, i'm sure at some point i'll try out react yeah bluebird > promesa > kvlt

so yeah its just libraries that don't declare npm deps properly since they typically just use cljsjs instead

i'm trying to make an http request but it seems super difficult

oh, does cljsjs not work with shadowcljs?

just use (js/fetch "something")

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

wow ok, that'll take some learning, thanks!

on that js/fetch, what is that? is there some js interop i can use to make http requests without having to use a cljs one?

i've always used cljs-http in the past

ah right you are on node

but that doesn't work in node

sorry js/fetch is for the browser

cljs-http should be working for node?

no, it doesn't because there's no XmlHttpRequest in node, which cljs-http requires. i've also looked at kvlt, but that has the similar problem of needing other stuff, which is why i'm learning about npm

otherwise the npm request lib is pretty popular I think

cool, maybe straight interop will be easier, although it seems to require npm as well which is the main problem

thanks again

node http package is built-in and should work just fine

yeah it looks as though that's always available, but i'd have to write a bunch of code to handle chunked responses. i'm guessing that solving the npm problem will be easier, and it has obvious other benefits for the future

incidentally i always get the variable shadow$umd$export is undeclared warning on compilation. is that something to worry about?

uhm are you publishing shadow-cljs compile or shadow-cljs release?

should only use shadow-cljs release when copying something to AWS

compile/watch are only meant to run locally

i'm running yarn shadow-cljs release app

)$ yarn shadow-cljs release app; cd target; rm arch
ive.zip; zip -r archive.zip *; cd ..
yarn run v1.12.3
$ /mnt/c/Users/conan/dev/minimal-shadow-cljs-nodejs/node_modules/.bin/shadow-cljs release app
shadow-cljs - config: /mnt/c/Users/conan/dev/minimal-shadow-cljs-nodejs/shadow-cljs.edn  cli version: 2.7.9  node: v8.15.0
shadow-cljs - running: lein run -m shadow.cljs.devtools.cli --npm release app
[:app] Compiling ...
------ WARNING #1 --------------------------------------------------------------
 File: shadow/module/main/append.js:2

 variable shadow$umd$export is undeclared
--------------------------------------------------------------------------------

nil
[:app] Build completed. (130 files, 1 compiled, 0 warnings, 16.52s)
Done in 37.80s.

shadow-cljs.edn:

{:lein true
 :builds {:app {:target :node-library
                :exports {:handler server.main/handler}
                :output-dir "target"
                :output-to "target/main.js"}}}

oh. yeah ignore that. I'll fix that so it doesn't show up

cool, thanks

thought you had some runtime error with that

no, just a warning on compilation

just to wrap up, i went through all the npm errors one by one installing each dep and now it's working! in the end i used kvlt. thanks for your help!