what does this mean in practical terms? I cannot use set! on goog-define?

Closure compilation failed with 4 errors
--- registry/aws_test.cljs:16
@define variable registry.PROVIDER assignment must be global

[edit] Ok, at https://github.com/binaryage/cljs-devtools/blob/master/docs/faq.md#what-is-the-hints-feature I finally noticed that I can enter, at the REPL: (devtools.core/install! [:formatters :hints]) Also, to make the documentation better, it should be explained exactly where the following configuration is written: :external-config { :devtools/config { :features-to-install [:formatters :hints] :fn-symbol “F” :print-config-overrides true}} I assume it’s written in cljs-build configuration. I’m using shadow-cjls, not cljs-build. -------------------------------------------------------------------------------- I’m using Cursive and running this command from an IntelliJ terminal: lein with-profile +dev-cljs run -m shadow.cljs.devtools.cli watch :app …so when my web page loads, I see: Installing CLJS DevTools 0.9.10 and enabling features :formatters (with :hints and :async greyed out - the latter two weren’t loaded). How can configure project.clj or shadow-cljs.edn - or employ some other tactic - so that I can activate the :hints functionality of CLJS DevTools, i.e., DevTools? (PS, here is relevant portion of project.clj :profiles {:dev-cljs {:dependencies [[binaryage/devtools “0.9.10"] [thheller/shadow-cljs “2.5.1”]]}} and here is shadow-cljs.edn {:source-paths [“src”] :nrepl {:port 3333} :lein {:profile “+dev-cljs”} :builds {:app {:target :browser :output-dir “public/js” :asset-path “/js” :modules {:main {:entries [giggin.core]}} :devtools {:after-load giggin.core/main :http-root “public” :http-port 3000}}}}

Hey guys, does anyone know how to enable css live reloading for electron?

@endenwer how does electron deal with CSS? how are the files included?

I am trying to make it work with this example https://github.com/ahonn/shadow-electron-starter.

Config

;; shadow-cljs configuration
{:source-paths ["src"]

 :dependencies [[reagent "0.8.0-alpha2"]
                [cider/cider-nrepl "0.18.0-SNAPSHOT"]]

 :builds {:main {:target :node-script
                 :output-to "resources/main.js"
                 :main app.main.core/main}

          :renderer {:target :browser
                     :output-dir "resources/public/js"
                     :asset-path "js"
                     :modules {:renderer {:init-fn app.renderer.core/start!}}
                     :devtools {:after-load app.renderer.core/start!
                                :watch-dir "resources/public"}}}}

There is a library for that https://github.com/Quramy/electron-connect but as I know it reloads everything not just css

hmm it has trouble with the file:// urls electron returns for document.location.href

so i’m trying to run karma, to test my outputted js files

those dependencies that are not found are in the “dependencies” key in package.json , and i’ve npm install’d

hmm odd

I guess this code fails

if (util && util.inspect && util.inspect.custom) {
  module.exports.prototype[util.inspect.custom] = function () {
    var obj = util.inspect({ length: this.length });
    return this.constructor.name + ' ' + obj;
  };
}

any reason why that would fail?

even after an explicit npm install it still does not work

there is nothing for you to install

compilation would fail if it were missing any packages. the code is just weird

which code? mine? i.e is this something i can fix?

no the JS code in node_modules/readable_stream

ah

you probably can't fix it no

poo. well i’m using that to resolve stream

:resolve {"object.assign" {:target :npm :require "object-assign"}
                              "stream"        {:target :npm :require "readable-stream"}}

so could maybe try remove that?

uhm yeah don't do that

if i dont:

[:ci] Compiling ...
symbol module$node_modules$object_assign$index already provided by [:shadow.build.npm/resource "node_modules/object-assign/index.js"], conflict with [:shadow.build.npm/resource "node_modules/object.assign/index.js"]
{:provide module$node_modules$object_assign$index, :conflict [:shadow.build.npm/resource "node_modules/object-assign/index.js"], :resource-id [:shadow.build.npm/resource "node_modules/object.assign/index.js"]}
ExceptionInfo: symbol module$node_modules$object_assign$index already provided by [:shadow.build.npm/resource "node_modules/object-assign/index.js"], conflict with [:shadow.build.npm/resource "node_modules/object.assign/index.js"]
	clojure.core/ex-info (core.clj:4739)
	clojure.core/ex-info (core.clj:4739)

sorry I meant don't do the stream override

oh right

okay let me try that

object.assign is fine

shadow-cljs has a few built-in node overrides for browser builds

and you just interfered with one of them 😉

https://github.com/thheller/shadow-cljs/blob/master/src/main/shadow/build/npm.clj#L288

oh haha

The required JS dependency "readable-stream/writable.js" is not available, it was required by "node_modules/stream-browserify/index.js".

Searched in:/Users/chrisetheridge/code/Cognician/Monolith/node_modules

You probably need to run:
  npm install readable-stream/writable.js

trying the readable-stream/writable.js. but i’ve installed readable and stream

yeah that repo doesn’t exist (writable.js)

you probably installed too many packages

ah

or rather the wrong ones

ill clean node modules

all of those should be ... wait ... do you have shadow-cljs and a dependency in your package.json?

I made that optional a while ago and this has caused sooo much trouble

it definitely was not worth removing it

remove util and buffer definitely

them rm -rf node_modules

npm install should definitely install the node_modules/readable-stream then

trying that now

npm can be a PITA sometimes

➜  Monolith git:(shadow-cljs) ✗ shadow compile ci --debug
shadow-cljs - config: /Users/chrisetheridge/code/Cognician/Monolith/shadow-cljs.edn  cli version: 2.5.1  node: v10.8.0
shadow-cljs - starting 2.5.1 with launcher 2.1.0 ...
[:ci] Compiling ...
The required JS dependency "readable-stream/readable.js" is not available, it was required by "node_modules/stream-browserify/index.js".

Searched in:/Users/chrisetheridge/code/Cognician/Monolith/node_modules

You probably need to run:
  npm install readable-stream/readable.js

See: 

➜  Monolith git:(shadow-cljs) ✗

does node_modules/readable-stream exist? if so check its package.json please

no it doesn’t

hmm? are you running npm in the wrong directory or something?

nah definitely in the right dire

try deleting node_modules and package-lock.json again

lol doing that now as a try

I don't understand why it wouldn't install the package?

ah that worked!

package-lock was out of sync i guess

hmm ok

does that happen often?

yeah .. npm sucks ...

😕

is there a way to reduce how much memory shadow-cljs is using?

Have an 8G laptop and having trouble

you can set :jvm-opts ["-Xmx1G"] in shadow-cljs.edn

that would limit it to 1gb

can try -Xmx512m

maybe 256m but at that point you'll run into problems I think

[:ci] Compiling ...
The required JS dependency "react-dom/test-utils" is not available, it was required by "node_modules/enzyme-adapter-react-15/build/ReactFifteenAdapter.js".

Searched in:/Users/chrisetheridge/code/Cognician/Monolith/node_modules

You probably need to run:
  npm install react-dom/test-utils

is react-dom not installed?

and no you don't need :resolve for this

whenever you see a message like this

check /Users/chrisetheridge/code/Cognician/Monolith/node_modules + react-dom/test-utils

so

/Users/chrisetheridge/code/Cognician/Monolith/node_modules/react-dom/test-utils.js

the error message isn't ideal. it should list the full paths it tried to find

ah okay. let me check that

i’ve installed react-dom

it was in your deps so it should be there

but you pinned the version to exactly 15.0.0

thats probably not ideal

it may just not exist in that version

yeah that’s most probably the reason. going to see if i can bump it

oh i can use 16

probably don't have to bump to the latest react. just something more recent from the 15.x branch

15.0.0 is probably just bad

yeah that worked 🙂 thank you

is it possible to use a runner ns with karma?

if i use a runner ns, i get init is not defined

➜  Monolith git:(shadow-cljs) ✗ karma start --single-run
17 08 2018 12:38:56.254:INFO [karma]: Karma v2.0.5 server started at 
17 08 2018 12:38:56.259:INFO [launcher]: Launching browser ChromeHeadless with unlimited concurrency
17 08 2018 12:38:56.267:INFO [launcher]: Starting browser ChromeHeadless
17 08 2018 12:38:56.619:INFO [HeadlessChrome 0.0.0 (Mac OS X 10.13.6)]: Connected on socket B0WRKA9GuQOl0l4wAAAA with id 88087934
HeadlessChrome 0.0.0 (Mac OS X 10.13.6) ERROR
  {
    "message": "Uncaught TypeError: Cannot read property 'init' of undefined\nat : Cannot read property 'init' of undefined\n    at eval (eval at <anonymous> (/Users/chrisetheridge/code/Cognician/Monolith/node_modules/karma-cljs-test/adapter.js:6:7), <anonymous>:1:19)\n    at ContextKarma.start (/Users/chrisetheridge/code/Cognician/Monolith/node_modules/karma-cljs-test/adapter.js:6:7)\n    at ContextKarma.loaded ()\n    at ",
    "str": "Uncaught TypeError: Cannot read property 'init' of undefined\nat : Cannot read property 'init' of undefined\n    at eval (eval at <anonymous> (/Users/chrisetheridge/code/Cognician/Monolith/node_modules/karma-cljs-test/adapter.js:6:7), <anonymous>:1:19)\n    at ContextKarma.start (/Users/chrisetheridge/code/Cognician/Monolith/node_modules/karma-cljs-test/adapter.js:6:7)\n    at ContextKarma.loaded ()\n    at "
  }

are you using a custom :runner-ns?

yes

can you not use a custom one?

with karma

then you must adjust your karma config accordingly

it tries to call client: {args: ["shadow.test.karma.init"]

ah of course. it hooks into shadows one

doh thanks dude

[0:0]~cljs.user=> (require '["enzyme-adapter-react-16" :as Adapter])
[:result {:type :repl/error, :ex #error {
 :cause "symbol module$node_modules$object_assign$index already provided by [:shadow.build.npm/resource \"node_modules/object.assign/index.js\"], conflict with [:shadow.build.npm/resource \"node_modules/object-assign/index.js\"]"
 :data {:provide module$node_modules$object_assign$index, :conflict [:shadow.build.npm/resource "node_modules/object.assign/index.js"], :resource-id [:shadow.build.npm/resource "node_modules/object-assign/index.js"]}
 :via
 [{:type clojure.lang.ExceptionInfo
   :message "symbol module$node_modules$object_assign$index already provided by [:shadow.build.npm/resource \"node_modules/object.assign/index.js\"], conflict with [:shadow.build.npm/resource \"node_modules/object-assign/index.js\"]"
   :data {:provide module$node_modules$object_assign$index, :conflict [:shadow.build.npm/resource "node_modules/object.assign/index.js"], :resource-id [:shadow.build.npm/resource "node_modules/object-assign/index.js"]}
   :at [clojure.core$ex_info invokeStatic "core.clj" 4739]}]

in a shadow-cljs browser-repl

nvm. hit this before. i was on the wrong build

hmm i still cannot require this module properly

["enzyme-adapter-react-16" :default Adapter]

browser repl doesn't have the :resolve setting

regardless of :default :refer or :as, i get undefined each time

read the error message. none of that matters

i get no error message. printing the required object gives me undefined

hmm? you just posted an error above?

that was in the browser repl. i wanted to debug the require from there. but dropped that cause of the resolution errors

sec

Fix for loading files with absolute paths in electron. With this live reloading will work.

@endenwer I can fix the live reload, its just getting confused because of the file: url since I didn't expect that it just assumes http semantics currently.

no need to hack into electron to make this work

This is from https://github.com/electron/electron/issues/2242. I din't find another way to fix live reloading

@endenwer I can fix it .. just not right now.

https://github.com/thheller/shadow-cljs/issues/371

You mean in shadow-cljs?

yes

@henrik try running shadow-cljs stop and then shadow-cljs server. it probably fails on startup.

odd

may be related to the new launcher though. I'm currently reworking that again to fix a few things

you can just downgrade to 2.4.33

I see. Are you storing logs somewhere that I can send you?

there should be one in .shadow-cljs/*.log

Downgrading works fine

henrik@Mimir-2 ~/D/P/P/i/a/.shadow-cljs> cat server.stderr.log
Error: Unable to access jarfile null
Error: Unable to access jarfile null
Error: Unable to access jarfile null
Error: Unable to access jarfile null
Error: Unable to access jarfile null
Error: Unable to access jarfile null
Error: Unable to access jarfile null
Error: Unable to access jarfile null
Error: Unable to access jarfile null
Error: Unable to access jarfile null
Aug 17, 2018 6:28:11 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.8.Final
Aug 17, 2018 6:28:11 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.8.Final
shadow-cljs - HTTP server for :client available at 

those are not normal errors though

OK, I rm-rf’d .shadow-cljs, reinstalled 2.5.1, and did a shadow-cljs start.

server.stderr.log has a single Error: Unable to access jarfile null in it

what's the recommended way to serve non-js dependencies from npm (e.g., the css file for katex)? I am hoping there is something better than webjars or symlinks into the node_modules directory

don't serve them at all. bundle them into one file.

I currently use node-sass for that

I would appreciate some 👀 on https://github.com/shadow-cljs/lein-template/pull/4

I'm off to lunch right now, but I'll be back in a couple hours.

Is it possible to increase --max-old-space-size (the max heap size) via the package.json (reference: https://stackoverflow.com/a/34358130) I'm running out of memory doing some very large batch processing with fs

I.e., can shadow listen for the start command in package.json?

@loganpowell where are you running out of memory?

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node_module_register
 2: v8::internal::FatalProcessOutOfMemory
 3: v8::internal::FatalProcessOutOfMemory
 4: v8::internal::Factory::NewFillerObject
 5: v8::internal::wasm::WasmOpcodes::TrapReasonMessage
 6: 000002033BF843C1

no which build?

cli version: 2.4.25

you mean shadow or Node?

node-repl or what?

yes, node-repl

but it's due to the load I'm putting on Node

you can run (shadow/node-repl {:node-args ["--whatever"]})

that option is however not available from the CLI currently so only from clj-repl

Like this?

(shadow.cljs.devtools.api/node-repl {:node-args ["--max-old-space-size=8192"]})
To quit, type: :cljs/quit
=> [:selected :node-repl]

yep

so that's the equivalent of:

"start": "node --max-old-space-size=4076"

sorry with the 8192 in there instead

yes

sweet! Thank you!