Andreas Rozek

My solution: instead of modifying the source of "preact-custom-components", I got rid of the duplicated child elements using a "trick" mentioned in [issue #32](https://github.com/preactjs/preact-custom-element/issues/32): > for a component with inner...

sorry for the late response, but I had to meet a submission deadline for another project first... I'm running Quant-UX in a local docker container...

Just in case that anybody reads this: NW.js 0.64.0 is the lastest version I got running under macOS 10.13.6 (High Sierra) on my old Mac mini mid-2011

can't you just use `this.base.parentElement` after `componentDidMount` ran? That's what I am doing in my code...

indeed, I also made my own fork and reverted [086ebe1](https://github.com/karpathy/nanoGPT/commit/086ebe1822791b775e951b4b562fbb7131d83cc2), resulting in a dramatic speedup on my Mac mini M1!

> Thanks to this thread I got it working on my M2 MacBook Pro - I wrote up some detailed notes here: https://til.simonwillison.net/llms/nanogpt-shakespeare-m2 Simon, thank you very much for your...

I do not think that this modification is required any longer: `config/eval_gpt2.py` already contains a line with `init_from = 'gpt2'` which overwrites the setting in `sample.py`. This issue may therefore...

Oops... Have you ever tested or used component attributes? Unless I've fundamentally misunderstood their concept, they were completely broken - but fixed now

Ah, I got it: you wanted scope properties to be set from other prop.s whose names are given by attributes. But, isn't this already possible using ```

Good morning (from Germany)! I see your points (and goals) although I needed `v-if` at the time I implemented it and had no time to "implement variable name parsing" or...