Ecosystem and Frameworks: My Role at Netlify
I'm curious what frontend frameworks you're all interested in these days? Powerful meta frameworks have been built using libraries like Vue and React. Next.js comes to mind: Remix is a new contender, and we have other notable projects like SvelteKit, Astro, Eleventy, etc.
I'm on the ecosystem team working on frameworks in my new role at Netlify. Our job, at the moment, because I'm sure it will evolve, is to ensure whatever you deploy to Netlify deploys seamlessly. I'm not saying this to promote Netlify, although it is incredible. It's to express my excitement at this type of role.
I need to know/learn how all these frameworks work, which is exciting.
For example, if you weren't aware, Netlify released their Edge functions offering a couple of weeks ago. My coworker Salma has a great post about them.
We're all living on it. But what exactly is The Edge?
My other awesome coworker Eduardo released a deep dive article about Netlify Edge functions if you want to check that out as well.
I was looking into an issue with Netlify Edge functions within the Remix framework.The https://github.com/remix-run/remix repository on GitHub
One of the core team members had issues getting Edge functions to work with Remix. After some fun detective work, I figured out the issue. TLDR; a polyfill wasn't web standards compliant, so the bug only occurred when Edge functions were enabled because Deno is compliant. In contrast, regular serverless functions use the non-web standards compliant polyfill in Node.js land.
It's not fixed yet, at least when writing this post, but the Remix core team is working on it. It was tons of fun to figure things out publicly and share my findings, as this is open-source baby!
I'm stoked to continue exploring this role, working with the developer community, our customers, my coworkers, and open-source community!
Photo by Alex Kondratiev on Unsplash