Migrate from Webpack to Remix
Apps that depend on Webpack loaders and plugins weren't able to incrementally migrate to Remix. Until now!
Edited videos available on this playlist: https://www.youtube.com/playlist?list=PLXoynULbYuEC36XutMMWEuTu9uuh171wx Learn more at https://remix.run/conf/2022 Chat at https://rmx.as/discord 00:00:00 Starting title 00:40:00 Michael Jackson keynote 01:10:00 Henri Helvetica on webpage test 01:35:00 Shaundai Person on remix as browser framework 01:54:45 Erik Rasmussen on state machines 02:45:15 Anthony Frehner on Remixing Hydrogen 02:59:50 Ryan Dahl on deno + remix 03:21:40 Nick Small on remix-three 03:29:20 Erick Tamayo on web vitals 03:38:00 Scott Smerchek on stale-while-revalidate 03:43:25 Lunch 05:55:00 Vic Vijavakumar on social good with low code 06:07:51 Ben Wishovich on remix + rust 06:15:10 Greg Brimble on Full Stack Fast: Data on the Edge 06:24:00 Arisa Fukuzaki on ui + ux 06:48:10 Daniel Weinmann on remix-forms 07:06:30 Jon Jensen on incremental remix 08:00:00 Sarah Dayan on search with algolia + remix 08:24:00 Dennis Beatty on switching to remix at neighbor 08:45:00 Closing Notes
This video shows how to configure VS Code to debug your Remix loaders and actions. NOTE: You can now use the `debugger` statement instead of the external `debug()` function. I tried this before, but it didn't work. Not sure why it works now. You still can't set a breakpoint inside a route module, but you can add `debugger` statement and it will break there. You can then step through your code. I will be re-recording this video with this new info. Get the launch configuration here: https://rmx.fyi/debug
HTTP Caching is a web fundamental every web developer should eventually learn. The quickest way to a slow website is to not understand caching and ofc, the best way to make your website fast is to take advantage of it. In this video we'll explain the basics of HTTP caching, how web browsers respond to it, and how CDNs take advantage of it, by building a bare-bones Node.js server and then quickly see how to specify caching headers in a Remix App.
Have you heard about our new Remix Stacks template the K-pop Stack? It combines Remix, Supabase, Tailwind, and more to give you a note creation app with auth to help jump start your own Remix creation. Check out how to make it your own and get it deployed to fast and free! Repo: https://github.com/netlify-templates/kpop-stack Blog Post: https://www.netlify.com/blog/deploy-your-remix-supabase-app-today!/
We will walk through a simple demonstration of a remix application using nested routes and parameterized routes. The use of nested routes helps me with component design and separation when architecting an application. Parameterized routes / Dynamic Routes contain state information that can through the parameters that are defined on the route. This provides powerful flexibility when designing your app and app's components. Putting the two together in an simple solution to be a reference when you build something amazing. Speaker bio: Aaron is an Information Technology Strategist, Thought Leader, and Diversity and Inclusion Trailblazer - Founder & CEO of Clearly Innovative. He believes technology and in his case coding is an enabler and an equalizer. Aaron has focused a large part of his career training and developing individuals who want to get into tech but cannot find the opening; through the apprenticeship program he ran at Clearly Innovative, teaching web and mobile development at Howard University, and the free technical videos on his Youtube Channel he just want to help others get a seat at the table of tech and innovation. Learn more at https://remix.run/conf/2022/speakers/aaron-k-saunders
Remix relies on CDNs and cache control headers to get the best web performance possible. Here we’ll compare various caching strategies, including Static Site Generation and Increment Static Regeneration, and compare the tradeoffs.