This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
while we were doing the hoplon6 migration, we have deleted all of the pages except one and we were testing the results with only that
i was wondering if i could specify some kind of limitation to which pages do i want to render
i thought about sifting in only the relevant sources but since there are some common parts it's not obvious which sources do i need
my other idea is – similar to mocha --grep
– is to specify a page name regex to hoplon and it would only compile those pages
Hmh, I should probably try to get the new boot-cljs released soon. I'm thinking there are maybe three things to fix before that.
Cljs version comparison (1.7.100 > 1.7.48), some problem with cljs tests caused by shim ns, and displaying warnings prettily
Ah, and now that :output-dir is not always /out
it quite hard to se asset-path option manually
We need to either provide good documentation about how to properly do things
or support setting asset-path
I'm thinking it's easier to support asset-path option....
I'm thinking in 90% use cases people have files in public/
prefix and serve that as /
.
And in most cases good solution is to compile cljs to js/
and serve that as js/
.
There might also be some cases where user needs to use absolute asset-path
Like in dev build with a blog where different pages are using directories.
But perhaps current implementation already works, asset-path is set to sane default and user can override it using :compiler-options
It just needs a mention that output-to ends with {{id}}.out
instead of just out/
Or maybe we could append last part of output-to to asset-path
Though then we should have boot-cljs asset-path option so we don't mess with how cljs asset-path option works
I guess it would work the same, but the name makes sense
Boot-reload could use the same name
What would scriptroot option do?
Yeah it should be per module
Ah yeah
Really strange this cljs refresh bug. If I save app.core once, then changes in app.test work fine, but before that changes to app.test don't work.
I added "shim" ns to cljs.jar test and it still works
Both with cljs.build.api/watch and build
And identical cljs compiler options 😕
I wonder how cljs is reading anylysis cache for hello-world.core as that shouldn't be cached yet
And why boot doesn't use analysis cache
Does boot change timestamps for unchanged files?
Cljs writes and reads cache files directly from output-dir
And that dir shouldn't change between builds
With Boot-cljs Cljs reads some files from another dir
Ha, I managed to reproduce the issue with pure Cljs
Moving shim ns to separe folder and passing only that folder to cljs.build.api/build. Then having the real files in classpath.
I'm not sure if that's the problem
Besides, it should be in classpath already?
At least once cljs task has run?
The temp-dir contents are commited as resources
Hmm but I'm not sure if that's the problem.
There could be some bug in Cljs with handling cache file paths
I tried adding the folder with shim ns to classpath and that didn't fix it