🔥 Daily Digest: Master Monorepos, Custom Auth, and Next.js Strategies for Seamless Dev Workflows

In partnership with

Daily Issue #70 | Subscribe to DS | Daily Sandbox Pro

This issue is all about tackling monorepos, rolling your own auth, and some powerful tools. Check it out:

• Monorepo Shrinkage: How we cut our JavaScript monorepo size by 94%.

• Managing Large Monorepos: Best practices for keeping a massive JS monorepo under control.

• DIY Auth: Guide to implementing custom authentication in JavaScript & TypeScript.

• Next.js Authentication: Simplifying auth for your Next.js projects.

• Coding Toolbox:

  • medusa: The most flexible e-commerce platform out there.

  • JSON Crack: Visualize JSON and other data formats with interactive graphs.

  • Offload: Build web apps running AI directly in the browser for faster performance.

• How we shrunk our Javascript monorepo git size by 94%

• How to successfully manage a large scale JavaScript monorepo

• How to roll your own auth in JavaScript & TypeScript

• Authentication in Next.js

More news here →

Learn AI in 5 minutes a day.

The Rundown is the world’s most trusted AI newsletter, with over 700,000+ readers staying up-to-date with the latest AI news, understanding why it matters, and learning how to apply it in their work.

Their expert research team spends all day learning what’s new in AI, then distills the most important developments into one free email every morning.

Sign up.

Mastering Data Sync in Postgres: Automating Resource Counts with Triggers

Imagine a bustling library, where every new book or magazine needs to be meticulously logged in the main catalog to keep counts accurate. In the world of databases, we face a similar challenge: how do we keep track of thousands of entries across multiple categories without constant manual updates? Enter Postgres triggers, our silent but tireless librarians, ensuring data stays perfectly synced.

The Core Structure: The "Resources" Table

At the heart of our setup is the resources table, the master catalog that tracks every resource type: articles, boilerplates, templates, and more. The crucial column, total_num, holds the count of each resource category. But here’s the beauty: we don’t manually update this count. Postgres triggers handle it for us, automating updates and maintaining perfect accuracy.

How It Works: Triggers in Action

For every resource—like articles or templates—there’s a corresponding table. When a new item is added to one of these tables, a Postgres trigger fires off, automatically updating the total_num in the resources table.

Here's a quick look at a trigger setup for the articles table:

CREATE TRIGGER update_total_num
AFTER INSERT ON articles
FOR EACH ROW
EXECUTE FUNCTION update_resource_count();

Whenever a new article is added, this trigger calls update_resource_count(), a function that recalculates the total and updates the master table.

The Function Behind the Scenes

Our update_resource_count() function is the brains of the operation:

CREATE OR REPLACE FUNCTION update_resource_count()
RETURNS TRIGGER AS $$
BEGIN
  UPDATE resources
  SET total_num = (SELECT COUNT(*) FROM articles)
  WHERE resource_name = 'articles';
  RETURN NEW;
END;
$$ LANGUAGE plpgsql;

It counts the entries in the articles table and updates the master count, ensuring data integrity. Similar functions and triggers are set up for other resource types, so everything remains in sync.

⭐️ For the full details, check out the full article here

More code snippets here →

• medusa - The world's most flexible commerce platform

• JSON Crack - Innovative and open-source visualization application that transforms various data formats, such as JSON, YAML, XML, CSV and more, into interactive graphs

• Offload - Create web apps that run AI directly in your users' browsers

• codeflow - an open-source platform designed to help developers, teams, and organizations quickly grasp any code base

More code libs here →

Midjourney

More AI prompts here →

📣 HELP SPREAD THE WORD

🚀 Spread the Code! Love what you read? Share the newsletter with your fellow devs - every recommendation helps power up the community.

💻 Sponsor the Dev Journey! Keep the bytes flowing and the newsletter growing by becoming a sponsor. Your support helps maintain this valuable resource.

💬 Tweet the Deets! Share the latest with your code crew - let’s make this viral, not just a bug!

If you have built anything that you’d like to share with the community, get with me on X @dailysandbox_ 😀