npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

nest-ql-schema

v0.0.6

Published

GraphQL schema definitions and generated types for Nest Tanzania Rental Platform

Downloads

242

Readme

Nest QL Schema Package

GraphQL schema definitions and generated TypeScript types for Nest Tanzania Rental Platform.

🔒 Schema Safety Guarantees

This package enforces package-level schema validation with modular architecture:

  • Modular schema files - Domain-separated .graphql files for maintainability
  • Single deployable schema - Merged into schemas/appsync.graphql at build time
  • Build-time validation - Invalid schemas fail during npm run build
  • Publish-time protection - npm publish fails if schema is invalid
  • AppSync compatibility - Generated schema is AppSync-safe only

📁 Modular Schema Structure

schemas/
├── _shared/
│   ├── scalars.graphql      ← AWSDateTime, AWSJSON
│   ├── enums.graphql        ← All enums
│   └── directives.graphql   ← @aws_subscribe
│
├── location/
│   ├── types.graphql        ← Region, District, Ward, Street
│   └── queries.graphql      ← Location queries
│
├── user/
│   ├── types.graphql        ← Tenant, Landlord, Admin, UserProfile
│   ├── inputs.graphql       ← SignUpInput, UpdateUserInput
│   ├── queries.graphql      ← User queries
│   └── mutations.graphql    ← Auth & user mutations
│
├── property/
│   ├── types.graphql        ← Property, Address, PropertyMedia
│   ├── inputs.graphql       ← CreatePropertyInput, UpdatePropertyInput
│   ├── queries.graphql      ← Property queries
│   ├── mutations.graphql    ← Property mutations
│   └── subscriptions.graphql ← Property subscriptions
│
├── application/
│   ├── types.graphql        ← Application, ApplicantDetails
│   ├── inputs.graphql       ← SubmitApplicationInput
│   ├── queries.graphql      ← Application queries
│   ├── mutations.graphql    ← Application mutations
│   └── subscriptions.graphql ← Application subscriptions
│
├── root/
│   ├── query.graphql        ← type Query { _empty: String }
│   ├── mutation.graphql     ← type Mutation { _empty: String }
│   └── subscription.graphql ← type Subscription { _empty: String }
│
└── appsync.graphql          ← GENERATED (DO NOT EDIT)

🚀 Usage

For CDK/AppSync Consumers

import { APPSYNC_SCHEMA_PATH } from 'nest-ql-schema';
import * as appsync from 'aws-cdk-lib/aws-appsync';

new appsync.GraphqlApi(this, 'Api', {
  schema: appsync.SchemaFile.fromAsset(APPSYNC_SCHEMA_PATH),
});

For Type Definitions

import { 
  Property, 
  CreatePropertyInput,
  Resolvers 
} from 'nest-ql-schema';

🛠 Development

# Build merged schema from modules
npm run schema:build

# Validate merged schema
npm run schema:validate

# Generate TypeScript types
npm run codegen  

# Full build (merge + validate + codegen)
npm run build

# Publish (fails if schema invalid)
npm publish

✅ Modular Schema Rules

  1. Root types: Use extend type Query/Mutation/Subscription in domain files
  2. Domain separation: Each domain owns its types, inputs, queries, mutations
  3. No duplicates: GraphQL prevents duplicate type names automatically
  4. Single source: Only appsync.graphql is consumed by CDK

🔄 Build Process

  1. Merge: Combine all schemas/**/*.graphql files (except generated ones)
  2. Validate: Ensure merged schema is valid GraphQL
  3. Generate: Create appsync.graphql with header
  4. Codegen: Generate TypeScript types from merged schema
  5. Package: Copy schemas and generated files to dist/

⚡ What This Prevents

Before: Monolithic schema, merge conflicts, unclear ownership
After: Clean domain separation, no conflicts, clear ownership

Before: Invalid schema deployed to AppSync → runtime failure
After: Invalid schema rejected at build time → no broken deployments

The package now guarantees modular development with deployment safety.