-
Notifications
You must be signed in to change notification settings - Fork 3
feat: template based installer + tailwind option for cli + git init option for cli #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
feat: template based installer + tailwind option for cli + git init option for cli #6
Conversation
|
@okwasniewski @szymonrybczak mind taking a look at this |
| import fs from 'fs-extra'; | ||
| import path from 'path'; | ||
|
|
||
| export async function setupTailwind(targetPath: string): Promise<void> { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: can we delete the comments, function names are pretty self-explanatory already
| } | ||
|
|
||
| async function updateAppCSSForTailwind(targetPath: string): Promise<void> { | ||
| const appCSSContent = `@tailwind base; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's leave a comment or let's open an issue to properly implement templates where each template which be used based on the option because it's much harder to maintain this kind flow that is added here.
|
@szymonrybczak i added template based installer using github. sparse checkout, removed the copy-templates logic. |
this pr adds tailwind setup following official docs lynx tailwind setup
i have a single util file that takes in all the folders needed for scaffold and copies them into a temp folder and then inside the project (perf is decent).
for tailwind i have 4 files that overwrites the base react but if needed we can make it a standalone template so we just either copy react or react-tailwind template.
This way we dont have to publish the templates to other sources.