-
-
Notifications
You must be signed in to change notification settings - Fork 27k
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
CRA --template not picking up github url from a nested folder. #9211
Comments
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
This issue has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue. |
I don't know how common this use case is but this is probably something we can make work. |
@iansu is there any way that I can help out with this issue? :) |
If you'd like to submit a PR adding this feature that would be great. I just put up a PR that affects this same code here: #9412. You would need to make some additional changes in the |
Describe the bug
I am trying to init a
create-react-app
with a github urlThe issue is my github repo has multiple templates, I can run them locally like
But I can run it via the github link, because the project folder is under a nested github folder.
Did you try recovering your dependencies?
This issue does not have dependencies.
Which terms did you search for in User Guide?
https://create-react-app.dev/docs/custom-templates
Environment
Steps to reproduce
(Write your steps here:)
npx create-react-app my-app --use-npm --template git+ssh://[email protected]/<username>/<repo-name>.git/folder1/fodler2/cra-template-javascript
Expected behavior
(Write what you thought would happen.)
It should create the project reading from the github url.
Actual behavior
(Write what happened. Please add screenshots!)
Reproducible demo
(Paste the link to an example project and exact instructions to reproduce the issue.)
The text was updated successfully, but these errors were encountered: