broneukr/packages

@jeromefitz/packages

Monorepo (via 📦 pnpm and 🔺 turbo) for tools I use frequently in various projects, people, and companies I work with.

• 📦️ Packages
• 👷️ CI/CD Overview
• CI/CD Workflows

📦️ Packages

🔧 Configuration

Originally was all-in-one as @jeromefitz/codestyle, these have been broken out for separate maintainability and ala-carte implementation.

Spoiler: They are opinionated, but can be overriden, extended, or ignored. 🙈

• @jeromefitz/eslint-config
• @jeromefitz/lint-staged
• @jeromefitz/prettier-config
• @jeromefitz/tsconfig

🖼️ Design System

Built with radix-ui and stitches. A tree-shakeable design system that you can use as much of, or as little of, as you would like.

• @jeromefitz/design-system
  • 🏆 Major props to the @radix-ui team as this is 🍽️ of sorts.
  • 📘 Storybook is included but not all the way there. May
  • 🚀 Code Example: @jeromefitz/websites
  • 🚀️ Live Example: jeromefitzgerald.com

⚡ Release Management Tools

• @jeromefitz/conventional-gitmoji
  • Map gitmoji to conventional-commits
    • feat => ✨️
    • fix => 🐛️
    • ci => 👷️
    • fix-ci => 💚️
    • ...
  • Allows you to keep semver consistent by expanding both
  • You most likely do not need to use this, unless you are using this for your separate tooling. This is more of a configuration stop-gap for ...
• @jeromefitz/git-cz
  • cli prompt for (expanded) conventional commits and conventional branches as no one needs to remember all the different types
    • 📝 Formats your commit message for you
    • 🖲️ Integrate with your Issue Tracking System
    • 🔢 Customize which commit types get which semver
• @jeromefitz/semantic
  • Automatic Semantic Versioning through semantic-release with support for gitmoji.
• @jeromefitz/release-notes-generator
  • You guessed it, a custom release-notes-generator.
  • 📝 See the latest output at the releases page.

🎲 Misc

• @jeromefitz/notion
  • 🗃️ API (hyper-customized @notionhq/client) for Notion
  • 🚀️ Live Example: jeromefitzgerald.com
• @jeromefitz/scripts
  • scripts that are used to set up repos and for CI/CD
• @jeromefitz/spotify
  • 🧑‍🎤️ API to gather data on:
    • now-playing|top-artists|top-tracks
  • 🖼️ Plus imagery customizations via plaiceholder
  • 🚀️ Live Example: jeromefitzgerald.com/music
• 🧰️ @jeromefitz/utils
  • Scripts that are generically re-used throughout

🔜 Coming Soon(ish)

• next-notion
  • Next.js implementation for @jeromefitz/notion

🎁 Bonus

• @jeromefitz/dotfiles: Separate from this repository
  • zsh + homebrew computer setup

👷️ CI/CD Overview

• 📦 pnpm workspaces
• GitHub Actions for CI/CD
  • Plus release management through npm
• 🔺️ turbo for monorepo management
  • cache: local / remote & team development
  • cache: github actions
• 👷️ tsup for typescript builds (w/ some config)
• 🤖️ Renovate for Patch + Minor Package Management
• 🤖️ Kodiak to “Automate (our) GitHub Pull Requests’
• 🤖️ Automatic Semantic Versioning w/ Conventional Commits
  • 😜️ Commits & Versioning (Release Notes) made more fun by a few of the packages in this repo

CI/CD Workflows

• ⚗️ **pull**:
  • Branch(es):
    • main|canary|develop
  • Script(s):
    • lint|test|build
• 🔀️ **push**:
  • Branch(es):
    • main|canary|develop
    • (ci|feature|fix|refactor|release)/**
  • Script(s):
    • lint|test|build|semantic-release
  • Note(s):
    • [b] necessary for semantic-release
      • Pre-relase branches (aka !main):
        • Handled in root release.config
        • Can be overriden in any package
    • [b] necessary for build when not on main
• 🌃️ **weekly**:
  • Branch(es):
    • main
  • Script(s):
    • lint|test|build|semantic-release
  • Note(s):
    • [b] not necessary for semantic-release