I'm curious, which is the line that makes the hot-loader react to fixture changes. is it https://github.com/lapanoid/hot-cosmos/blob/master/webpack.hot.config.js#L8?
Just published Cosmos 0.5.0 https://github.com/skidding/cosmos/releases/tag/0.5.0 - available on npm as well
@skidding Hah it was silly issue with lodash, but I still can not use cosmos 0.5.0. I build dev common js cosmos, now I am getting http://joxi.ru/eAO67wRipVDL2o. I guess playground changed and now I can hardly understand what is happening=(Is that valid "cosmos\examples\component-playground\component-playground.html" - http://joxi.ru/nAy6qybijDbOrZ ?
it's weird that props.component is undefined. it should contain the name of the component (see https://github.com/skidding/cosmos#component-lookup)
but the ComponentPlayground populates it automatically so you don't have to add it in the fixture: https://github.com/skidding/cosmos/blob/master/components/component-playground.jsx#L94
can you show me the fixturePath from the url for the screenshot you posted
?
Or you want me to host it?
I'm curious why did your project stop working though
the 3rd level is meant to be blank in the cosmos example, it's the same for me
May be you use something simple like https://github.com/lapanoid/hot-cosmos/tree/master/components ?
If you implement some simple example it would be really helpful for me to understand how it should work
after that I might learn a few things that need to be tweaked as well on the playground
still. you're saying it worked with 0.4.0 and doesn't work with 0.5.0?
Nothing special I just solved a couple issues, I dont deeply understand cosmos yet=(
should come with a few dummy components to showcase
