Enhance CLI with new commands, templates, and testing features#74
Merged
Conversation
Merge pull request #51 from Ebyte-Lab/dev
Add commander dependency and CLI flag support
… portfolio, opusify --template badname
Implement opusify list command with template options
…t has been created
Add Opusify command to include plugins and features post-creation
Add automated template testing to CI
…eat/EnhanceCLU
Feat/enhance clu
…provements fix[]:Error Handling & Validation Improvements
…n-navcount Add dynamic navigation generation based on navCount
Implement fully designed portfolio template
Implement full design for eCommerce platform
Implement full SaaS template
Implement full blog design with article pages
Add Vite and React SPA for Portfolio Template
Implement Vite and React for E-Commerce SPA Template
Implement remaining design themes
Add --verbose flag and enable debug logging
Implement security hardening module
Add Prettier and ESLint configuration to projects
Publish package to npm Registry
Change deployment trigger to tag and main branch
…provements refactor[templat]:added igonre for vite shop
Add code of conduct
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces significant improvements to the Opusify CLI project, focusing on automated testing, package publishing, dependency management, and project documentation. The most important changes are the addition of comprehensive template integration tests, a publish workflow for npm, verbose and dynamic dependency injection, and enhanced project metadata and documentation.
Continuous Integration & Testing:
.github/workflows/templates.yml) to automatically test all template combinations (template, architecture, design, sidebar) on pull requests, ensuring new changes do not break template generation.scripts/test-templates.jsandscripts/test-single-template.js, to generate and build all template variants, catching regressions before release. These scripts are integrated into the CI pipeline. [1] [2]Publishing & Distribution:
.github/workflows/publish.yml) to automate publishing the package to npm on pushes tomainor new tags, streamlining the release process..npmignoreto exclude development files, test outputs, and unnecessary configs from the published npm package, reducing package size and exposure of non-essential files.Dependency Management & CLI Improvements:
src/dependencies.jsandsrc/generate.jsto support verbose logging and dynamic dependency injection based on template configuration (design system, sidebar, architecture), with clear CLI output for added dependencies. [1] [2] [3] [4] [5]src/commands/add.jscommand that allows users to add plugins (like authentication, dark mode, analytics) to existing Opusify projects, updating files and dependencies as needed.Project Metadata & Documentation:
package.jsonwith a detailed description, keywords, author, license, Node.js engine requirement, and updated the files field to control what is published. [1] [2]LICENSEfile with the MIT license and aCODE_OF_CONDUCT.mdfor community standards, improving project transparency and contributor guidance. [1] [2]