Improve adapter & runtime/deployment abstractions?

[gitblit]

Hi! I've noticed that Remix seems to have more dependency on adapters than some other frameworks and by that I mean, the choice of adapter can/does impact all the routes due to explicit adapter imports. Maybe I am doing it wrong, but I've seen this repeated in many tutorials/walk-throughs.

For example...

import { type ActionArgs, json, type ActionFunction, type V2_MetaFunction } from "@remix-run/cloudflare";

It would be great to import standard framework packages rather than adapter packages. This seems to tie me to a specific host. I did read the docs about polyfills, etc.... but I am wondering how this might work with the upcoming Vite build. SvelteKit scopes adapters as plugins (primarily, afaik) to vite.config.js so they can impact the build process but without requiring adapter-specific imports everywhere. I don't know if that is feasible for Remix or not, but it could be a nice improvement for portability and/or targeting multiple cloud hosts.

Similarly, Remix does not offer any abstracted/universal access to environment variables. Having an abstraction would be a nice quality of life improvement to avoid coding special handling for Cloudflare vs Node. Again, I don't know if the Vite transition plans or brings any improvement for something like this.