tools-monorepo

Bernier LLC Tools Monorepo

This repository contains a collection of reusable, production-grade packages for modern web applications, maintained by Bernier LLC. It is organized as a monorepo using npm workspaces for scalable, maintainable multi-package development.

Packages

• Each package lives in packages/<name>/ and is published independently to npm under the @bernierllc/ scope.
• Packages include: logging, calendar, messaging, tasks, integrations, docs-viewer, and more.
• See each package's README for usage and API details.

Getting Started

# Install all dependencies (from the repo root)
npm install --legacy-peer-deps

Important: Always run npm install from the root directory, never from individual package folders. See Contributing Guidelines for more details.

Development

• Each package has its own package.json for direct dependencies and peerDependencies.
• Shared devDependencies (Jest, TypeScript, React Testing Library, etc.) are hoisted to the root.
• Run scripts from the root or from individual packages; dependencies will be resolved correctly.

Common scripts:

npm run build         # Build all packages
npm test              # Run all tests
npm run lint          # Lint all packages
npm run type-check    # Type-check all packages

🚀 Publishing to npm

Development CLI (Recommended)

For the easiest publishing experience, use our development CLI:

# From the root directory
npx development-cli publish

# Or if you have the CLI installed globally
development-cli publish

This will:

• Show you a list of all packages to choose from
• Ask you to select the version bump (patch, minor, major)
• Prompt for a changelog summary
• Automatically create the changeset, commit it, run versioning, and publish
• Handle 2FA authentication prompts clearly

The development CLI is the future of our publishing workflow!

Legacy Publishing (Temporary)

Until the development CLI is fully implemented, you can use our legacy interactive script:

node scripts/publish.js

Note: This script is deprecated and will be removed once the development CLI is complete.

Manual Publishing Workflow

If you prefer to use the manual workflow:

• Create a changeset for the package you want to publish:

  npx changeset
  

  • Select only the package(s) you want to release when prompted.
  • Choose the appropriate version bump (patch, minor, major).
  • Write a summary for the changelog.

• Commit the changeset:

  git add .changeset/*
  git commit -m "chore: add changeset for <package>"
  

• Update versions and changelogs:

  npx changeset version
  git add .
  git commit -m "chore(release): version packages"
  

• Publish to npm:

  npm run publish:all
  

  • This will only publish packages that have a new version (i.e., those with a changeset and version bump).
  • All other packages will be skipped.

If any step fails, the publish is aborted.

Note: The manual workflow is being phased out in favor of the development CLI.

For detailed information about the publishing workflow, see: docs/deployment-with-changesets.md

Monorepo Workspaces & Dependency Management

This repo uses npm workspaces for scalable, maintainable multi-package development. All dependencies (including devDependencies) are hoisted to the root. Always run npm install from the root directory.

React 19 and Testing Library Compatibility

All packages are now standardized on React 19.1.0. As of July 2024, some testing libraries (notably @testing-library/react) do not yet officially support React 19 in their peerDependencies. To work around this, we use:

npm install --legacy-peer-deps

This allows npm to install all dependencies despite the peer conflict. This is a safe, temporary workaround until official support is released. Monitor for updates and upgrade Testing Library when React 19 support is available.

Contributing

• Fork the repository
• Create a feature branch
• Make your changes
• Add tests
• Submit a pull request

For detailed contributing guidelines, see: CONTRIBUTING.md

License

ISC License - see LICENSE file for details. # Enhanced Pre-commit Hook

Test full validation