This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-04-12
Channels
- # announcements (1)
- # babashka (79)
- # beginners (165)
- # calva (29)
- # cider (20)
- # clara (3)
- # cljdoc (1)
- # cljs-dev (52)
- # clojure (42)
- # clojure-chicago (5)
- # clojure-europe (48)
- # clojure-germany (1)
- # clojure-italy (4)
- # clojure-nl (2)
- # clojure-spec (10)
- # clojure-uk (19)
- # clojurescript (50)
- # clojureverse-ops (5)
- # conjure (8)
- # datomic (16)
- # depstar (2)
- # events (1)
- # figwheel-main (23)
- # fulcro (26)
- # girouette (41)
- # graalvm (9)
- # heroku (3)
- # honeysql (10)
- # jackdaw (20)
- # lambdaisland (6)
- # lein-figwheel (1)
- # lsp (34)
- # malli (7)
- # meander (3)
- # music (1)
- # off-topic (14)
- # polylith (7)
- # re-frame (14)
- # reitit (8)
- # reveal (15)
- # ring (3)
- # schema (1)
- # sci (15)
- # shadow-cljs (42)
- # spacemacs (1)
- # startup-in-a-month (12)
- # tools-deps (59)
- # vim (1)
- # xtdb (27)
by this logic, you can ask any question you want... your question really has nothing to do with shadow-cljs, shadow-cljs just creates some javascript files for you, what you do with those js files is completely your problem you should ask this in a general or beginner channel or somewhere that has to do with heroku
Has anyone got a repl workflow working with developing chrome extensions?
depends on which "target" you are talking about? there are many different runtimes when it comes to extensions, background scripts, page injects, page actions etc
Yea I am still wrapping my head around it all. I’ll poke around a bit more and report back when I can more clearly express what I am looking for. I was basically wondering if there was any off the shelf demo repo’s that hooked up a repl for the extension runtimes where it works etc
Which is more standard, put :dev-tools section under build-id, or put :dev-tools under :dev (which itself is under build-id) ?
don't need to put devtools in dev, that is implicit and will not apply to release builds anyways
[:app] Build failure:
The required namespace "goog.result" is not available, it was required by "shadow/xhr.cljs".
not use shadow.xhr? 😛 goog.result was removed from closure-library with no replacement. where do you get this?
@thheller initial build
ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.oracle.truffle.js.scriptengine.GraalJSEngineFactory could not be instantiated
Warning: Nashorn engine is planned to be removed from a future JDK release
NPM dependency "@js-joda/core" has installed version "1.12.0"
"3.2.0" was required by jar:file:/Users/den/.m2/repository/cljs/java-time/cljs.java-time/0.1.18/cljs.java-time-0.1.18.jar!/deps.cljs
shadow-cljs - HTTP server available at
shadow-cljs - server version: 2.11.18 running at
shadow-cljs - nREPL server started on port 8877
shadow-cljs - watching build :app
[:app] Configuring build.
-> build target: :browser stage: :configure
<- build target: :browser stage: :configure (4 ms)
[:app] Compiling ...
-> Resolving Module: :main
[:app] Build failure:
The required namespace "goog.result" is not available, it was required by "shadow/xhr.cljs".
looks like you are trying to use an older shadow-cljs version with the new cljs release?
need to bump shadow-cljs if you want to use cljs 1.10.844, which will also fix this problem
I think I’m on the newest version
✨ Done in 0.35s.
➜ z1 git:(simple) ✗ yarn global add shadow-cljs
yarn global v1.22.5
[1/4] 🔍 Resolving packages...
[2/4] 🚚 Fetching packages...
[3/4] 🔗 Linking dependencies...
[4/4] 🔨 Building fresh packages...
success Installed "[email protected]" with binaries:
- shadow-cljs
✨ Done in 0.57s.
that said, looks like shadow-cljs does not print its version at the beginning of the build process
Getting the error
The required JS dependency "@material-ui/core/SnackBar" is not available, it was required by "athens/views.cljs".
when building on Linux but not MacAlso not having a problem importing other core
components like
["@material-ui/core/ExpansionPanel" :as ExpansionPanel]
["@material-ui/core/ExpansionPanelDetails" :as ExpansionPanelDetails]
["@material-ui/core/ExpansionPanelSummary" :as ExpansionPanelSummary]
["@material-ui/core/Slider" :as Slider]
["@material-ui/core/Switch" :as Switch]
hmm, I think i figured it out. was importing SnackBar
instead of Snackbar
. interesting that this works on Mac but not Linux though!
Is it possible to have the out directory be the same as the directory the cljs files is in? So instead of a dist directory just compile a js file right next to the cljs file and keep the directory structure as is?
My end goal here is to introduce clojurescript to an existing node codebase gradually by compiling similar to how rescript (formerly reasonml) recommends right alongside each file. I was thinking it might help with adoption / testing if we were able to gradually compile certain features in clojurescript etc
Can shadow-cljs's repl integration work if the index.html is dynamically generated server-side? I have a deps.edn-based project that I am playing with and we typically generate our home page server-side. I can get everything to work correctly aside from any cljs-repl functionality.
hi thomas! Is it somehow possible to add a ring undertow websocket handler to the shadow-cljs dev server? We use sente for websockets in our app, and we tested sente with undertow, and this works. but somehow I seem not to be able to get it to work on the shadow http dev server.
I do recommend using your own server if you do this. :dev-http
is meant as a STATIC webserver and using a custom handler is not recommended