This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-16
Channels
- # aws (6)
- # beginners (129)
- # calva (9)
- # cider (4)
- # cljs-dev (2)
- # clojure (41)
- # clojure-beijing (2)
- # clojure-dev (3)
- # clojure-spec (23)
- # clojure-uk (46)
- # clojurescript (38)
- # community-development (20)
- # core-async (4)
- # cursive (12)
- # data-science (7)
- # datascript (13)
- # datomic (15)
- # duct (11)
- # emacs (18)
- # figwheel-main (5)
- # fulcro (26)
- # off-topic (4)
- # pathom (28)
- # pedestal (3)
- # reagent (8)
- # reitit (6)
- # shadow-cljs (32)
- # specter (3)
hmm.. Okay totally n00b question. Since shadow-cljs allows the use of nodejs or browser REPL, are there any actual configurations that would really benefit from using Lein or is that option more for people who simply prefer it?
I haven't got an opinion either way and just getting to use both so.. just curious 🙂
most people use lein
when they have some other CLJ code (eg. server-side) they need to work with as well
nothing build related is affected by whether you use lein
, tools.deps
or shadow-cljs standalone
ah I see. So as a configuration for a full stack project.
Yeah I'm actually gonna playaround using NodeJS instead of just JVM BEs but I'm going to be using lein on other projects in the future so I set it up just to familiriaze myself
but it also fine to use shadow-cljs.edn
for CLJS and lein
for CLJ completely separate. that is what I do.
hmmm.. hmmm.. I see! Well this clarifies nicely 🙂
hmm.. some clarifications about building a node scripts 🙂
So let's assume I have arbitary project foo where I'm defining a core.cljs having a main function
Does this seem to be in order? Am I correct to assume that next thing leiningen needs is a notion of where the sourcecode files are?
but yes you need :source-paths ["src"]
or so in project.clj
and the file located in src/foo/core.cljs
(or whatever your source path is)
like previously said, it's likely I need to use it in the future and just thought I might as well begin now
I know it's additional and without familiarity just adds complexity currently 🙂 that's why ask does it actually have additional benefits
yes, I've noticed 😄
but since I started configuring might as well check it trough. Write a memo about it and then move in to what I actually use 😄
I hate to just leave stones unturned if I've started. So yeah. I'll just verify it's in order
okay verified, time to strip the clunkyness off
basically the only difference is that :source-paths
and :dependencies
are either in shadow-cljs.edn
or project.clj
yup. I'll add Leiningen when I'm actually using some non JS based BE or have more bigger production environment at hand
I haven't really even Clojure before. Only Common Lisp before 😄
As usual, when you start you really have too many options and not really an idea how to filter the useful parts of the information
Yeah I can dig that. Sometimes I throw up into my mouth a bit when I look at what some of my webpack+others configurations have become like