This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-04-17
Channels
- # announcements (1)
- # babashka (94)
- # beginners (76)
- # calva (24)
- # cider (24)
- # clj-kondo (1)
- # cljs-dev (16)
- # cljsrn (45)
- # clojure (135)
- # clojure-europe (9)
- # clojure-france (5)
- # clojure-germany (2)
- # clojure-italy (12)
- # clojure-losangeles (13)
- # clojure-nl (3)
- # clojure-portugal (54)
- # clojure-uk (20)
- # clojurescript (55)
- # conjure (67)
- # core-async (5)
- # cursive (2)
- # datomic (10)
- # docker (7)
- # duct (22)
- # emacs (16)
- # fulcro (34)
- # graalvm (15)
- # hoplon (1)
- # instaparse (1)
- # jobs-discuss (3)
- # juxt (94)
- # luminus (1)
- # meander (4)
- # off-topic (13)
- # pathom (4)
- # pedestal (1)
- # ring (3)
- # ring-swagger (2)
- # shadow-cljs (61)
- # spacemacs (17)
- # specter (2)
- # sql (23)
- # xtdb (33)
Hello! anyone have any experience with shadow-cljs and tailwindcss?
I am having trouble getting tailwindcss to load and be usable
Hi all, anyone had any luck getting shadow-cljs
, deps.edn
and cider
working nicely together?
Things work perfectly just using shadow-cljs
and cider
but when I try to use deps.edn
as well the cider-jack-in-cljs
stops working.
I select cider-jack-in-cljs
-> clojure-cli
and then my build and I get the following error.
error in process filter: The shadow-cljs ClojureScript REPL is not available. Please check
@sofra that is not an error from shadow-cljs and I can't help with the cider parts sorry
should be easy to do though. just add shadow-cljs to deps.edn and then start as normal
@mbbailey96 whats the issue? you just load the tailwind css file? shadow-cljs doesn't need to know anything about that?
I usually use cider-connect-cljs
I launch a watch process
before
Question about https://code.thheller.com/blog/shadow-cljs/2017/11/06/improved-externs-inference.html I'm getting Cannot infer target type in expression (. c__41761__auto__ -ratomGeneration)
when using r/with-let
-form in reagent (in a react native project). The article would suggest that I should be use to tag it using ^clj
but this does not help. Is this a known issue? I can always revert back to (let [] (fn [] ...))
and it works.
the problem is in the code the macro generates. so you cannot typehint it properly without modifying the lib
In what case does this happen? I'm running Reagent test suite with Shadow-cljs and extern inference so it should be okay.
But this probably requires version 0.9.1
OK, maybe I need to update my libs then
Yeah, this project is at 0.8.1, I'll update it. Thanks for your fast replies!
https://github.com/reagent-project/reagent/blob/master/src/reagent/ratom.clj#L48 that has a ^clj
tag so should work
Yeah, and that change was released in 0.9
Updated reagent to 0.9.1 and it works. Thanks!
@thheller I am getting a js-invalid-requires message on watch, specifically pointing out a require located in the index.js file of tailwindcss. Docs recommended an NPM install of tailwind so that's what I did. When I view the app in browser, it give me "failed to load" errors again citing the 'require not defined'. I tried changing :js-options :js-provider to :require but that only fixed some of the issues. It's the closest I've gotten to a working build
@mbbailey96 I like the shadow-cljs + tailwindcss workflow described in this YouTube video: https://www.youtube.com/watch?v=_CTTbC6owS0
@iradavidhale, so do I! That's where I got the idea for tailwind from, but if you look at his git repo, he has the pulled tw css file already, not the node_modules. Errors like the ones I described above are only happening when I import the tailwind node module. Also, @thheller, I forgot to mention. I get the same failed to load in browser for
react
and react-dom
@mbbailey96 I don't know what you are trying to do. tailwind is a css file and doesn't have JS?
As far as I understand when reading through the install docs on the official tw website, it calls for an install through npm or yarn, then adding @tailwind base (and others) to your site.css file.
Ah, then I gravely misunderstood the task at hand. Sorry to bother you @thheller
or you just skip the custom build stuff and just use <link href="
Yep! Just read further into the site, and found that little gem.
My apologies, didn't mean to ask stupid questions
Is there anything that would prevent shadow from loading a cljs namespace in a resources/
path? I have resources
as a source path in my deps.edn
and :deps true
in shadow-cljs.edn but when I try to require public.code.myns
which is located in resources/public/code/myns.cljs
I'm getting "The required namespace "public.code.myns" is not available"
oh right. resources/public
is filtered by default because it is were people usually output there code to
Yeah, kinda a weird situation where I have static code files I wanted to eval with a bootstrapped compiler, there are probably better ways to do it but I was doing it this way as a shortcut for now
Been getting lots of those recently https://gist.github.com/spacegangster/c3ffcb526598c40cb03bfd37a120c436 Internal compiler error
could be ES6 forms again?
the opposite – porting some legacy))
I haven't worked in direct JS support in a while so I imagine that it has several issues
Yes. This time adding terminating semicolons helped.
Nope, premature celebration, still digging the sources.
But yeah, that’s something about Closure, not Shadow