Clojurians
#cljs-dev
<
2017-09-21
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

dnolen07:09:35

@mfikes cool, will try to find time to look at that tomorrow

lxsameer15:09:07

@dnolen can you please give me a brief info about this https://dev.clojure.org/jira/browse/CLJS-2298

mfikes17:09:02

@lxsameer CLJS-2298 alludes to a similar feature in Clojure, where a user.clj file at the root of the classpath will be auto-loaded when starting a REPL. Where Clojure users often have an (ns user) with useful definitions, ClojureScript users might more often define a (ns cljs.user) namespace in that file, but that is really just a convention, orthogonal to the fact that user.(cljs|cljc) files in the root of the classpath should be automatically loaded upon REPL startup.

lxsameer19:09:01

@mfikes so basically try to load cljs.user instead of user if there was such a namespace

mfikes19:09:23

Not exactly

mfikes19:09:00

Any user.cljs and user.cljc files that reside at the root of the Java classpath should essentially be subjected to load-file, I would imagine

mfikes19:09:56

I would actually consult with what the bare Clojure REPL does with user.clj for specifics

alexmiller19:09:02

iirc it’s not a REPL feature, it’s part of the Clojure RT to find and load user.clj from the classpath if it exists

alexmiller19:09:13

prob has never been updated to look at user.cljc, so that’s a reasonable enhancement

bhauman23:09:39

I've been working on getting Figwheel and ReactNative to play nicely, and its starting to become apparent that the targets for JS are just going to keep coming, and maybe we should think in terms of a separate/pluggable post compilation step that packages up a :main entrypoint for a specific platform

bhauman23:09:58

or perhaps multimethod that switches on :target

bhauman23:09:38

apologies if I've missed conversations about this very thing