Alternative ways to define/instantiate adapters (Bring-Your-Own-Adapter)

[solidjs]

Alternative ways to define/instantiate adapters (Bring-Your-Own-Adapter)

[potatopotaro]

Yes I saw! Thank you good sir! I managed to get my own custom adapter working, with the exception of the "server/worker entry" (aka app.jsx within the solid-start package; webStream in my particular case).

I'm moving on to HTTP2 push now (e.g. https://developers.cloudflare.com/workers/examples/http2-server-push), trying to send assets ASAP.

I'll make sure to share my code with you at some point in discord, and likely a generalized cf worker adapter as a PR.

Thank you for all the badass work you do Ryan, cheers 🍻

[potatopotaro]

I think this is an area I can contribute to as well, so please let me know if this functionality is desired or if the team has an own approach they'd like assistance with.

[potatopotaro]

For those interested, it is possible to specify a custom adapter by providing an absolute path in the adapter field, like so:

// vite.config.js
import { fileURLToPath } from "url";
import { dirname } from "path";

const __dirname = dirname(fileURLToPath(import.meta.url));

adapter: `${__dirname}/custom-adapter.js`,

Both url and path should already be installed through solid-start and such. Your custom-adapter.js will need to emulate something like this.

[ryansolid]

I will make the change to import. However, leaving it wide open is another thing. I feel that would add complexity that unsure want to worry about at this point.

[ryansolid]

Ok I have made that change and published it now. So it should be a lot easy to load in custom adaptors.

I think we take the other suggestion under advisement but see no reason to rush towards that now.