home.social

Search

1000 results for “kitten_tech”

  1. 🥳 New Kitten¹ Release

    • Fixed: Errors in a project’s _main.script.js_ now cause a hard crash without retry attempts. The errors are also now better classified and communicated.
    • Housekeeping: Removed unmaintained dev dependency, updated supported ES versions to esnext and simplified jsconfig.json.

    Full change log:
    codeberg.org/kitten/app/src/br

    Enjoy!

    :kitten:💕

    ¹ kitten.small-web.org

    #Kitten #KittenReleases #SmallWeb #SmallTech #web #dev

  2. @kitten
    I'm still considering if I even want to go to @emf UK is not in Schengen, so traveling will just be annoying as well as long and costly...

    #emf #emf2026

  3. 🥳 New Kitten release

    Several but fixes, thanks to wunter8 (codeberg.org/wunter8):

    • Default socket doesn't work when testing with a local mobile device (codeberg.org/kitten/app/issues)
    • Apostrophes in the text content of <if> tags can cause problems (codeberg.org/kitten/app/issues)

    Also, there’s now a canonical place to initialise state-maintaining child components when using the new (and still undocumented) class-based Kitten Component system. Until it’s all documented, please refer to this:

    codeberg.org/kitten/app/issues

    Enjoy!

    :kitten:💕

    #Kitten #KittenReleases #SmallWeb #SmallTech

  4. 🥳 New Kitten Release

    I just reworked the fix for this to simplify the Kitten renderer (as this fix introduced a regression with components getting instantiated multiple times due to the fall-through logic between asynchronous and synchronous rendering). The renderer now treats every component render function as asynchronous, thereby avoiding the issue entirely.

    kitten.small-web.org

    Enjoy!

    💕

    #Kitten #KittenReleases #SmalWeb #SmallTech #web #dev #components #async #rendering

  5. 🥳 New Kitten Release

    This one fixes a bug that you would have encountered had you had an asynchronous component (component with asynchronous render method) nested more than one-level deep within synchronous components.

    (Kitten’s html renderer transparently supports both synchronous and asynchronous render methods.)

    So, this (taken from my unit test), for example, works correctly now:

    ```js
    class AsynchronousOtherName extends KittenComponent {
    async html () {
    await new Promise(resolve => setTimeout(resolve, 10))
    return kitten.html`<i>Balkan</i>`
    }
    }

    class SynchronousName extends KittenComponent {
    /* NOT async */ html () {
    return kitten.html`<strong>Aral</strong> <${AsynchronousOtherName.connectedTo(this)} />`
    }
    }

    class SynchronousTemplate extends KittenComponent {
    html ({ SLOT }) {
    return kitten.html`[Before slot]${SLOT}[After slot]`
    }
    }

    class MyPage extends KittenPage {
    html () {
    return kitten.html`
    <${SynchronousTemplate.connectedTo(this)}>
    <h1>This should render all at once after a short delay.</h1>
    <p>Hello, <${SynchronousName.connectedTo(this)} /></p>
    </>
    `
    }
    }
    ```

    Enjoy!

    :kitten:💕

    kitten.small-web.org

    #Kitten #KittenReleases #SmallWeb #SmallTech #web #dev #JavaScript #NodeJS #async #render