# frontend development Frontend development is the discipline of building and optimizing the user-facing parts of websites and web applications using technologies such as HTML, CSS, and JavaScript. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Two days in Barcelona with the Svelte community DevFeed: [Two days in Barcelona with the Svelte community]() Original publisher: [Read original article]() Author: Guilhem Le Mouel Published: 2025-05-20T00:00:00Z Content type: article Language: en Sources: [Windmill Blog]() Topics: [Svelte](), [frontend development](), [Development](), [JavaScript]() Tags: [2025](), [community](), [frontend-development](), [javascript](), [sponsor](), [summit](), [svelte](), [svelte-5](), [svelte-summit](), [svelte-svelte-summit-sveltekit-svelte-5](), [sveltekit](), [talks](), [windmill]() ### AI overview A first-hand account of attending Svelte Summit Spring 2025 in Barcelona, covering the event's community atmosphere, talks, and Windmill's decision to use Svelte for its frontend. ### Source excerpt A first-hand account of the Svelte Summit Spring 2025 in Barcelona, exploring the talks, community, and why Windmill chose Svelte for its frontend development. ## Announcing Inertia 2.0: Redefining Frontend Development for Laravel DevFeed: [Announcing Inertia 2.0: Redefining Frontend Development for Laravel]() Original publisher: [Read original article]() Author: Joe Tannenbaum Published: 2024-12-13T19:28:00Z Content type: release Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [frontend development](), [Front end](), [Single-page application (SPA)](), [React](), [Svelte](), [Vue.js](), [Object-relational mapping](), [Routing (disambiguation)](), [Core Web Vitals]() Tags: [async](), [core-web-vitals](), [deferred](), [frontend-development](), [laravel](), [lazy-loading](), [orm](), [performance](), [react](), [release](), [routing](), [svelte](), [vue]() ### AI overview Inertia 2.0 is a stable release that adds asynchronous requests, deferred props, prefetching, and polling to Laravel frontend development. These features support more responsive applications while avoiding the complexity of maintaining a separate API. ### Source excerpt Inertia 2.0 brings powerful new features to Laravel frontend development including async requests, deferred props, prefetching, and polling. Learn how these improvements help you build faster, more responsive applications without the complexity of maintaining a separate API. ## Joining Nrwl: Five Weeks at the Company DevFeed: [Joining Nrwl: Five Weeks at the Company]() Original publisher: [Read original article]() Published: 2020-02-12T00:00:00Z Content type: opinion Language: en Sources: [Juri Strumpflohner]() Topics: [Development](), [Front end](), [frontend development](), [Angular](), [React](), [JavaScript](), [Refactoring](), [Tooling](), [ci](), [Open Source]() Tags: [angular](), [ci](), [frontend-development](), [javascript](), [monorepo](), [open-source](), [react](), [refactoring](), [tooling]() ### AI overview The author describes joining Nrwl and their first five weeks there, introducing the company's focus on helping enterprises scale software development through monorepos, engineering expertise, consulting, training, automation, and tooling. The article also explains Nx and Nx Console and outlines benefits and challenges of monorepos. ### Source excerpt Lorem ipsum dolor sit amet ## Egghead Lesson: Simple caching with RxJS DevFeed: [Egghead Lesson: Simple caching with RxJS]() Original publisher: [Read original article]() Published: 2018-11-10T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Caching](), [Angular](), [API](), [frontend development](), [Development](), [Redis]() Tags: [angular](), [api](), [cache](), [caching](), [development](), [frontend-development](), [redis](), [software-development](), [video]() ### AI overview An accompanying article for an Egghead video lesson on implementing simple data caching in Angular with RxJS. It discusses cache invalidation and stale data, recommends considering optimizations and server-side API caching such as response headers or Redis, and points to a StackBlitz example. ### Source excerpt Lorem ipsum dolor sit amet ## Egghead Lesson: Avoid memory leaks when subscribing to RxJS Observables in Angular Components DevFeed: [Egghead Lesson: Avoid memory leaks when subscribing to RxJS Observables in Angular Components]() Original publisher: [Read original article]() Published: 2018-10-28T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Angular](), [Memory Leaks](), [frontend development](), [Development]() Tags: [angular](), [development](), [egghead](), [frontend-development](), [memory-leaks](), [rxjs](), [video]() ### AI overview This Egghead lesson explains how memory leaks can occur when subscribing to long-running RxJS Observables in Angular components. It demonstrates the leak and compares manual unsubscription, the takeUntil operator, and the async pipe. It also notes that Angular HTTP client Observables complete immediately, while service abstractions may require different handling. ### Source excerpt Lorem ipsum dolor sit amet ## JavaScript Workshop with Kyle Simpson DevFeed: [JavaScript Workshop with Kyle Simpson]() Original publisher: [Read original article]() Author: Daw Chih Liou Published: 2018-10-15T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [JavaScript](), [Functional programming](), [frontend development](), [Programming]() Tags: [article](), [babel](), [engineering-culture](), [frontend](), [frontend-development](), [functional-programming](), [javascript](), [reactive-programming](), [webpack](), [workshop]() ### AI overview A recap of a five-day JavaScript workshop led by Kyle Simpson at trivago. The workshop covered JavaScript foundations, recent language features, asynchronous programming, functional programming, scope, hoisting, closures, compilation, and execution. The article also discusses applying functional programming and empathetic communication in frontend development. ### Source excerpt It has been a couple of months since Kyle, author of the "You Don't Know JS" series, visited our trivago headquarters a... ## Simple State Management with RxJS's scan operator DevFeed: [Simple State Management with RxJS's scan operator]() Original publisher: [Read original article]() Published: 2018-10-09T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [frontend development](), [Redux](), [Development]() Tags: [angular](), [frontend-development](), [how-to](), [redux](), [rxjs](), [state-management]() ### AI overview A tutorial on using RxJS's scan operator to build a simple state-management solution for frontend applications. It contrasts this lightweight approach with more structured patterns and libraries such as Flux and Redux, while noting that the example is intentionally naive and should be adapted to specific needs. ### Source excerpt Lorem ipsum dolor sit amet ## Looking back on 2017 DevFeed: [Looking back on 2017]() Original publisher: [Read original article]() Published: 2017-12-29T00:00:00Z Content type: opinion Language: en Sources: [Juri Strumpflohner]() Topics: [frontend development](), [Angular](), [Web platform]() Tags: [angular](), [frontend-development](), [public-speaking](), [web-platform](), [writing]() ### AI overview A personal review of 2017 highlights the author's first experiences with remote online speaking, print-press writing, and conference speaking. It also reflects on ten years of blogging, the blog's increasing focus on frontend development and Angular, interest in the wider web platform, and growth in readership. ### Source excerpt Lorem ipsum dolor sit amet ## A Gulp Workflow for Frontend Development Automation DevFeed: [A Gulp Workflow for Frontend Development Automation]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-08-15T22:25:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Gulp](), [frontend development](), [workflow automation](), [CSS](), [JavaScript](), [make]() Tags: [automation](), [build](), [cache](), [cool](), [css](), [debugging](), [development](), [es6](), [faster](), [frontend](), [frontend-development](), [gulp](), [helps](), [here-s](), [insights](), [javascript](), [scss](), [stuff](), [tool](), [workflow]() ### AI overview A tutorial explaining why frontend workflow automation is useful and how Gulp can assemble a website's assets. It describes tasks for processing CSS and JavaScript, including SCSS compilation, browser prefixing, source maps, dependency inclusion, combining, minification, transpilation, and uglification. ### Source excerpt Gulp is a workflow automation tool that helps you build cool stuff faster; here's how to use it for frontend development. ## Why the Team Transitioned Its Frontend from Angular to React DevFeed: [Why the Team Transitioned Its Frontend from Angular to React]() Original publisher: [Read original article]() Author: Nate Tenczar Published: 2017-02-02T20:33:59Z Content type: opinion Language: en Sources: [Localytics]() Topics: [React](), [Angular](), [frontend development](), [JavaScript]() Tags: [angular](), [frameworks](), [frontend](), [javascript](), [react]() ### AI overview The article explains how the team evaluated its frontend development environment and decided to transition from Angular to React. It cites React's growing user base, state-management solutions, and existing internal use, while emphasizing that the opinions reflect the team's specific use case. ### Source excerpt If you sit quietly enough while reading this article you'll hear a sound. It's the faint tapping of fingers on a keyboard, off in the distance in parts unknown. Those self-assured fingers are putting together yet another think piece on JavaScript in this--the ## A Better package.json for the Frontend DevFeed: [A Better package.json for the Frontend]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2016-12-23T19:46:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [frontend development](), [Package manager](), [npm](), [Yarn](), [Gulp]() Tags: [better](), [consider](), [days](), [frontend](), [frontend-development](), [gulp](), [here-s](), [insights](), [like](), [mandatory](), [node-js](), [npm](), [npm-packages](), [package-json](), [setup](), [tools](), [webdev](), [webpack](), [workflow]() ### AI overview This article explains how to use package.json as a centralized manifest for a website's frontend packages and workflow tooling. It discusses replacing Bower with npm, and notes that Yarn can manage the same registry with deterministic installs through yarn.lock. ### Source excerpt Frontend workflow tools like gulp are almost mandatory for webdev these days; here's what I consider to be a better package.json setup ## Frontend Dependency Management with Browserify DevFeed: [Frontend Dependency Management with Browserify]() Original publisher: [Read original article]() Author: Wordbitly Published: 2014-10-30T20:10:27Z Content type: tutorial Language: en Sources: [Bitly]() Topics: [frontend development](), [JavaScript](), [Package Management](), [Node.js](), [npm]() Tags: [browserify](), [dependency-management](), [frontend](), [javascript](), [node-js](), [npm](), [package-management]() ### AI overview This developer article explains how Bitly adopted Browserify for frontend dependency management while overhauling its "Your Bitlinks" interface. It describes Browserify's Node.js-style module and package workflow, including bundling dependencies from an entry point into a destination file, and discusses benefits such as fewer HTTP requests and a less-polluted global namespace. ### Source excerpt With frontend development moving as fast as it does at Bitly, things can get pretty messy. We found ourselves with piles of unmanaged script tags and little indication of what was still being used in the app's current iteration. There had to be a better way! Enter Browserify! A few months ago, we embarked upon a project to totally overhaul the "Your Bitlinks" interface, and with that came the opportunity to rethink our practices and introduce frontend dependency management. Now the page looks as good behind the scenes as it does in your browser! So, what is Browserify? Browserify is a great tool that lets you write your client-side scripts like it's node, allowing you to use node's package management and module systems. Each file should be a module and explicitly require() all its dependencies. Then you simply give Browserify your main entry point, such as an overarching app file, and the name of a destination file, e.g. browserify app.js > bundle.js This example takes your network of dependencies starting at app.js and streams all the files from your network of dependencies into bundle.js. (Side note: Being familiar with the node.js environment and NPM, node's package manager, is essential for picking up Browserify. In the weeks before we started working with Browserify, I wrote and published a node module as a side project. Going through the process, making sure all the pieces were in place-- specifically the package.json-- so that I could add it into the NPM registry made figuring out Browserify much easier.) Why use Browserify? There was no question in our minds that using a frontend dependency management tool was an important step in our app's development. We considered the field of options, ultimately settling on Browserify. We didn't need the async loading functionality of Require.js and appreciated the power of using NPM, leaving Browserify as the natural choice. Leveraging node to bundle our JavaScript provides many advantages over the traditional multiplicit ## Interview On Treehouse DevFeed: [Interview On Treehouse]() Original publisher: [Read original article]() Author: Paul Irish Published: 2012-10-29T12:07:00Z Content type: article Language: en Sources: [Paul Irish]() Topics: [frontend development](), [Web Development](), [Boilerplate](), [Tooling](), [HTML5]() Tags: [development](), [frontend](), [html5](), [interview](), [tooling](), [web-development]() ### AI overview An interview with Treehouse discusses frontend development, the author's background, HTML5 Boilerplate, and tooling. It highlights HTML5 Boilerplate features, fallback scenarios in web development, and whether developers should understand abstractions and their underlying mechanisms. ### Source excerpt The great folks at Treehouse sat down with me for 30 minutes to talk about frontend development, my background, HTML5 Boilerplate and tooling. A few highlights: 3:40 Where'd I grow up? What was I into? (Also, the supercool IE4 DHTML event I went to!) 14:45 What's my favorite feature inside the HTML5 Boilerplate? 18:34 Will web development even out where we don't need to fuss over so many fallback scenarios? 22:52 Are abstractions okay? Should you always learn what's going on under the covers first? I've also updated the interview listing on my About page. <3z ## Academic research on browsers, frontend development, and debugging DevFeed: [Academic research on browsers, frontend development, and debugging]() Original publisher: [Read original article]() Author: Paul Irish Published: 2012-09-13T15:45:00Z Content type: article Language: en Sources: [Paul Irish]() Topics: [browsers](), [frontend development](), [debugging](), [Development](), [JavaScript](), [web applications](), [Document Object Model (DOM)](), [Ajax](), [Security](), [Mobile](), [LocalStorage](), [Node.js]() Tags: [academic-research](), [browser](), [browsers](), [debugging](), [debugging-tools](), [development](), [frontend](), [frontend-development](), [javascript](), [mobile](), [node-js](), [performance](), [realtime](), [research](), [security](), [web-applications]() ### AI overview An English developer article curates academic papers, talks, and researchers focused on browsers and frontend development. It covers browser capabilities, DOM events, client-side validation, mobile performance and energy use, web-application race detection, debugging tools, Node.js performance visualization, and browser security research. ### Source excerpt University-level education has never really touched too directly on what we do as frontend developers. I know I was self-taught in the ways of the browser, as were all of my friends. Luckily the sort of webapp work we do these days is quite sophisticated so those CS graduates bring much of the great ideas to the JavaScript community. (Alex Sexton has been a personal inspiration here) Early last year, something clicked in my head when I saw this video: Crossing the Chasm: Pitching Security Research to Mainstream Browser Vendors. You mean.. there are academics... who are doing research on browsers.. in universities? My my! You mean bright minds think about the same things as us and don't publish them on Octopress? ;) Turns out it's quite an active area of research. So, I've put together a list of academic papers, talks, and researchers all centered around frontend development and browsers (Please chime in on the comments if you know of more): Webapps Gibraltar: Exposing Hardware Devices to Web Pages Using AJAX UC San Diego, Microsoft Research, Univ. of Singapore, 2012 Modeling and Reasoning about DOM Events Brown University, 2012 Don't Repeat Yourself: Automatically Synthesizing Client-side Validation Code for Web Applications University of Illinois at Chicago, 2012 Performance Who Killed My Battery: Analyzing Mobile Browser Energy Consumption Stanford, 2012 How far can client-only solutions go for mobile browser speed? ACM Digital Library, 2012 Race Detection for Web Applications Sofia University & ETH Zurich & IBM T.J. Watson Research Center, 2012 Leo Meyerovich - Berkeley Rsearch UC Berkeley, 2009 (Parallel Browser Execution, Security) James Mickens - Microsoft Research Microsoft, 2004- (Performance, localStorage, Mashups, Speculative Execution James Mickens, the Galactic Viceroy of Research Magnificence at Microsoft Research, does awesome work. The above shot is from his MIX11 talk Making Better Web Apps For Today's Browsers. Debugging & Tools Timelapse - Interactiv ## Moving The Web Forward DevFeed: [Moving The Web Forward]() Original publisher: [Read original article]() Author: Paul Irish Published: 2011-12-04T03:33:00Z Content type: article Language: en Sources: [Paul Irish]() Topics: [Web](), [Web platform](), [GitHub](), [frontend development](), [Front end](), [IRC](), [jQuery](), [Boilerplate]() Tags: [community](), [contribute](), [developers](), [development](), [frontend](), [frontend-development](), [github](), [html5](), [open](), [platform](), [project](), [repo](), [resources](), [standards](), [team](), [web](), [web-platform](), [web-standards](), [writeup]() ### AI overview The article introduces Move the Web Forward, an initiative that helps people channel their interest into practical contributions to the web community and web platform. It describes the initiative's collaborative creation through design, frontend development, IRC, etherpad, and GitHub, and highlights examples of participants contributing to web standards, Firefox, BuddyPress, and documentation. ### Source excerpt This Wednesday, me and a ragtag team of like-minded developers launched Move the Web Forward, an initiative to direct people's passions into productive efforts that assist not only the web community but the entire web platform. People often feel the need to "give back", but when it comes to contributing it's a challenge to find the right place. This is something I've seen happen firsthand in the jQuery and HTML5 Boilerplate communities. The MWF effort was inspired by a tweet by WebKit extraordinaire Dimitri Glazkov. If you want to help out with Web standards, you could wear a blue beanie once a year. Or you could start hacking on WebKit/Gecko. -- Dimitri Glazkov (@dglazkov) December 29, 2010 Me and Divya started brainstorming on an etherpad. We rounded up some folks on Google+ and IRC and started collecting a lot of excellent resources. Soon after a design was in the making and we started working in an open repo on github... At this point, I want to call out Mat Marquis aka @wilto, in particular, for really taking early ownership of this project and spearheading the design and frontend development. His efforts really made the site communicate its content effectively. Naturally the site is on github if you'd like to contribute. We have a few issues open that we'll be improving the site with. (Also, let me just say for projects like this, a cron job to pull latest from Github makes for such a relaxing workflow.) Thanks to Divya, Mat, Aaron Forsander, Connor Montgomery, Stephanie Rewis (great writeup!), Nicolas Gallagher, Addy, and all these awesome folk. Truly a socially developed site; everyone collaborating on IRC, etherpad and github (with as many having commit rights as possible). Fun project to work on and I hope to see everyone find the right place for them to get more involved in actively making the web as awesome as you want it to be. 2011.12.02: #movingwebforward in action! Beyond all the people who signed up (with the avatars) on the site to commit to things.. ## Web browser, frontend and standards feeds to follow DevFeed: [Web browser, frontend and standards feeds to follow]() Original publisher: [Read original article]() Author: Paul Irish Published: 2011-11-22T03:57:00Z Content type: article Language: en Sources: [Paul Irish]() Topics: [Front end](), [frontend development](), [browser](), [Web](), [JavaScript](), [GitHub]() Tags: [blog](), [blogging](), [browser](), [development](), [frontend](), [frontend-development](), [github](), [javascript](), [news-reader](), [standards](), [web]() ### AI overview A curated collection of frontend development, web standards, browser news, and large web application feeds, organized into downloadable OPML bundles for import into a news reader. The article also encourages durable blogging and recommends several weekly newsletters. ### Source excerpt While a lot of conversation has moved to twitter and G+, hugely useful information is still published regularly to blogs. I've shared collections of frontend development feeds twice before. Now I'm back, but with three choices: Download this: frontend-feeds.opml 2013.07.26: Poor Reader. :'( Here are the three below bundles grouped up into an OPML file. Your new news reader can import them in one go. Also, do not forget the most important site that has no feed: webplatformdaily.org. It's the best thing. (2013.09.12: It has a feed now! Added) 2013.09.12: The OPML is now on Github Frontend development exploration, techniques, tips. Lots of JavaScript. 275 feeds. Standards development and browser dev news. 56 feeds. Blogs focusing on building large webapps (new!) 22 feeds. Also, a short commentary on blogging vs tweeting.. while a lot of people have changed to twitter+jsfiddle only, tweets are not available via search after 30 days, so if you expect anything you share to last, blog it for real. :) 2011.12.02: Adding newsletters! 2012.08.09: Refreshed all the bundles. Added the frontend-webapps feed. Also please subscribe to these guys which do a great job of highlighting the top stories of the week: JavaScript Weekly Web Design Weekly HTML5 Weekly 2013.07: Added opml.