Julian Sigmund
Julian Sigmund
> The cast to `any` is a little unfortunate but it's something I'd be willing to add by hand if there was no other option - maybe some documentation for...
Ahh i think you have to await locals.session.set() in your endpoint! Since switching to webcrypto those methods are async.
You'll have to use the session store somewhere in your application via `$session`. This error would also appear if you'd use the unmodified version and `session.set` or `session.update`. The set...
Hey! I'm by no means a security expert, but the algorithm used `aes-gcm 128` should be cryptographically secure and sufficient for your needs!
Sorry for the late response, was quite busy. I think you should be infinitely incrementing the secret ID, just to be sure.
@hayes Thank you very much for your investigation. I structured it much like you did in the example repo, which means i should be able just switch to a dynamic...
@hayes It seems like the esm folder wasn't published to npm, at least i can't see it in my node_modules folder.
I cloned giraphql and tested it locally with the esm build, works perfectly!
> Sorry, small oversight on my part on how the release script works. Should be fixed now No problem, thank you very much! I tested it and at first it...
The current Implementation of esm seems to be slightly wrong. It's working fine with vite in dev. But node still tries to import the cjs version. I think because of...