uhm that error doesn't make sense. is this one of your files node_modules/raw-body/index.js? node-library doesn't process npm packages, so this weird

or did you configure it specifically to bundle npm packages?

and how did you require it? should be (:require ["async_hooks" :as x]), not (:require [async_hooks :as x]). ie a string not a symbol

thanks for the quick response! I love shadow-cljs, awesome user experience!! 🔥 node_modules/raw-body/index.js is not one of my files, probably pulled in in my import of express (:require ["express" :as express])

The required JS dependency "async_hooks" is not available, it was required by "node_modules/raw-body/index.js".

Dependency Trace:
	shadow/umd_helper.cljs
	test/lambdas/checkout.cljs
	node_modules/express/index.js
	node_modules/express/lib/express.js
	node_modules/body-parser/index.js
	node_modules/body-parser/lib/types/json.js
	node_modules/body-parser/lib/read.js
	node_modules/raw-body/index.js

Searched for npm packages in:
	/Users/user/dev/checkout/node_modules

could be a misunderstanding on my side how npm and node work, or shadow.. I think I've configured it based on your example of deploying a function to netlify

:stripe-checkout {:target :node-library
                    :output-to "landing/functions/checkout.js"
                    :exports {:handler test.lambdas.checkout/handler}
                    :js-options
                    {:js-provider :shadow
                     :keep-native-requires true}
                    :devtools
                    {:enabled false}}

well yes, that configure it to make shadow-cljs bundle npm dependencies

in that case you can add :keep-as-require #{"async_hooks"} to the :js-options map

not you need to bundle everything in your case though

its best if its not needed at all

woooow, thanks a lot, error is gone.. :star-struck:

what is best if it's not needed at all? the bundling?

depends on the deployment. best to just let node load the dependencies, and just have shadow-cljs build the CLJS

but that requires that the runtime can load npm packages. some can, some can't. not sure what you are deploying to

so you mean don't bundle any npm packages, because node will load them from node_modules? if I understood it right, that should work, because I'm deploying to netlify functions, and in the deployment it will install packages.json.

yeah if the runtime can install npm packages its best to just remove :js-options from the config above

but also fine to leave it when it works. 😉

hehehe, yeah, my usual approach.. I'll try it out though, makes sense

thanks a lot for your help! 😌 brings a bit more light into the shadow 😄

what does cljs-dist/cljs_env.js does not export 'Nf' mean? its not supposed to be exported? what is generating this error?

in fact what is generating this source at all? this doesn't look like npm-module output?

require("./cljs_env");require("./cljs_env.js"); why is that duplicated?

That’s generated by running the release command with shadow using this config:

{:source-paths ["src"]
 :dependencies [[reagent "1.1.1"]]
 :builds {:app {:output-dir "./cljs-dist"
                :target :npm-module
                :entries [app.main]
                :release {:compiler-options {:optimizations :advanced}}}}}

When I use :simple optimizations that duplication does not happen.

cljs-dist/cljs_env.js does not export 'Nf' refers to some mangled name that is supposed to be exported on the global $CLJS object / module

But for some reason those fields are removed after the release build finishes. And when I try to use a tool like Webpack (in this case Parcel), the JS bundler reports that error

and what do you do in your code?

removing stuff is normal and expected. $=require("react"); $CLJS is the global object

so that looks all exactly like its supposed to

I'm missing what the actual problem is here?

besides an error message I do not recognize and must be coming from other 3rd party tools

might just be a linter trying to lint :advanced optimized output?

so the question is: what is generating cljs-dist/cljs_env.js does not export 'Nf'? the error message I mean. the code is fine from what I can tell?

hmm nvm. the code is broken. cljs-dist/cljs_env.js requiring cljs_env is indeed a bug, that should not be

apologies. that error message really confused me. should be fixed as of 2.20.18, a bad cljs_env.js file was indeed being generated.

not sure that error message if fixed now though 😛

Haha no worries, I’m going to double check that the JS bundler is not doing something weird. If I keep running into the issue I’ll create a reproducible example to debug with you. Thank you for the help!