-
Notifications
You must be signed in to change notification settings - Fork 395
Breaks with @react-native-community/[email protected] #38
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
Comments
Okay, this seems to be a general problem with the latest version of I'm seeing the issue even with a plain setup. npx [email protected] init YoYoYo With the same error
They don't seem to be using the latest template version yet either. |
Thanks for creating the issue and raising awareness about the new CLI changes. Luckily it seems like it can be fixed easily by creating a template config file and changing the folder structure. As this will break the process in the current CLI, I'll do that in a separate branch and release a pre-release version. |
Okay, I did some progress with the changes but I'm going to pause it for now. As you already figured out, the current (and also the one from It also seems like the CLI documentation isn't up to date anymore as a few things don't work as described ( Let's just wait a little more until the things get a bit more stable 😄. |
Hey! Looks like we didn't communicate clearly enough on how the new init works. When you call:
the init will use the To use a new init in RC phase you need to use npx [email protected] init [email protected] Project After RN 0.60 is stable, it's gonna be as easy as:
I think the docs are pretty clear on that. However if you still find something not being obvious enough, please send PRs with clarifications 🙏 (we're clearly biased because we created the new command, so any outside feedback is appreciated). It's also worth to note that the legacy init (as we call |
Hi Michał 😄 Oh wow, I feel honored to have you here! Thanks a lot for helping out and clarify a few things. There are a few things that are documented differently than the actual implementation, which confused me and that's why I paused for now. I'm also not quite sure if it's either documented or implemented "incorrectly" because both could be intentional. But hey, let's move that discussion over to the soon to be created PR in the CLI repo. 👍 Cheers |
If you mean moving this template to CLI, then that's not a good idea. However we're happy to have it in |
Ah I see how you came here 😄. Yeah no, I meant the PR which contains the doc changes because it's not directly related with this template. P.S. I agree it's not a good idea to integrate it directly in the CLI. |
FYI: I created a separate issue to discuss how to handle both CLI versions. |
I see that RN 0.60 has been released. Is there a way to use this template with the current version of the CLI? |
The migration process isn't finished yet, so you'd have to be a bit patient. But as Michał mentioned, the legacy CLI is still working, you can use that in the meantime. 🙂 |
@paulmelnikow I submitted PR #45 to make master-cli-v2 branch work. It hasn't been merged yet you can try out this command for now.
|
You can now use the new CLI to create a project 🎉 : |
@emin93 Getting the following exception on an unchanged project using the above command:
(putting here because the template github repo doesn't accept issues) |
On first glance it looks like you're using an old version of RN. But that shouldn't be if you set up the project with the exact above command. Can you check the How do you mean the template repo doesn't accept issues? |
Expected results
The project should initialise properly.
Observed results
Can't be built because of the new template api documented here
Logs
Steps to reproduce
The text was updated successfully, but these errors were encountered: