finished a prototype last night of sending code from my editor to developing webpage, https://www.youtube.com/watch?v=lOdUfa7TfW0

@jiyinyiyong two things: can you please post you target/shadow-cljs/logging.properties? the warning you see on startup is NOT normal. Also please dont use the from-remote call, it is not part of any public API and may change at any time. Just call (shadow.cljs.devtools.api/repl :build-id) instead.

also your startup time seems excessively slow? you are probably out of memory and swapping right? maybe setting :jvm-opts ["-Xmx521M"] helps a little?

CPU in Mac 12 inch is slow. It is obviously faster when I run shadow-cljs in Macbook Pro.

it still seems very slow. just thinking that it might be using too much memory and start swapping

very likely to happen if you only have 4GB or so

is (shadow.cljs.devtools.api/repl :build-id) doing the same thing like from-remote?

no, but that is the point. from-remote does stuff you don't need.

> 1.2GHz dual-core 7th-generation Intel Core m3 processor Turbo Boost up to 3.0GHz 8GB 1866MHz LPDDR3 memory 256GB SSD storage1

hmm guess that is a realyl slow CPU then 😛

not with that device currently... looks it's 8G,

really really slow CPU... I bought it because of the light weight.

will do after I get home.

Hi, may I ask how to get some other than js files from npm package in the build? In this case css from material-components-web package. I searched the User Guide and web generally, but haven't found anything.

I can just copy it to public folder, but maybe there is some better way?

currently shadow-cljs doesn't provide anything to build css

well I thought something like boot sifting

so you either need to copy manually or use a tool to do it for you

Ok, thank you

I eventually want to build something for css but nothing available yet

Cause today I spent such a horrible morning with cljsjs and externs problem in production build, I have to move to shadows ASAP 😉

just moved my build script into a .clj file, from package.json https://github.com/mvc-works/calcit-workflow/blob/master/cli/build/main.clj

but I still too call yarn build as an alias for shadow-cljs run-cljs build.main/build.. the later is quite long.

possible to call that piece of code in a shorter form?

shorter form no

😄

thought about adding #!shadow-cljs for a while.

if there's some improvements on clj tool, I would try to switch.

why would you switch?

calling clj cli/build.clj is shorter.

and when I want to run some bash scripts from clj, I don't have to initialize shadow-cljs before running it.(although calling Bash scripts from Clojure is kind of slow.)

I personally dislike the running of scripts but I can add an option for that if you like

if you put things in proper namespaces you can run everything from the REPL

scripts are kinda annoying to use imho

I used npm scripts for long time, typing yarn build yarn html is really smooth.

I meant cli/build.clj as "script"

tried clj again... not feeling very good still.

it's slow. only benefit is clj -m build.release is short to type in.

easy fix alias x="shadow-cljs run-clj"

x build.release

yep...

what did you mean by REPL?

=>> yarn shadow-cljs clj-repl
yarn run v1.3.2
$ /Users/chen/repo/mvc-works/calcit-workflow/node_modules/.bin/shadow-cljs clj-repl
shadow-cljs - config: /Users/chen/repo/mvc-works/calcit-workflow/shadow-cljs.edn version: 2.1.6
shadow-cljs - starting ...
shadow-cljs - HTTP server for ":browser" available at 
shadow-cljs - server running at 
shadow-cljs - socket repl running at localhost:5900
shadow-cljs - REPL - see (help), :repl/quit to exit
[1:0]~shadow.user=> (require '[build.main :as b])
nil
[1:0]~shadow.user=> (b/build)
{:exit 0, :out , :err }
[:browser] Compiling ...

I actually feel better using a REPL.

shadow-cljs node-repl
shadow-cljs - config: /home/joscha/src/realtime-playground/backend/shadow-cljs.edn version: 2.1.6
shadow-cljs - running: lein run -m shadow.cljs.devtools.cli --npm node-repl
Feb 12, 2018 6:17:05 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.3.8.Final
Feb 12, 2018 6:17:05 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.3.8.Final
shadow-cljs - server running at 
shadow-cljs - starting node-repl
[:node-repl] Configuring build.
[:node-repl] Compiling ...
[:node-repl] Build completed. (39 files, 1 compiled, 0 warnings, 1.96s)
[0:0]~cljs.user=> fs.js:642
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: ENOENT: no such file or directory, open '/home/joscha/src/realtime-playground/backend/shadow-cljs/builds/node-repl/dev/out/cljs-runtime/goog.debug.error.js'
    at Error (native)
    at Object.fs.openSync (fs.js:642:18)
    at Object.fs.readFileSync (fs.js:510:33)
    at global.SHADOW_IMPORT ([stdin]:44:15)
    at [stdin]:3003:1
    at [stdin]:3042:3
    at ContextifyScript.Script.runInThisContext (vm.js:25:33)
    at Object.runInThisContext (vm.js:97:38)
    at Object.<anonymous> ([stdin]-wrapper:6:22)
    at Module._compile (module.js:570:32)

{:aws-lambda {:id               :aws-lambda
                       :target           :node-script
                       :output-to        "target/backend/backend.js"
                       :main             backend.core/main
                       :optimizations    :none
                       :language-in      :ecmascript5}}

strange... https://github.com/thheller/shadow-cljs/issues/193

@schnipseljagd oops. there is a bug in the resolve code

looking into it

the node process for the repl is started by basically doing cat target/shadow-node-repl.js | node and that filename gets lost in the process

so node will resolve relative to the process root which is incorrect

that broke when I moved to relative paths in 2.1

meh

can't remember why I don't just call node target/shadow-node-repl.js

just released 2.1.7. I also upgraded the Closure Compiler version which may break stuff. Please let me know if you run into any issues. I did some testing and all appears to be working correctly but its really hard writing automated tests for this stuff so I may have missed some stuff.

@schnipseljagd 2.1.7 also fixes the node-repl

Thx a lot. I am going to verify it.

Looks good to me 🙂