Adding Firebase Auth to a Chrome extension built with Plasmo using offscreen documents and using web_accessible_resources to load a script from the extension.

Dockerfile with uv for Scrapy and Playwright for web scraping and automation

How to handle the token refresh for the Google OAuth flow in a Chrome extension using an external server API running in a Cloudflare Worker.

How to handle the token exchange and refresh for the Google OAuth flow in a Chrome extension using an external server API running in a Cloudflare Worker and Firebase Auth.

How to set up Google Sign In with Google OAuth in a Chrome Extension using chrome.identity.launchWebAuthFlow to handle the OAuth flow across all Chromium-based browsers. This is the first post in a series on implementing Google Sign In using Google OAuth in Chrome extensions.

Save the Scrapy spider crawl stats to a Postgres database using a custom extension and SQLAlchemy. We'll also update the existing database item pipeline to collect custom stats specific to the spider.

Setting up a Scrapy spider to crawl pages with infinite scroll using Playwright and Chromium.

Using Cloudflare Workers, D1, and Drizzle ORM to verify and save Lemon Squeezy subscription webhook data.

Detecting issue transfers and redirects in browser extensions using the chrome.webNavigation API and the server_redirect transition qualifier.

Adding support for user-provided Gen AI LLM API keys in the dossi Chrome extension.

dossi, a browser extension and web app to keep track of your own private GitHub notes is now open source.

If you want to change to the application type from SSR to SSG, or SSG to SSR, then the platform and framework type will need changed in your application settings in Amplify Hosting. If not, you'll likely hit deploy errors or 503s when the site builds and deploys.

This post steps through setting up Amplify Auth with the Amplify UI React library in a Next.js SSR application. Once set up, we can restrict access to pages using the built-in hooks from the Amplify Authenticator and use withSSRContext and Auth to restrict access to the API routes and pages with SSR.

Add Prisma to Next.js API routes deployed to Amplify Hosting.

Set up and deploy a Next.js SSR app that uses the Prisma ORM with a PostgreSQL database. Once integrated, we'll be able to fetch data using SSR and getServerSideProps. We'll store the connection information for the database in AWS Systems Manager Parameter Store and deploy the app using Amplify Hosting.

Set up NextAuth.js with the Slack provider and Prisma.

Building and deploying a Slack app with AWS Amplify, Python, and Bolt.

Deploying a FastAPI backend using AWS Amplify Container-based REST APIs.

Display the active Amplify Environment in your terminal alongside your Git branch status.

A quick Zsh or Bash function to open an RStudio project from the command line.

The last step in creating a Vue component library plugin is to publish it as a package. Most packages are published on npm if the intention is to distribute to an external audience. Other registry options include GitHub Package Registry and Artifactory. It is also possible to run your own private registry. To demonstrate, we'll publish to npm. Similar steps can be taken to use a different registry if it also utilizes the npm (or yarn) CLI API conventions.

Documentation is no fun if it isn't public. Now, having configured the component library to use VuePress for the documentation and marketing aspect, we need to deploy it. Netlify is a great choice for this!

Documentation time! In this post, we'll add a documentation element to the Vue component library plugin using VuePress. The end state of this post will be a static site that is structured to document a component library that exists in the same project. The component will generate its own documentation!

At this point, we have a structured approach for creating new Vue.js components and consolidating them into a single module export. Awesome! Next, we'll bundle the components into a plugin to be registered on a Vue instance.

In this post, we'll step through the initial project structure for your Vue components. Remember, you'll want to to try to lower the barriers to entry of understanding for other developers in order for them to grasp your design choices.

In this series, we’ll focus on structuring a Vue component library as a plugin for use, and reuse. That also includes distribution and documentation. That's what is so great about Vue - the ability create your own building blocks for designing a user experience.

The settings below are my defaults for Vue.js development in Visual Studio Code.

The initial jump into the netlify.toml file is a bit daunting at first, especially if you only want to make a small change. Once your Hugo site it deployed on Netlify, you’ll want to redirect traffic pointed to the provided subdomain to your primary domain.