DEV Community

Cover image for Ecosystem and Frameworks: My Role at Netlify
Nick Taylor
Nick Taylor

Posted on • Originally published at iamdeveloper.com

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.

My other awesome coworker Eduardo released a deep dive article about Netlify Edge functions if you want to check that out as well.

I bring this up because I get to continue to work in open source in my role at Netlify. For some background, Edge functions use the amazing Deno project, a modern open-source runtime for JavaScript and Typescript. We're big fans of OSS at Netlify. ♥️

Deno Land · GitHub

Deno Land has 60 repositories available. Follow their code on GitHub.

favicon github.com

I was looking into an issue with Netlify Edge functions within the Remix framework.

GitHub logo remix-run / remix

Build Better Websites. Create modern, resilient user experiences with web fundamentals.

Welcome to Remix!

We are happy you're here!

Remix is a full stack web framework that lets you focus on the user interface and work back through web fundamentals to deliver a fast, slick, and resilient user experience that deploys to any Node.js server and even non-Node.js environments at the edge like Cloudflare Workers.

Want to know more? Read the Technical Explanation of Remix

This repository contains the Remix source code. This repo is a work in progress, so we appreciate your patience as we figure things out.

Documentation

For documentation about Remix, please visit our website.

Also, please join our community on Discord.

The documentation is automatically generated on each release from the files in the docs directory.

Contributing

If you're interested in contributing code and/or documentation, please see our guide to contributing.

Code of Conduct

Please see our code of conduct for any questions…

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!

Peace peeps!

Photo by Alex Kondratiev on Unsplash

Discussion (2)

Collapse
rajeshroyal profile image
Rajesh Royal

Decoraters [ts], Generators, Memoization, Redux toolkit.

Collapse
xinusys profile image
XinuSys

The front-end world will continue to produce newer frames and frameworks: one factor being ease of mobile access, another being backwards - compatibility for older browsers ( where some CSS/JS breaks)

'Web standards' are great, but they get updated often, just as hardware evolves.