jplhomer

8 ms·

1.
Lessons Learned from Four Months of Working Solo(jplhomer.org)
2 points by jplhomer 2y ago|0 comments
2.
by jplhomer 4y ago
Yes. We are working on it right now. If you are comfortable in Remix, that’s a great place to start. Everything from Hydrogen will be additive from there.
3.
by jplhomer 4y ago
We're working on a new version of Hydrogen which is powered by Remix: https://hydrogen.shopify.dev/roadmap/ It's nice to not have to build two meta-frameworks (along with docs and support) so Hydrogen can foc
4.
by jplhomer 4y ago
We'll be redesigning Hydrogen to be powered by Remix: https://hydrogen.shopify.dev/roadmap/
5.
by jplhomer 4y ago
Terrific update! You resolved the only two pain points I'd experienced (`tw` template literal and JSX pragma stuff). Out of curiosity: does the support for automatic JSX incur any startup or deployment penalty? I'd assumed Deno di
6.
by jplhomer 4y ago
Curious to hear more about your experience. We’ve optimized our latest themes (Dawn) as well as the Hydrogen demo store templates with SEO in mind.
7.
by jplhomer 4y ago
I do! As of this week, we're at stable v1 and out of developer preview. https://hydrogen.shopify.dev/
8.
by jplhomer 4y ago
Yep, we're planning to offer a `@shopify/hydrogen-ui` package with useful components and hooks. That work is in progress but not quite ready. We have a working prototype of Hydrogen deploying to Vercel, and we need to formalize it
9.
by jplhomer 4y ago
Certainly not out of the picture, but Cloudflare is a terrific solution for us right now.
10.
by jplhomer 4y ago
Hydrogen is purpose-built to be used for custom Shopify storefronts, correct. So you're communicating with Shopify's backend using helpers like `useShopQuery` https://shopify.dev/api/hydrogen/hooks/g
11.
by jplhomer 4y ago
That's good feedback. The directive approach relies much less on initial discoverability and tedious work which enables it, like naming each and every JS module a certain way up front. Instead, it relies on error handling and developer
12.
by jplhomer 4y ago
Correct, we're shipping with an initial version of React Server Components (RSC) that works in Vite and uses file suffixes. Hydrogen provides missing pieces to the current version of RSC, like data fetching and other dev tooling. We&#x
13.
by jplhomer 4y ago
Sounds like an explosive combination ;)
14.
by jplhomer 4y ago
Look for a blog post about Oxygen in the coming weeks! Initially, we're partnering with Cloudflare using Workers for Platforms [0] so Oxygen's runtime shares many of the same APIs you'd expect to see in a Cloudflare Worker [1
15.
by jplhomer 4y ago
Shopihydroreact? The name happens to pair nicely with Oxygen, our hosting platform: https://shopify.dev/custom-storefronts/oxygen
16.
by jplhomer 5y ago
Des Moines, IA software engineer checking in! It’s great. Not terribly exciting, but the hours/culture/WL balance others have described holds up.
17.
by jplhomer 5y ago
Not in particular — this was meant as way to clarify that Hydrogen isn't a drop-in solution for e.g. Android or Unity apps. Though we're exploring the use of Hydrogen + React Native > Android/iOS.
18.
by jplhomer 5y ago
+1 to what Dan said! `*Provider` handling of client components is a workaround for lack of server context right now. When server context ships, we'll migrate to it in Hydrogen. There are several other things that are specific to Hydrog
19.
Building an in-browser image editor with React(product.voxmedia.com)
1 points by jplhomer 6y ago|0 comments