Hi everybody. Is there a way to reference a local project as a dependency in shadow-cljs.edn? Like :local/root does in deps.edn, I mean.

only if you use deps.edn

you could just add the :source-paths manually too but nothing like :local/root without deps.edn

I see, thank you

Hi, in my shadow-cljs.edn file i have :source-paths [ "dev" "src" "test" ] - in the dev directory, i have company/repl.cljs, and add :repl-init-ns company.repl - when i then load the page, i get a 500 error with the message clojure.lang.ExceptionInfo: no output for id: [:shadow.build.classpath/resource "company/repl.cljs"] {:resource-id [:shadow.build.classpath/resource "company/repl.cljs"]. I've also tried just putting user.cljs in there, but get the same error. Is there something obvious I'm missing? to start the repl, i'm running shadow-cljs cljs-repl my-project-id.

something seems off about your error

500 error doesn't make sense?

you are running shadow-cljs watch your-build I presume?

yes sir

and that completed successfully?

yes, and that's where the error is being printed, in the watch terminal

Apr 08, 2019 10:16:42 AM io.undertow.server.Connectors executeRootHandler
ERROR: UT005071: Undertow request failed HttpServerExchange{ POST /worker/files/sif/4ef2910a-fa9c-4a38-b142-fcbfbc831193/34c60217-4ac5-46a3-b75c-7567c23309ca request {Accept=[*/*], Accept-Language=[en-US,en;q=0.9], Accept-Encoding=[gzip, deflate], Origin=[], User-Agent=[Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3626.96 Safari/537.36], Connection=[keep-alive], Content-Length=[427], content-type=[application/edn; charset=UTF-8], Referer=[], Host=[]} response {Cache-Control=[private, no-cache]}}
clojure.lang.ExceptionInfo: no output for id: [:shadow.build.classpath/resource "company/repl.cljs"] {:resource-id [:shadow.build.classpath/resource "company/repl.cljs"]}

oh. the company.repl namespace probably isn't included by any other means right?

full error

try adding it to :preloads

ah, no - i thought the source-path would somehow imply it was required

I guess I don't account for :repl-init-ns not being part of the build

probably should

for now just add it to :devtools {:preloads [company.repl]} for your build

that was it, it's working now

thanks!!!!!

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

really appreciate it

very weird error that I’m having trouble debugging. trying to get a bare bones shadow-cljs compilation working with my app via lein. have my :depencencies and :source-paths set in my project.clj and :lein true set at the top level of my shadow-cljs config. receiving the error Exception in thread "main" Syntax error compiling . at (shadow/build/closure.clj:67:5).. I’ve stripped down everything in my project.clj to be absolutely bare bones with just dependencies and src-paths, yet still encountering this error

just declaring everything in shadow cljs and not using lein works for getting my js built. working with a clj/cljs codebase tho and would prefer to not have to duplicate my dependencies declaration for the different platforms

check lein deps :tree

there should be a [com.google.javascript/closure-compiler-unshaded "v20190325"] dependency

if you still have a cljsbuild or figwheel plugin running they might be adding older versions of that dep

yep that’s exactly the conflict

The blog post I wrote about my adventures with shadow-cljs and react native navigation was published today: https://040code.github.io/2019/04/02/react-native-navigation-and-clojurescript/. (Here you are @haiyuan.vinurs.) Thanks again @thheller!!

hello everyone

hey

I’v just started to use shadow-cljs, pretty nice tool, thanks to everyone involved.

I’m hitting a problem in my project config right now, I’m really stuck trying to understand why it’s not working. My project file looks like this:

{:source-paths [“src”] :dependencies [[cider/cider-nrepl “0.21.0"]] :builds {:app {:target :node-script :output-to “target/main.js” :main server.main/main! :devtools {:after-load server.main/reload!} :js-options {:resolve {“oauth2" {:target :file :file “/src/js/oauth2.js”}}}}}}

the problem here is the :js-options keyword, the compiler continues to tell me this:

[:app] Build failure: Wrong number of args (4) passed to: shadow.build.npm/js-resource-for-file

why are you doing that?

@thheller good question. Because I wasn’t able to import some functions from a js file I have in my project, so I tried to specify this file in the project config

so you want to include that file directly in your project? it is not an override for something within node_modules?

My import doesn’t work:

(ns server.google-sheet (:require [“fs” :as fs] [“googleapis” :as g] [“oauth2” :as auth :refer (listFiles oAuth2Client)] [clojure.pprint :as pp] [promesa.core :as p]))

@thheller no, it’s not an overwrite

ok yeah then you should skip the :resolve config completely

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

and just require the file directly

ok, but then importing functions from the js file results in the imported symbols being null

what module format do you use? import/export ESM or require/module.exports commonjs?

the .js file that is

the module.exports flavour

ok that should work fine then?

I think so, but hey, at least you directed me on the right track again, I was fighting with the wrong configuration settings

@rastandy try logging auth and see what's in there

as a quick test make sure the file is on the classpath

I will check the .js file correctness

then fire up shadow-cljs browser-repl

then (require '["/path/to/file.js" :as x])

(prn x)

uhm I’m using cider-connect-cljs, it works but right now it’s not finding the .js file

let me check again the path

with your :source-paths ["src"] and the file at src/js/oauth2.js it would be (require '["/js/oauth2.js" :as x])

(js/console.dir x) is sometimes better than (prn x) so maybe try that too

I’ve included the js file in my server.main namespace

the file is loaded from the app and some code is executed, I see the output in the stdout

but when importing, the ns is null

can you please test why I asked?

skip cider or anything else

(ns server.google-sheet (:require [“fs” :as fs] [“googleapis” :as g] [“./oauth2” :as auth :refer (listFiles oAuth2Client)] [clojure.pprint :as pp] [promesa.core :as p])) (prn auth)

don't use prn then

(prn auth) is null

and the file actually has exports?

oh ok, will skip cider

yes: module.exports = { authorize, listFiles, oAuth2Client };

can try shadow-cljs node-repl since this is node stuff

ok

just want to eliminate all other factors and that is the quickest way to do it

I’m not able to change namespace in the node-repl 😞

sorry forget that

don't change the namespace

just require

it was a typo

literally just shadow-cljs node-repl then (require '["/server/oauth2.js" :as x]) (js/console.dir x) nothing else

yes it loads the file, I can see the output from some statements in the js file

and what is x?

#js {:default #js {:authorize #object[Function], :listFiles #object[Function], :oAuth2Client #object[OAuth2Client [object Object]]}}

looks like it's loading as esm

ah right ... closure is rewriting it "incorrectly"

probably best to just switch the file to use export { authorize, listFiles, oAuth2Client } instead.

I’m not that into JS modules…

does it matter for this file? is anyone else using it?

no, only me

well that is the quick and easy fix I can offer

the other way is [“./oauth2” :default oauth] and then oauth/listFiles etc

Ok, but does that imply something else?

no doesn't imply anything else

its just the annoying situation in that the JS world cannot decide on how to do ESM->CommonJS interop

I made the change in the file: export { authorize, listFiles, oAuth2Client };

and the closure compiler only supports strict mode currently

now when requiring the module I get:

which means commonjs files only get a default export

[:result {:type :repl/error, :ex #error { :cause “closure errors” :data {:tag :shadow.build.closure/errors, :errors [{:resource-name “server/oauth2.js”, :source-name “server/oauth2.js”, :line 93, :column 0, :msg “A file cannot be both a CommonJS module and an ES6 module.“}]}

did you remove the module.exports?

can't have both

or whatever else is in line 93

yes

line 93 is this:

export { authorize, listFiles, oAuth2Client };

and is there a require or exports or module.exports reference before that?

closure already decided to treat that file as commonjs before it gets to line 93

gosh! Yes there are requires at the top of the file, sorry

I’m pretty lost in JS modules land

hmm hang on ...

something odd is happening here

because commonjs files on the classpath that have require should not be rewritten by closure

which version are you on?

shadow-cljs - config: /Users/arusso/Development/clojurescript/ask-scopus/shadow-cljs.edn cli version: 2.8.26 node: v11.13.0 shadow-cljs - server version: 2.8.26 running at http://localhost:9630

hmm

alright there seems to be a bug

where node targets are treated differently than browser one

sorry @thheller maybe it’s better to report with complete files

I have the issue reproduced now so its fine

ah ok

totally new to shadow-cljs but i'm excited to start building some node modules! when following the shadow-cljs repo's readme and also with the minimal-shadow-cljs-browser i get the following error in the browser:

bidi.js:276 Uncaught SyntaxError: Invalid regular expression: /[Ö‘-Û¯Ûº-ࣿâ€�-��-�ï¬-ï·¿ï¹°-ﻼ]/: Range out of order in character class
    at new RegExp (<anonymous>)
    at bidi.js:276

invalid charset used in the HTML

add <meta charset="utf-8"> to your html

heyo, that did the trick. thanks!

next question. the repo's readme refers to :node-script as a build target where as the docs refer to :node-library. which one am i after?

depends on what you want to build?

ah, they're different. got it. i was hoping to play around with cljs and aws nodejs lambdas.

for that you want :node-library

@thheller thank you very much for you rhelp

great, thanks! really looking forward to all the great things i've heard about shadow-cljs.

@rastandy I just pushed 2.8.29 that fixes the broken commonjs interop. so it should be working correctly now, no need for :default

might need to undo the changes if you switched to :default

if you switched to import/export that is fine

@joshkh there was a post about shadow-cljs + aws here https://dev.to/royalaid/cljs-s-lambda-697

maybe that helps

@thheller thank you very much! I’ll confirm if it’s working, thank you again

> maybe that helps immensely. thanks for sharing!

quick question, I’m trying to figure out the best way to handle a ‘lib’ project. Say I have a project with some common fulcro components and it uses a few react libs, then I want to pull it in to my main ui app, via say clojure deps. I guess I’d need to the main app’s package json also include any of the lib projects npm dependencies?

you can include a deps.cljs file with {:npm-deps {"whatever" "version"}} in the lib

I may just be misunderstanding things, but it seems like when I run shadow-cljs watch app, and open my browser, then connect via a CIDER repl, that there are two distinct contexts. For example, I have an atom defined with defonce - in the browser, it has one value, but at the REPL, it ahs another. Is there a way to unify these two contexts?

do you open the correct REPL?

I don't know much about cider sorry but shadow-cljs cljs-repl app would give you the REPL into the browser

https://shadow-cljs.github.io/docs/UsersGuide.html#cider dunno how current this is

Ah ok cool