@dnolen working on reloading preprocessed and compiled js. Current problem is compiler is emmiting module names defined with const

@bhauman that seems goofy

@dnolen Is that in GCL or our code?

@bhauman I think just a mistake in my demo?

@bhauman yep

where?

just need to switch those

Components.js

I’m using const instead of var

oh i see it now

darn thanks

@bhauman np, exciting 🙂

can also probably be solved by specifying :language-out, no?

@anmonteiro in theory, but I haven’t been able to get that to work

@dnolen the Circle class definition is being emmitted as a const

@bhauman this might be a Closure bug, or a weird ES6 spec thing

so we don't use classes I guess

@bhauman I just tried over here

I don’t see the class being exported as const

hmmm really?

@bhauman definitely do not

this is using my es6-demo

oh yeah it's not a const ... it's a "class" which throws on redefinition

@dnolen so it behaves as a const

so again no classes

@bhauman not so fast 🙂

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/class

you just need to assign to a var

gotcha

so much for JS being simple

whew ...

well that looks weird as heck

@dnolen and it freaking works!!!!

amazing

and in a year will be the most asked question "Why don't classes reload?"

@bhauman in all seriousness this is great news

between this feature, npm module loading support via Closure, and the externs stuff I think 2017 is going to be “ClojureScript is a pretty awesome JS tool"

Awesome, there is progress on externs?

yes I have some working prototype code

sweet!!!!

damn

and I merged some missing bits from Maria Geller’s GSoC work

probably a a couple of Fridays of my time and we can probably have something testable on master

@bhauman are you planning to ship the Figwheel tweaks anytime soon?

just let me know when you do - I would like to write a post about it - possibly an updated http://clojurescript.org guide

There are other changes that I need to make in order for this to be workable.

:watch-paths, :compile-paths, etc

gotcha - no rush

would like the post to be something people can try immediately w/o hassle

also I'm cheating a bit, in that I'm relying on the current convention of where the output file of a foreign lib is placed

@bhauman right that’s probably going to change

yeah I figured

necessarily so

as it's not robust

especially if we’re going to integrate with random JS stuff

we need to preserve paths to avoid clashes

absolutely

thats why I know its bad

I was thinking that you may want to preserve paths from the root of the project

or hash them

it’s pretty high on the list of issues - since a lot of stuff is blocked around it

probably won’t mess with hashing - just makes debugging harder

my underlying issue is that I have to have the :provides from the file

preserving path based on the root of the project is probably the simplest thing

or the $ seperated convention could work as well

we don’t control the module naming convention

Closure implementation detail

no I meant that instead of recreating the whole output path you could concat into a single dir with $

unlikely to do that

that way we can know the difference

cool

just makes integration with browser tools uglier

harder to undersatnd

gotcha

for stuff that doesn’t follow classpath conventions

location relative to project root is probably the best we can do

@dnolen I think I'm going to block on that issue as well

yes working around it is inadvisable 🙂

http://dev.clojure.org/jira/browse/CLJS-1718

gotcha