Hi, it seems I touched nothing but suddenly went into a lot of errors such as

index.js:1 Uncaught TypeError: shadow.js.provide is not a function
    at index.js:1
(anonymous) @ index.js:1
emptyObject.js:1 Uncaught TypeError: shadow.js.provide is not a function
    at emptyObject.js:1
(anonymous) @ emptyObject.js:1
invariant.js:1 Uncaught TypeError: shadow.js.provide is not a function
    at invariant.js:1

Reinstall shadow-cljs solves this. It may because of I run git pull in the shadow-cljs repo. 😕

...
[CACHED] doumi/bottomnav.cljs
-> JS Cache read: 32 JS files
<- JS Cache read: 32 JS files (24 ms)
-> Closure - Optimizing ...
Closure compilation failed with 1 errors
--- EXTERNS:/Users/yuzhao/.m2/repository/cljsjs/d3/4.2.2-0/d3-4.2.2-0.jar!/cljsjs/d3/common/d3.ext.js:670
Object literal contains illegal duplicate key "scaleSequential", disallowed in strict mode

10774 ± : ls /Users/yuzhao/.m2/repository/cljsjs/d3/                                                                         ⏎ [43m] ✹
ls: /Users/yuzhao/.m2/repository/cljsjs/d3/: No such file or directory

Does shadow-cljs need to do some "clean" work?

It is weird I already have removed all about d3 from my code.

===> Hi, I removed the target folder , removed [braintripping/re-frame-trace "0.1.9"] and run shadow-cljs release app again and it works now!

@cmal that error I believe is from an old version of braintripping/re-frame-trace

OK. I've switched re-frame-trace to re-frisk now.

And it works well in wechat simulator.

@cmal that error is from an old cljsjs/d3 release, not directly related to shadow-cljs

@thheller I update shadow-cljs version. And after that I find the old target prevent me from re-compiling the new code until I removed target folder when it begins to work.

yes, that is due to AOT. I do not recommend working with a checkout of shadow-cljs

OK.

I can probably add a config option to disable AOT, but then startup will be very slow

only need to delete target/shadow-cljs/aot-classes, the rest is ok to keep

OK. Maybe a shadow-cljs clean-aot to clean the aot. I stared at the [CACHED] things for a while and finally found out removing target will work. 😄

that is not related

😕

[CACHED] cljs/core.cljs means that the CLJS compilation output is cached

I do all kinds of checks to ensure that is properly invalidated

the AOT cache is wiped whenever a new shadow-cljs release is used

Yes. I remembered I got the error message when Optimizing....

but that doesn’t work of you use a checkout

-> Closure - Optimizing ...
Closure compilation failed with 1 errors
--- EXTERNS:/Users/yuzhao/.m2/repository/cljsjs/d3/4.2.2-0/d3-4.2.2-0.jar!/cljsjs/d3/common/d3.ext.js:670
Object literal contains illegal duplicate key "scaleSequential", disallowed in strict mode

No. I did not use a checkout. Not yet find out how to work with a checkout. 😆

do shadow-cljs --cli-info | grep d3

just in case because I lein install once weeks before.

oh wait .. it already has all the info 😉

you are using cljsjs/d3/4.2.2-0

(probably not you, but one of your dependencies)

yep. @mhuebert says it was [braintripping/re-frame-trace "0.1.9"]

https://github.com/cljsjs/packages/commit/d675025ee9194e536fd4cf2578ad0837c9bfd19d#diff-07cb41fdc598845710ebb9d47ab69d29

I removed that and it works.

this was fixed a while ago

you just need the updated cljsjs/d3 version

😄

add [cljsjs/d3 "4.3.0-5"] as your first :dependencies

latest version of shadow-re-frame already has that https://github.com/mhuebert/shadow-re-frame/blob/master/shadow-cljs.edn#L8

(a newer re-frame-trace version)

Never mind. I do not use that any more. But I will write that down, in case later I will use d3 again. 😆

@mhuebert https://clojars.org/braintripping/re-frame-trace still lists the old cljsjs/d3 dependency?

ah its a fork ok

oh… you are right though I think

I had removed d3 from the build because that feature doesn’t work anyway, but then was trying to get my fork to be closer to master and forgot about this whole d3 extern fiasco

going to submit a PR to re-frame-trace

I didn’t notice because I am not doing an :advanced build for the demo anymore as it causes too many problems with trace

wonder which hacks trace is doing 🙂

@mhuebert about circleci, if there is something I could add to make integration easier let me know

still need to figure out this cljs.test stuff

@thheller I happened to make my attempt last night when circleci itself began having reliability problems

ah hehe doh

their 1.0 platform is way too slow and underresourced so the builds fail

and their 2.0 platform wasn’t working properly last night

unfortunately i didn’t realize that their platform wasn’t working until later so I gave up on some of the config stuff that might have worked

shadow-cljs happily eats up all the resources it can get since everything is threaded/parallel

might need an option to turn that off for things like CI

2 builds in parallel = 2x memory requirement

it looks like parallelism in circleci means ‘multiple machines’ instead of providing multiple cores or more memory in one machine: https://circleci.com/docs/2.0/parallelism-faster-jobs/

and not sure if it helps us at all. they do give 4 instances for free for open source projects

hmm so each “job” only gets one core?

hmm can’t find any info on how much resources each job gets

ah found it, https://circleci.com/docs/2.0/configuration-reference/#resource_class

OSS probably = small?

probably

yuck .. definitely need a “use less resources” option then, parallel builds will actually be slower on one core

2CPU/4096MB

that’s what my build gets

ah ok, that should be ok then

circleci 2.0 is based on docker vs. their old config system

which means it is no longer simple to specify an environment that has both nodejs and java

doh

it used to be as simple as specifying a version for both. now, because they only have prebuilt docker images for each individually, you have to make or find your own

the one i found has an old version of node

equals pain.

I have to confess that I have never used docker … or rather never could get it running.

I take a plain old linux box over this container crap any day 🙂

now i found a docker image that has java and recent node, but no git

apparently i already have a docker account

you could probably use the lein image they provide

ah no wait .. need npm 😛

wait .. circleci is using clojurescript? how do they not have a pre-built image for this

maybe they do

there is an official clojure image but it appears to only include lein and boot

hmm yeah thats enough if you only use cljsjs, guess I need to sell them on shadow-cljs 😉

I cannot get shadow cljs to compile my cljs, I get the error could not find or load main class clojure.main... Google does not give any usefull hints. Going through lein it works , but I don't want to use lein for this project.

@eveko which error do you get?

Just that it cannot find clojure.main

full error + command you used would help

Give me a moment need to fish my laptop

which OS are you on? windows by any chance?

Yeah Windows

hmm yeah thats probably it. I never tried running windows before.

have you considered the linux subsystem stuff for windows? that works pretty well

I will try that in a moment

The command is shadow-cljs watch app

Then error: could not find or load main class clojure.main

pretty sure this is the cause https://github.com/thheller/shadow-cljs/blob/master/src/main/shadow/cljs/npm/cli.cljs#L33-L34

let me check if there is an easy way to figure out if running in windows

@eveko try [email protected] maybe that works

Ok i got a different error now

It is namespace related, so I think I can resolve it with some tinkering

I really recommend the linux subsystem stuff, that just works out of the box

I’m not 100% I handle everything correctly when it comes to windows, I should be in most cases

otherwise just report the errors and I’ll see if I can fix it

I had the same error though from the wsl a moment ago

The clojure main one

hmm thats odd

But then again, it does flip out having both windows and Linux version of commands

maybe old node version?

I am on node 9

hmm

booting my windows machine now 🙂

It is a pity though, I wanted to experiment with some cljs front end, our backend at work is http://asp.net framework on windows

I tried keeping everything windows compatible, just might have missed a few things

Current error I get is failed to inspect resource

Then the path of my cljs file

I really need the full error

trying it on my windows machine now but almost everything is outdated there

updates gonna take a while

running it via wsl works fine

[:app] Compiling ... Nov 01, 2017 8:04:01 PM clojure.tools.logging$eval761$fn__764 invoke WARNING: failed to inspect resource "C:\Users\*\Documents\Visual Studio 2017\Projects\techtest\techtest\src-cljs\main\app.cljs", it will not be available. The required namespace "techtest.app" is not available.

this is the console output from windows

the wsl one also has the same error, but I believe that is because wsl tends to sometimes use the windows binary of noder/yarn

I will try making this work on my home desktop where i can be sure that wsl wont use windows binaries

it sort of works in windows directly

the compiled succeeded but the watch failed, I can fix that

the above error just looks like a namespace violation?

techtest.app should be in src-cljs\main\techtest\app.cljs

if src-cljs/main is your source path

main\app.cljs would be main.app

oh hold on

yeah

not sure why the inspect fails though, there should be a proper message for that

oh hmm … might be me packing this mistake

ok i think i am overlooking how to set up the module in the edn

if I have src-cljs/main/app.cljs

:source-paths ["src-cljs"] in the shadow-cljs.edn

the namespace in app.cljs is techtest.app

then it should be in src-cljs/techtest/app.cljs

ah maybe its empty or doesn’t start with (ns techtest.app)?

everything in CLJS is namespaced and it must always be first in each sourcefile

(ns techtest.app)

maybe something wrong here?

do you have :source-paths ["src-cljs"]? besides that it looks correct

yup

hmm let me check if it chokes because of the spaces in the file path, eg. Visual Studio 2017

it really shouldn’t but you never know

can you try cloning https://github.com/shadow-cljs/quickstart-browser

cloned

so I am getitng that clojure main error

npm install + npx shadow-cljs watch app

😛

ah sorry

npm install [email protected]

didn’t bump the version

compiling should work fine

just file watching is broken

yeah exception and then build complete

trying to make sense of this error but I’ll get that fixed

I go try get my cljs to compile

cause the one I just pulled worked, It also had the visual studio path, so the spaces are not the issue

ok good to know

I got no immediate idea what might be causing your issue. does it dump a full stacktrace?

no it does not.

it did dump one when doign the browser one

the required namespace is not available... 😕

if you can post the contents of the project I can take a look

I have it on local git only atm

unless you don't mind opening a zip

sure that works

<mailto:[email protected]|[email protected]>

skip the node_modules and target folders, don’t need those 🙂

here you go

you propably also don't want the microsoft packages 😛

(ns techtest.app
    :require [reagent.cor :as r])

...

thats missing a ( before :require

bloody

dirt in my eyes

and typo at core as well

should be

(ns techtest.app
  (:require [reagent.core :as r]
            [clojure.string :as str]))

as the reagent example for some reason doesn’t have a proper require for clojure.string

besides that it looks ok

it still does not find the namespace though

also if it seems that the watch is trying to do something

hmm yeah it doesn’t work on my machine as well … investigating

hehe nice

<U+FEFF>(ns techtest.app
  (:require [reagent.core :as r]
            [clojure.string :as str]))

there is a bad character in front

whaat?

I can’t rid of it in my editor

but I don't have that , why would there be font info?

dunno, my editor doesn’t show it either

looking at it with less shows it (the linux tool, not the css thing)

indeed

but nano can't see it

yeah I tried vscode, atom, intellij, vim, emacs

not a single one is able to show or remove it

super weird

https://stackoverflow.com/questions/7297888/0xef-0xbb-0xbf-character-showing-up-in-files-how-to-remove-them

vim -b app.cljs worked

i just made an other file

copied the contents

delete old and rename

but now it cannot find react

npm install react react-dom

create-react-class

can i just not yarn add react?

yes yarn works too

it does but now I get namespace error for create-react-class

also yarn add create-react-class

its a bit unfortunate how reagent is bundled currently, the alpha is a bit in flux and doesn’t properly declare some deps

woot done 😛

it compiled

I “fixed” the watch issue … well it doesn’t error out anymore, but doesn’t update either 😉

not quite sure why

now i need to figure out how to make http://asp.net serve the correct path for js

it is trying to find the other compiled js in the views folder

but they are in the public

hmm no idea how that works in http://asp.net, never used it

should be easy to just serve one directory, its just static files

https://docs.microsoft.com/en-us/aspnet/core/fundamentals/static-files

use the public directory?

fixed

very easy really

cool

:asset-path "../js"

in the edn

be careful with relative paths in JS

if you try to do that in it won’t work

indeed

it adds the asset-path at the end of the url for the lookup

why is that so?

/public/views/public/js/cljs-runtime/module$node_modules$fbjs$lib$getActiveElement.j

instead of public/js/cljs-runtime/module$node_modules$fbjs$lib$getActiveElement.js

hmm?

:output-dir and :asset-path sort of belong together

:asset-path is where the files are reachable when using a http server

public all files from :output-dir must be reachable there

:asset-path should basically always be an absolute path

everything else is just asking for trouble

the asp link about mentions a wwwroot? so maybe use :output-dir "wwwroot/js"?

i will have to check around,

that is for http://asp.net core

but I really don’t know .. the article looks like it should work if configured correctly

i am using .net framework.

its just static files, not the typical “view”

that is so

oh well i will tinker arround. the ../js will be my dirty temporary solution

should work fine if i treat the project as a spa

@eveko just published [email protected] which has fixes for all the obvious windows issues I could find

reloading works properly now

let me know if you run into any other issues