I try to release a node-script , it works fine if I run node target/main.js. However, it seems to depend on node_modules . If I move target/main.js to somewhere else, it can't find required module anymore. Is it expected? How can I have a single file bundle?

@doglooksgood yes, that is intended. if you must have a fully standalone build I recommend post-processing the output with something like https://github.com/vercel/ncc

thank you, I'll check ncc.

I have two apps, the smaller one can be bundled by ncc, the larger one can not. The error is Error: Cannot find module 'qs', looks like it still looking for something in node_modules. I tried to (js/require "qs"), but it seems doesn't work. Any suggestion on what should I do for further debugging?

npm install qs?

can't say more without more info

It's weird to because I can found qs in node_modules, I can even run target/main.js without any problems. So I have no idea which side cause the problem. Is the generated target/main.js has a statement that ncc can not recognize? or I just ran into a bug of ncc.

Hi all, I'm trying to use d3 in a cljs project. I'm working with shadow-cljs and I'm pretty new to both shadow-cljs and d3 so expecting this might be a stupid mistake. I did a yarn add d3 which seems to have done what I expected and added a bunch of d3 modules into node_modules/ I'm requiring d3 like so:

(ns browser
  (:require ["d3" :as d3]
            ["d3-scale" :refer [scaleLinear]]
            ["d3-shape" :refer [line]]))

(-> (scaleLinear)
    (.domain #js [1 2]))
=> #object[scale]

(.select d3 "#app")

Execution error (TypeError) at (<cljs repl>:1).
module$node_modules$d3$src$index.select is not a function

["d3-selection" :refer [select]]

(select)

Execution error (TypeError) at (<cljs repl>:1).
_select is undefined

Is there a way to hide deprecated var use warnings for a particular set of vars while still showing for vars not in that set?

@dstephens do you get any errors during loading? see the browser console? I would expect things to exist but maybe something failed to load properly?

@kenny no

@thheller Yes, I have found some errors!

shadow-cljs - failed to load module$node_modules$d3_array$src$number js.js:74:16
shadow-cljs - failed to load module$node_modules$d3_array$src$bisect js.js:74:16
shadow-cljs - failed to load module$node_modules$d3_array$src$index js.js:74:16
shadow-cljs - failed to load module$node_modules$d3$src$index js.js:74:16
An error occurred when loading abc.js main.js:1672:15
shadow$provide.module$node_modules$d3_array$src$number@http://localhost:8020/js/cljs-runtime/module$node_modules$d3_array$src$number.js:5:400
shadow.js.jsRequire@http://localhost:8020/js/cljs-runtime/shadow.js.js:34:18
shadow$provide.module$node_modules$d3_array$src$bisect@http://localhost:8020/js/cljs-runtime/module$node_modules$d3_array$src$bisect.js:1:521
shadow.js.jsRequire@http://localhost:8020/js/cljs-runtime/shadow.js.js:34:18
shadow$provide.module$node_modules$d3_array$src$index@http://localhost:8020/js/cljs-runtime/module$node_modules$d3_array$src$index.js:17:485
shadow.js.jsRequire@http://localhost:8020/js/cljs-runtime/shadow.js.js:34:18
shadow$provide.module$node_modules$d3$src$index@http://localhost:8020/js/cljs-runtime/module$node_modules$d3$src$index.js:1:164
shadow.js.jsRequire@http://localhost:8020/js/cljs-runtime/shadow.js.js:34:18
shadow.js.require@http://localhost:8020/js/cljs-runtime/shadow.js.js:59:20
@http://localhost:8020/js/cljs-runtime/abc.js:2:48
goog.globalEval@http://localhost:8020/js/main.js:577:21
SHADOW_ENV</env.evalLoad@http://localhost:8020/js/main.js:1670:12
@http://localhost:8020/js/main.js:2360:12

regeneratorRuntime.mark(numbers)

yarn add core-js
yarn add regenerator-runtime

looks like you are using an older shadow-cljs verison as well?

the regenerator thing you maybe can fix by doing a (:require ["regenerator-runtime/runtime"]) before your d3 or other js requires

> older shadow-cljs verison Very likely, I was just trying to add a few things into a previously working (to the best of my limited knowledge) play project I had. Thanks, I'll try updating and adding that and see how it goes!

Thank you @thheller! 🎉

(.select d3 "#app")
=> #object[Selection [object Object]]