Add @remix-run/oxygen package

[frandiox]

Most of this comes from @remix-run/cloudflare and @remix-run/deno. This still uses KV asset handling for for local dev since we depend on Wrangler. We can remove that dependency once we migrate to mini-oxygen (I think?).

RE: #70

[jplhomer]

PUMPED. A few thoughts:

• Nit on the name. It would be nice to have a single @hydrogen/remix package (tho that namespace is taken) for all handler things AND query abstractions, etc. Not a deal-breaker, but we don't need to decide this now.
• We should sync up with @GustavoCaso and friends to see how asset handling is changing in the Oxygen roadmap, and determine what we should be building

[frandiox]

Shouldn't @hydrogen/remix be a different package with all the Hydrogen stuff + optional Oxygen stuff re-export?
Like, it's still possible to deploy raw Remix to Oxygen without anything from Hydrogen, right?

[jplhomer]

Like, it's still possible to deploy raw Remix to Oxygen without anything from Hydrogen, right?

This is what I assumed, but I think SLT does not want us to optimize for this use case cc @benjaminsehl

[frandiox]

@jplhomer Let's say we add a new @hydrogen/remix (or a different name) package that exports all the Hydrogen utilities and re-exports from @remix-run/oxygen, but it wraps createRequestHandler to add extra stuff to the loaders context, such as storefront client, language, and the buyer-ip thingy.

The @remix-run/oxygen package would probably be owned by the Oxygen folks to make sure it works with CFW and other platforms, and perhaps to add same-origin asset proxy if needed.

Would that work or do you have something else in mind?

[jplhomer]

@frandiox sounds good to me!