This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-27
Channels
- # beginners (24)
- # boot (10)
- # cider (6)
- # cljs-dev (8)
- # cljsrn (9)
- # clojure (46)
- # clojure-brasil (7)
- # clojure-dev (7)
- # clojure-germany (1)
- # clojure-uk (5)
- # clojurescript (22)
- # cursive (2)
- # datomic (19)
- # defnpodcast (2)
- # dirac (94)
- # emacs (4)
- # fulcro (20)
- # graphql (2)
- # hoplon (2)
- # lumo (9)
- # off-topic (2)
- # om (1)
- # re-frame (8)
- # shadow-cljs (66)
- # spacemacs (5)
- # sql (1)
- # test-check (3)
@thheller I'm trying to uberjar a node-library, that require thing doen't seem to find a js resource I'm requireing, I did (js/require (path/join js/dirname "fileinroot.js")), that fileinroot is inside the uberjar, but won't get extracted. Is this something known, or maybe implementing resolve for modules from node-library targets just what's needed.
I define it from leiningen in :reosource-paths -> lein uberjar and then it's in the .jar file
I want to create library and in another project call it. I can't see a better way of hosting cljs code than on clojars?
if you want to publish a CLJS library you just publish the code, not the compiled code
I have a cljs project that has a single vanilla js file that has exports that I want to use in cljs land. I require it and it all works, I just want to package the whole thing, and from a different project call the cljs functions that some also call vanilla js code
if you publish the .js file to a npm package you can just declare it in :npm-deps
for the lib
I have a few outstanding ideas for better JS interop since some things aren't as clean as I'd like
yes that's bit annoying, I've often thought about the other way around, just start uploading cljs stuff on npm.
we could easily add a bit of metadata to package.json
to declare :source-paths for a lib
yes, but a cljs compiler can just ignore the package.json and node ecosystem, go straight to node_modules read a package description file and resolve the classpath and files just with node_modules/packagex cut off.
yes, my idea is that this <root> would just have to be resolved differently for npm packaged cljs code.
just add package.json
"clojurescript":{"source-paths": ["src"]}
or something and that would work easily
nothing is node is named so if one file include another it must use the relative path
hopefully js people get their act together and enable at least react-virtualized/AutoSizer
at some point