How do you send email from a JAMstack-style site? Chris Coyer writes on CSS-Tricks: Let’s say you’re rocking a JAMstack-style site (no server-side languages in use), but you want to do something rather dynamic like send an email. Not a problem! That’s the whole point of JAMstack. It’s not just static hosting. It’s that plus doing anything else you wanna do through JavaScript and APIs. Here’s the setup…
read more
Stop wasting time mocking APIs. MockIt gives you an interface to configure and create REAL mocked end points for your applications.
read more
After several months of being just days away, we are over the moon to announce the stable release of Svelte 3. This is a huge release representing hundreds of hours of work by many people in the Svelte community, including invaluable feedback from beta testers who have helped shape the design every step of the way. Lots of folks (myself included) have been eagerly awaiting this release after Rich teed it up on The Changelog #332. We’d love to hear your first impressions!
read more
KBall MC’d a live show at React Amsterdam with a panel of 5 amazing React experts — Kitze, Michel Weststrate, Mike Grabowski, Vladimir Novick, and Andrey Okonetchnikov. It was a great discussion of state management solutions and the future of state management in the front-end.
read more
This is basically an API for the (excellent looking) Mermaid.
read more
What’s old is new again! Built with styled-components.
read more
Have fun in this rabbit hole. You can use emoji (and other graphical unicode characters) in URLs. And wow is it great. But no one seems to do it. Why? Perhaps emoji are too exotic for normie web platforms to handle? Or maybe they are avoided for fear of angering the SEO gods? Whatever the reason, the overlapping portion on the Venn diagram of “It’s Possible v.s. No One Is Doing It” is where my excitement usually lies. So I decided to put a little time into the possibilities of graphical characters in URLs. Specifically, with the possibility for animating these characters by way of some Javascript.
read more
This pretty much sums up the point Jeremy is trying to get across with this post on A List Apart and the future parts to this story of “Responsible JavaScript.” I’m not here to kill JavaScript — Make no mistake, I have no ill will toward JavaScript. It’s given me a career and—if I’m being honest with myself—a source of enjoyment for over a decade. Like any long-term relationship, I learn more about it the more time I spend with it. It’s a mature, feature-rich language that only gets more capable and elegant with every passing year. Yet, there are times when I feel like JavaScript and I are at odds. I am critical of JavaScript. Or maybe more accurately, I’m critical of how we’ve developed a tendency to view it as a first resort to building for the web…
read more
Playroom allows you to create a zero-install code-oriented design environment, built into a standalone bundle that can be deployed alongside your existing design system documentation.
read more
KBall and Jason geek out on the ins and outs of Gatsby. They talked through the fundamentals of working with Gatsby, the development process, and look into the future of Gatsby.
read more
KBall, Nick, and Chris dig into the various dimensions along which projects vary, dig into testing and best practices, and share a number of lessons learned from legacy projects.
read more
Marco Otte-Witte on how Single Page Apps (SPA), Progressive Web Apps (PWA), and Server-side Rendering (SSR) approaches deliver the best result when all combined in one app - you’re maintaining one app but run that both in the browser and the server and add PWA concepts like service workers on top.
read more
Stop me if you’ve heard this one before…the difference is DeskGap leverages the operating system‘s webview instead of baking a browser in with it (like Electron). DeskGap is a framework for building cross-platform desktop apps with web technologies (JavaScript, HTML and CSS). To enable native capabilities while keeping the size down, DeskGap bundles a Node.js runtime and leaves the HTML rendering to the operating system‘s webview.
read more
This new take on a block-style text editor from CodeX looks promising. Unlike how the common WYSIWYG editor produces raw HTML markup with both content data and content appearance, Editor.js outputs a JSON object with the data of each block of content. Here’s an example of how this news item would look. { "time": 1554306305, "blocks": [ { "type": "header", "data": { "text": "Editor.js — next generation block-style text editor", "level": 1 } }, { "type": "paragraph", "data": { "text": "This new take on a block-style text editor looks promising. Unlike how the common WYSIWYG editor produces raw HTML markup with both content data and content appearance, Editor.js outputs a JSON object with the data of each block of content. Here's an example of how this news item would look." } }, { "type": "code", "data": { "code": "" } } ], "version": "2.12.3" }
read more
Jerod and Nick are joined by Fred K. Schott – the main brain behind Pika. What’s that, you ask? An effort to make modern JavaScript more accessible by making it easier to find, publish, install, and use modern packages on npm.
read more
Maybe you’re thinking this is some kind of emulator that has been compiled to WebAssembly or a Docker thing somehow running in the browser. Nope! It’s a straight-up React-based web application that recreates the classic XP desktop. Most of the apps don’t actually exist, but have no fear: Minesweeper is here 🙌
read more
When you hard-attach your library to a specific technology or framework, you limit its potential impact. By thinking ahead and putting in a little more effort, your library could benefit orders of magnitudes more people.
read more
A (coverage-)guided fuzzer for dynamic language interpreters based on a custom intermediate language (“FuzzIL”) which can be mutated and translated to JavaScript. Not an official Google project, but written and maintained by Google engineer Samuel Groß. The README lays out quite a bit on the concept, implementation, and usage of the fuzzer, but there’s even more to learn in this presentation from Offensive Con 2019 and the associated master’s thesis for which the project was produced.
read more
We discuss the news (built-in modules, OpenJSFoundation, Lambda School stipends), chat about the internet of JS things, and finish up with one of our favorite segments: shout outs!
read more
Chris Coyier joins Suz and Jerod to continue the discussion on The Great Divide in front-end-land. We also use this as an opportunity to gush on how much CSS-Tricks has done for the community, get Chris’ perspective on the history of the website, and finish up by sharing some amazing Pens on CodePen.io.
read more
An amazing amount of information in an easily accessible format. Check out the GitHub org for additional versions on CSS, React, interviewing, and more.
read more
We made a silly joke on Twitter yesterday (this is what Twitter is for, no?) about test doubles and that unfortunate moment when they inevitably surprise you. This prompted Shlomo Kraus to reach out and tell us about Mockshot. In brief: Imagine you could: Never manually write a mock again Have a guarantee that your mocks are always valid Sounds nice! It works by using Jest’s snapshot tests output to generate mocks to be used in other tests. This is purposeful coupling, which seems like it could backfire in the long-run. However, the team behind the library has been using it for over a year and are still singing its praises. For more on their experience creating and using it, read this.
read more
This site is a collection of generative music pieces which can be listened to. The term “generative music” has been used especially by Brian Eno to describe music which changes continuously and is created by a system. Such systems often generate music for as long as one is willing to listen. Push play and code away.
read more
Why is writing portable Node code so important? According to the 2018 Node.js user survey (using the raw data), 24% of Node.js developers use Windows locally and 41% use Mac. In production 85% use Linux and 1% use BSD.
read more
Carmen Bourlon, writing on her personal blog: A browser will check in with a service worker every 24 hours and re-initiate the process, but only if there are changes. You might change your app’s CSS or JavaScript, but without a change to the service worker, the browser will never go and update your service worker. And if the service worker never gets updated, the changed files will never make it to your user’s browser! Fortunately, there’s a pretty simple fix – we’ll version our cache… Thanks to Carmen for this fresh take on service workers from an offline-first point of view. If you dug this, you might want to get on the list for her book “Let’s Take This Offline” — a book about service workers with a focus on helping users without a consistent internet connection.
read more
