You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document lists all NuGet and npm packages used in IssueTrackerApp, sourced from Directory.Packages.props and src/Web/package.json for centralized version management.
NuGet Packages
.NET Aspire Integration
Package
Version
Purpose
Aspire.MongoDB.Driver
13.1.0
MongoDB integration with Aspire orchestration and health checks
Aspire.StackExchange.Redis
13.1.0
Redis integration with Aspire orchestration and service discovery
Data Access
Package
Version
Purpose
MongoDB.Bson
3.6.0
BSON serialization for MongoDB documents
MongoDB.Driver
3.6.0
Low-level MongoDB client driver
MongoDB.EntityFrameworkCore
10.0.0
Entity Framework Core provider for MongoDB with LINQ support
Application Patterns
Package
Version
Purpose
MediatR
12.4.1
CQRS pattern implementation for command/query separation
FluentValidation.DependencyInjectionExtensions
11.11.0
Fluent API for model validation with dependency injection
Authentication & Security
Package
Version
Purpose
Auth0.AspNetCore.Authentication
1.5.1
Auth0 integration with Authorization Code + PKCE flow
Centralized NuGet Versioning: All package versions are managed in Directory.Packages.props to ensure consistency across projects
Aspire Integration: The Aspire.MongoDB.Driver and Aspire.StackExchange.Redis packages handle configuration, health checks, and resilience automatically
OpenTelemetry: All instrumentation packages work together to provide comprehensive observability
Testing: The project uses multiple testing libraries for different scenarios (unit, integration, component, E2E)
TailwindCSS v4: Uses the new v4 architecture with @import "tailwindcss" and @source directives
MSBuild Integration: CSS compilation is integrated into the .NET build process
Version Strategy
NuGet packages are updated regularly to maintain security and feature parity with .NET 10 ecosystem
npm packages follow semantic versioning with ^ prefix for minor version updates
Breaking changes are coordinated across the team before upgrade