`dump` on server clears cache against documentation suggestion. about metapatcher

[muratgozel]

Do you call .dump() in browser environment? I'm just trying to find the most sensible solution. The .dump() is for server side rendering and we may actually could just do:

    dump(): string {
        if (this.isDomAvailable) return ''

        const data = this.memory.join('\n')

        return data
    }

[indifferentghost]

Current workaround is using memory directly: metapatcher.memory.join('\n').

[muratgozel]

There should certainly be a check for dom while calling dump. Thank you for the PR @indifferentghost I will merge it shortly.

[muratgozel]

@indifferentghost I understand you use .dump() server-side as it should be but what problem do you have with its clearing cache? Server renders happen once per request and so it just dumps once and clears itself. Can you elaborate the problem here?

The way i use it is simply:

import.meta.env.SSR ? metapatcher.dump() : ''

[indifferentghost]

Hey, I'm using it as middleware for keeping head state across endpoints, many of these use the same head, but a few of them are different. It's useful for me to keep state rather than a finished dump.

[indifferentghost]

I don't see why it shouldn't though. I don't, nor do I foresee using it in the browser.

[muratgozel]

It's just because it's meant to be used in server side, i mean the dump method. we are able to use html dom like a memory in browsers so i would like to keep it as much as possible. anyway, i released the new version, it should be fixed now. thank you for the collaboration @indifferentghost