-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
yarn create luna-app fails generating expo #82
Comments
Hello @jonsherrard I will be able to have a look later today Meanwhile, what if you try |
same error: Error: ENOENT: no such file or directory, open '/var/folders/lv/hg_m8flx56z455spv6qfnx5h0000gn/T/.create-expo-app/template-cache/@create-luna-app/expo-3.0.3.tgz' |
@jonsherrard perhaps try an older version? 🙈
|
@jonsherrard I'm sorry but I'm not sure that I can reproduce it... it seems to me that there's some sort of Yarn cache issue. Perhaps if you could also try to clear it? Even navigating to You can also check the source code here: https://github.com/LunatiqueCoder/luna/tree/master/templates/expo I believe the most important part is this line of code here: https://github.com/LunatiqueCoder/luna/blob/master/templates/expo/next.config.js#L55 |
real strange. That folder doesn't exist, I tried deleted everything in the I've tried Yarn 1, and Yarn 3.5 same errors. Will report back if I find the fix. |
This failed for me in 2 different ways. First: yarn
When I looked in the directory, there was nothing there. Just an empty yarn.lock file. so then I upgraded yarn. Second:
|
Those issues might be related. Also, here's the Expo template on npm: https://www.npmjs.com/package/@create-luna-app/expo?activeTab=code |
@leogilmour @jonsherrard Are you guys using Ubuntu or Windows? I kept trying to see what's your issue but I can't find anything useful... I actually started building an app with the Expo template and everything is going well 🙈 |
both on osx |
I asked a few friends to try it out and they all confirmed it also works on their side. I really have no idea what's wrong here. Except from pasting links that you probably also found in your searches, I'm a little bit clueless. Perhaps if you clone the repo, run |
Any luck here? I might have an idea for another workaround, but it will take about 1 week for me to be able to implement it, hopefully it won't be too late for you. 🙈 |
so i ended up cloning and getting it working that way :) just went into the repo i got working (the manual way) and yarn linked. tried creating a new project, just to test it for you! still getting the same issue 🤷 |
Happy to hear that! Let me know if you need further help. I just started documenting how to implement Firebase with phone number authentication and Cloud Firestore DB using (almost) the same API for native and web. Also for i18next there's even an easier setup to work seamlessly between platforms. Cheers |
Hello @trubesv Thank you for trying out the template! Unfortunately, I really don't know what's the issue with some people. But I think you are on a good path by cloning the project.
This is probably an issue with the EDIT: Alternatively, you can try to check if the file exists in EDIT2: By the way, expo-router v2 introduces static rendered routes for web and in some future versions they also want to support server side rendering and React Server Components. So in my opinion, trying to use Next.js with React Native will be an useless headache compared to what Expo will offer. But that's just my opinion, don't take it for granted. |
I'm really not sure what happens there, but seems you're close to make it work. 🙈 I guess it's an issue with Yarn Plug N Play, not sure if this package supports it. My first search on google (but I guess you already came across this): https://stackoverflow.com/questions/76015181/the-yarn-plugnplay-manifest-forbids-importing-xyz-here-because-its-not-list
This uses a monorepo and in my opinion introduces a lot of complexity just because of this. Looks more like an enterprise starter.
My opinion:
Not really, depends on what you're looking for. I started with Next.js + Expo for the more complete experience but eventually I decided to stick just with Expo for now since I'm working alone on my pet project and I really need to move fast. Also, Expo (with expo-router) will support Next.js features out of the box, so in the future, this Solito (Next.js + Expo) stack might really be pointless. For example
So when my app is ready I will just start using those features with Expo if they are also ready. Refactoring will be easier I guess. |
Describe the bug
The CLI tool
yarn create luna-app
fails during the creation of a project with expo for RNThe text was updated successfully, but these errors were encountered: