-
Notifications
You must be signed in to change notification settings - Fork 504
Consider splitting out the create command #31
Copy link
Copy link
Closed
Labels
kind: featureNew feature or requestNew feature or requestscope: templatesRelated to an init template, not necessarily to core (but could influence core)Related to an init template, not necessarily to core (but could influence core)solution: unresolvedIssue has been closed by OP but root cause has not necessarily been resolvedIssue has been closed by OP but root cause has not necessarily been resolved
Description
Current Behavior
tsdx create is just another cli command. However, it shares almost zero code with the other commands and in fact makes things harder for them since certain values like paths.js are all undefined.
Desired Behavior
Split out the creation script into a separate package or isolate the code so that it does not interfere or cause headaches throughout the rest of the codebase
Suggested Solution
- Make a separate
create-ts-projectpackage. Thanks to thecreateprefix, it will work withyarn create. So people will be able to enteryarn create ts-project(instead of using npx). - Gluegun appears to have support for templating use .ejs, so that's worth evaluating during Use CLI Framework #17
Who does this impact? Who is this for?
Errbody.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind: featureNew feature or requestNew feature or requestscope: templatesRelated to an init template, not necessarily to core (but could influence core)Related to an init template, not necessarily to core (but could influence core)solution: unresolvedIssue has been closed by OP but root cause has not necessarily been resolvedIssue has been closed by OP but root cause has not necessarily been resolved