fix(js-template): support JavaScript templates in project generation#12
Merged
Conversation
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
1 participant
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 addresses issue #11 by implementing full support for JavaScript project templates in the create-nexter CLI tool.
Changes include:
Added separate JavaScript templates alongside TypeScript templates.
Updated the project generator to select and copy the correct template based on user language choice (js or ts).
Ensured clean project setup with proper configuration files for both JS and TS projects.
Verified successful project creation and functioning for both JavaScript and TypeScript options.
This enhancement improves the CLI’s flexibility and usability by catering to developers who prefer JavaScript or TypeScript.