Package Exports
- vibealive
- vibealive/dist/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (vibealive) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
A framework-aware code analysis tool for Next.js projects. Identify unused files, dead code, and redundant API endpoints to keep your codebase clean and maintainable.
Quick Start
# Analyze your Next.js project
npx vibealive analyze .
# Use in different languages
npx vibealive analyze . --locale es # Spanish
npx vibealive analyze . --locale fr # French
npx vibealive analyze . --locale de # German
npx vibealive analyze . --locale pt # Portuguese
# Start MCP server for IDE integration
npx vibealive serve --stdioFeatures
- Smart Analysis: Detects Next.js versions and routing patterns (App Router, Pages Router, hybrid)
- Dependency Tracking: Builds complete dependency graph to find orphaned files
- API Analysis: Identifies unused API endpoints
- Multiple Formats: Generates JSON, Markdown, and other report formats
- MCP Integration: Built-in Model Context Protocol server for IDE/LLM integration
- Build Integration: Webpack plugin and CI/CD pipeline support
- Focused Scans: Specialized analysis for themes, SEO, performance, and comprehensive WCAG 2.2 accessibility compliance
- Internationalization: Multi-language support with community translations
Installation
# Run directly with npx (recommended)
npx vibealive analyze <project-path>
# Or install globally
npm install -g vibealiveDocumentation
See the docs directory for complete documentation:
- Overview - Features and capabilities
- CLI Usage - Command-line interface
- MCP Server - Integration with IDEs and tools
- Build Integration - Automated analysis in CI/CD pipelines
- Internationalization - Multi-language support and translation guide
Contributing
We welcome contributions from the community! Please read our Contributing Guide for details on:
- Development setup and workflow
- Code style and testing requirements
- Pull request process and review guidelines
- Types of contributions we're looking for
Please also review our Code of Conduct which outlines our community standards and expectations for respectful collaboration.
License
MIT
