This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-09-17
Channels
- # announcements (1)
- # aws (7)
- # babashka (5)
- # calva (56)
- # cider (13)
- # clj-commons (1)
- # clj-kondo (12)
- # clj-yaml (35)
- # clojure (84)
- # clojure-europe (93)
- # clojure-sg (2)
- # clojure-uk (1)
- # clojurescript (10)
- # conjure (37)
- # core-typed (1)
- # cursive (31)
- # duct (1)
- # figwheel-main (4)
- # fulcro (2)
- # holy-lambda (2)
- # humbleui (3)
- # membrane (118)
- # off-topic (46)
- # pathom (8)
- # podcasts-discuss (5)
- # releases (2)
- # rewrite-clj (13)
- # sci (27)
- # shadow-cljs (17)
- # tools-deps (12)
hi, I connected cider-cljs and I have REPL, but my source buffer says cider[not connected], and I cannot use commands like M-. (jump to definition) or C-z (go to REPL). the REPL works all right though. and the sesman-browsser shows my session with suspicious message (pending-cljs):
1: projects5/bubrary-gui:localhost:9000 linked-to: proj(~/projects5/bubrary-gui/) objects: cider-repl %s(pending-cljs)
I'm trying to make the dev-http serv index-files from subdirectories for instance where /index.html would serve / and /app/index.html would serve /app
is there any configuration that I am missing?
no, it just assumes push-state routing. meaning your client doing the route logic with a base index.html
yes, I read that in the docs - i wish to have a static landing page on the root and the SPA in /app is it possible to configure this scenario?
no it still renders /index.html
:thumbsup:
Trying to get rid of a warning when I deploy my app:
:WARNING: You required cljs-devtools library in a project which is currently compiled with :optimizations :advanced.
remote: You should remove this library from non-dev builds completely because it impedes dead code elimination.
remote: The best way is to use :preloads compiler option: .
remote: To silence this warning please set :silence-optimizations-warning config key to true.
remote: More details: .
My shadow-cljs config is:
{:nrepl {:port 7772}
:builds {:app {:target :browser
:output-dir "target/cljsbuild/public/js"
:asset-path "/js"
:modules {:app {:entries []}}}
:dev {:target :browser
:output-dir "target/cljsbuild/public/js"
:asset-path "/js"
:modules {:app {:entries []}}
:devtools {:preloads [day8.re-frame-10x.preload]
:watch-dir "resources/public"}
:dev {:closure-defines
{re-frame.trace.trace-enabled? true
day8.re-frame.tracing.trace-enabled? true}}}
:test {:target :node-test, :output-to "target/test/test.js"
:autorun true}}
:lein true}
I thought taking the dev tools out of the ‘app’ build (used for deployment) would resolve the issue - any help appreciatedat deployment this script is run:
#!/usr/bin/env bash
npx shadow-cljs release app
lein uberjar
I'm guessing that somewhere in your code you directly require something from devtools.*
?
splitting into a :dev
build is not idiomatic. you can configure dev/release specific things in the main config. see https://shadow-cljs.github.io/docs/UsersGuide.html#_release_specific_vs_development_configuration