Having a weird issue with devcards on a particular instance. Seems that for some reason it sometimes does not get included on the resulting js.
@shaun-mahood: No, it's for a Chrome plugin, so lein chromebuild. Worked just fine on my desktop, testing it today from the laptop it's wonky.
As in sometimes it ends up there, sometimes it doesn't.
:whitespace for optimizations.
Up until recently it worked if I did a clean first, then full rebuild. It just stopped working that way.
Are you following the instructions from the readme on using devcards without figwheel or as a standalone website?
@shaun-mahood: Yes. I've been using it for a couple of days, only started getting this issue today. Can't figure out what changed.
Nothing relevant on the project file, I only added a new namespace for more tests.
@ricardo: Weird. You could try changing the optimizations and see if that makes a difference. I'm wondering if it's a chromebuild specific issue.
@shaun-mahood: I considered that, but it seems that all it does is call
cljsbuild and move some files to a specified folder. https://github.com/clumsyjedi/lein-chromebuild/blob/master/src/leiningen/chromebuild.clj#L37-L40
The files it moves wouldn't have an effect on this. They're stuff like the manifest.
So whatever's happening should be at cljsbuild time.
Can you share it at all? I'd be happy to try it on my machine and see if I can see anything obvious. Outside of that, not sure I have any bright ideas.
Sure, this is supposed to be open source when I'm done with it. Let me bash my head against this wall a bit more before I bother you, then I'll post it.
Hmpf. And this happens even from the repository version, if I stash all changes and clean.
I guess it's time to push, switch machines and confirm it's environment-specific.
Yeah, nevermind. Get it on the desktop now as well. Grr. Happy fun git-bisect time.
Did we get an answer on start-devcard-ui!* being private?