This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-28
Channels
- # babashka (29)
- # beginners (179)
- # bristol-clojurians (1)
- # calva (9)
- # chlorine-clover (47)
- # cider (57)
- # clj-kondo (1)
- # cljs-dev (13)
- # clojure (241)
- # clojure-europe (9)
- # clojure-nl (4)
- # clojure-norway (88)
- # clojure-spec (4)
- # clojure-uk (15)
- # clojurescript (211)
- # clojutre (1)
- # community-development (8)
- # core-async (1)
- # datomic (31)
- # figwheel-main (33)
- # fulcro (29)
- # ghostwheel (6)
- # graalvm (11)
- # graphql (12)
- # instaparse (4)
- # jobs (1)
- # jobs-discuss (17)
- # leiningen (7)
- # malli (6)
- # meander (38)
- # off-topic (208)
- # onyx (6)
- # re-frame (23)
- # reagent (8)
- # shadow-cljs (61)
- # spacemacs (10)
- # sql (5)
- # yada (5)
:bundle-cmd
command templates will now have :final-output-dir
and :final-output-filename
in addition to :output-to
and :final-output-to
AND I added better logging when a bundle command fails so that you can see the output of the failed command
AND finally I added an :auto-bundle
figwheel option which can take either a :webpack
or :parcel
keyword
^{:auto-bundle :webpack} {:main example.core}
is a complete config for working with NPM
@bhauman I realize it’s probably not a priority, but out of curiosity: do you expect yarn to work as more or less drop in replacement of npm? I prefer yarn but I’m probably in the minority
back in the day, npm was a huge mess and it was causing all sorts of weird issues and non-repeatable builds… yarn was a life-saver back then… I believe they’ve fixed it now (but I’m sticking with yarn)
@bhauman Loving the latest features! I upgraded our ten thousands of lines cljs project to 0.2.6, build and auto testing works great.
Awesome 🔥 Thank you.
I’m trying to configure the project using parcel
with the next config, but I got some spec errors Unknown map key:
:final-output-filename` and :final-output-dir
` Did I set up something wrong?
^{:open-url false
:watch-dirs ["src"]
:final-output-dir "public/assets"
:final-output-to "public/assets/app.js"
:final-output-filename "public/assets/bundle.js"}
{:main example.core
:target :bundle
:output-dir "target/public/assets"
:output-to "target/public/assets/app.js"
:bundle-cmd {:none ["npx" "parcel" "build" :output-to
"--out-dir" :final-output-dir
"--out-file" :final-output-filename
"--no-minify"]
:default ["npx" "parcel" "build" :output-to
"--out-dir" :final-output-dir
"--out-file" :final-output-filename]}
:closure-defines {cljs.core/*global* "window"}}
just supply :final-output-to
and figwheel spits it into :final-output-dir
and :final-output-filename
for you
Oh, thank you. I seem to have figured out the options. But I still could not configure parcel with tailwindcss and monaco-editor. Example with momentjs is very simple. I'll try again tomorrow
Or do I need to build assets separately from clojurescript application to e.g. vendor.js
If I can to configure everything, I will publish a step-by-step guide 😃
@U1EQNSHL4 I wouldn’t publish anything yet, let me go through some more iterations, because things are going to change probably as I learn more.
@U1EQNSHL4 I’d really like to understand what your hang ups are. Oh I think I understand, yeah you would probably need to run a tailwind watcher separately.
actually I think what you are going to want is some post build hooks https://figwheel.org/config-options#post-build-hooks
@bhauman I’m just trying to configure my library and usage example with parcel + figwheel-main instead of shadow-cls + rollup https://github.com/just-sultanov/clj-monaco Anyway thank you for your work on figwheel 👍