Introduction

Working With Monorepos

Workspaces

Shared Configs

Frontend

Schema

Backend

Introduction and Getting Started

Analyzing

Designing the Customer-facing UI with TailwindCSS

Data Model

Analysis and Design

PostgreSQL Ranges

The Provider Table

The Booking Table

Modelling with advanced Postgres features

Tailwind CSS

Foundation

Frontend State

Shared Components

Select Day

Frontend UI

Introducing tRPC

Connecting to tRPC

Refining the tRPC setup

Connecting to the Database

Generating Zod schemas

Endpoints

Testing tRPC Endpoints

Testing With the Database

Testing Frontend

Testing

Completing the Select Date Page

Infrastructure for Ranges

Completing Booking

Connecting The Dots

Conclusion and extra resources

This comprehensive course will equip you with the skills and knowledge to build modern full-stack applications using TypeScript, TailwindCSS, tRPC, and PostgreSQL. You will learn how to create a robust and scalable application architecture, from the backend data layer to the frontend UI.

PostgreSQL

NodeJS

Knex

React

TypeScript

tRPC

Monorepos simplify code development and can be split when necessary.

Setting up npm workspaces in our monorepo

Setting up shared Typescript, ESLint and Prettier configs

Master full-stack development with a single repository for everything!

Learn the art of full-stack development with this comprehensive course. Through implementing the latest technologies and techniques, the course directly addresses the most common challenges full-stack developers face:
- **Code consistency and sharing:** Monorepos eliminate the need for multiple repositories, ensuring consistent code across your application and facilitating seamless code sharing.
- **Technology integration:** Learn how to integrate modern technologies like TypeScript, Tailwind CSS, and tRPC, empowering you to build robust and maintainable applications.
- **Database management:** Master advanced PostgreSQL features to optimize data storage, retrieval, and manipulation, ensuring a high-performance and scalable backend.

Build type-safe full-stack applications with database-centric strategies

This comprehensive full-stack development course covers monorepos, TypeScript, Tailwind CSS, tRPC, and PostgreSQL, empowering you to build modern, scalable applications. Structured into 7 modules of bite-sized lessons, each module is designed to be engaging and informative, combining video lectures, hands-on coding exercises, and real-world examples.

Fullstack Typescript with TailwindCSS and tRPC Using Modern Features of PostgreSQL

Writing PostgreSQL ranges for the application database.

Breaking down the UI to build it with Tailwind CSS

Master monorepos for streamlined development workflows and enhanced collaboration

Implement TypeScript for type-safe code that prevents errors and improves maintainability

Utilize Tailwind CSS to create consistent and beautiful user interfaces

Employ tRPC for seamless data exchange between frontend and backend

Harness advanced PostgreSQL features for optimized data storage, retrieval, and manipulation

Build modern, scalable full-stack applications using a unified approach

As it is, you are treating the ranges (the 

 table) as strings in the code. That works and you could get far with that. But let's try to narrow it down a bit.

 which offers a type that can parse and stringify ranges in the PostgreSQL syntax and has some helper functions for doing arithmetic if we should want that.

 -- we want to work with these types everywhere!

Once that's in place, modify our Kanel configuration to use this class instead of a string for the 

const { knexTypeFilter, generateKnexTablesModule } = require('kanel-knex');
const { generateZodSchemas } = require('kanel-zod');
const { generateIndexFile } = require('kanel');

const knexConfig = require('./knexfile');

const outputPath = './src/models';

/** @type {import('kanel').Config} */
module.exports = {
  connection: knexConfig.development.connection,

  outputPath,
  preDeleteOutputFolder: true,

  typeFilter: knexTypeFilter,
  preRenderHooks: [
    generateIndexFile,
    generateKnexTablesModule,
    generateZodSchemas,
  ],

  customTypeMap: {
    'public.citext': 'string',
    'pg_catalog.tsrange': {
      name: 'Range<Date>',
      typeImports: [
        {
          name: 'Range',
          path: 'postgres-range',
          isAbsolute: true,
          isDefault: false,
        },
      ],
    },
  },
};

Notice that you're creating a somewhat complex type specification here. Basically we need to tell Kanel that it should use the 

 as the generic parameter. Also, we tell it that it's an absolute import (i.e. from an npm package) and that it's a named rather than default export.

If we run Kanel again, you will now see that your 

Sadly, and this is where the lacking soundness of TypeScript reveals itself, you would be in for an unpleasant surprise if you were to use these types with Knex as it is, because the 

 property will still be a string at runtime. You need to parse the results from PostgreSQL.

---
title: Infrastructure for Ranges
description: Setting up infrastructure for Ranges
isPublicLesson: true
privateVideoUrl: https://stream.mux.com/YZXXNORKZjQFtthhNV003yhmniovWRwiNq4olqYfGsyo.m3u8
code: https://gitlab.com/fullstackio/books/newline-course-apps/fullstack-typescript-with-tailwindcss-and-trpc-using-modern-features-of-postgresql-app/-/tree/main/module_07/lesson_07.02?ref_type=heads
---

## Infrastructure for Ranges

As it is, you are treating the ranges (the `during` column in our `booking` table) as strings in the code. That works and you could get far with that. But let's try to narrow it down a bit.

There is a package called [postgres-range](https://www.npmjs.com/package/postgres-range) which offers a type that can parse and stringify ranges in the PostgreSQL syntax and has some helper functions for doing arithmetic if we should want that.

Install the package in `schema`, `backend` and `frontend` -- we want to work with these types everywhere!

Once that's in place, modify our Kanel configuration to use this class instead of a string for the `tsrange` type:

```js
const { knexTypeFilter, generateKnexTablesModule } = require('kanel-knex');
const { generateZodSchemas } = require('kanel-zod');
const { generateIndexFile } = require('kanel');

const knexConfig = require('./knexfile');

const outputPath = './src/models';

/** @type {import('kanel').Config} */
module.exports = {
  connection: knexConfig.development.connection,

  outputPath,
  preDeleteOutputFolder: true,

  typeFilter: knexTypeFilter,
  preRenderHooks: [
    generateIndexFile,
    generateKnexTablesModule,
    generateZodSchemas,
  ],

  customTypeMap: {
    'public.citext': 'string',
    'pg_catalog.tsrange': {
      name: 'Range<Date>',
      typeImports: [
        {
          name: 'Range',
          path: 'postgres-range',
          isAbsolute: true,
          isDefault: false,
        },
      ],
    },
  },
};
```

Notice that you're creating a somewhat complex type specification here. Basically we need to tell Kanel that it should use the `Range` class with `Date` as the generic parameter. Also, we tell it that it's an absolute import (i.e. from an npm package) and that it's a named rather than default export.

If we run Kanel again, you will now see that your `Booking` type contains instances of this type.

Sadly, and this is where the lacking soundness of TypeScript reveals itself, you would be in for an unpleasant surprise if you were to use these types with Knex as it is, because the `during` property will still be a string at runtime. You need to parse the results from PostgreSQL.

Learn

The newline Guide to Building Your First GraphQL Server with Node and TypeScript

Teach

Amelia Wattenberger

Author of Fullstack D3

Community

Fullstack Typescript with TailwindCSS and tRPC Using Modern Features of PostgreSQL

Module 1: Introduction and Getting Started

Introduction:

Start Here

Lesson 1: (3:09)

Introduction

Lesson 2: (6:35)

Working With Monorepos

Lesson 3: (6:45)

Workspaces

Lesson 4: (17:56)

Shared Configs

Lesson 5: (9:27)

Frontend

Lesson 6: (16:20)

Schema

Lesson 7: (5:21)

Backend

Module 2: Analysis and Design

Lesson 1: (3:09)

Analyzing

Lesson 2: (4:04)

Designing the Customer-facing UI with TailwindCSS

Lesson 3: (2:49)

Data Model

Module 3: Modelling with advanced Postgres features

Lesson 1: (6:18)

PostgreSQL Ranges

Lesson 2: (16:10)

The Provider Table

Lesson 3: (4:47)

The Booking Table

Module 4: Frontend UI

Lesson 1: (1:25)

Tailwind CSS

Lesson 2: (7:58)

Foundation

Lesson 3: (21:53)

Frontend State

Lesson 4: (4:52)

Shared Components

Lesson 5: (16:13)

Select Day

Module 5: Endpoints

Lesson 1: (7:45)

Introducing tRPC

Lesson 2: (17:22)

Connecting to tRPC

Lesson 3: (7:22)

Refining the tRPC setup

Lesson 4: (7:28)

Connecting to the Database

Lesson 5: (4:56)

Generating Zod schemas

Module 6: Testing

Lesson 1: (4:33)

Testing tRPC Endpoints

Lesson 2: (25:00)

Testing With the Database

Lesson 3: (12:37)

Testing Frontend

Module 7: Connecting The Dots

Lesson 1: (21:07)

Completing the Select Date Page

Lesson 2: (14:07)

Infrastructure for Ranges

Lesson 3: (15:49)

Completing Booking

Module 8: Conclusion and extra resources

Lesson 1: (1:02)

Conclusion and extra resources

Infrastructure for Ranges