Help with setting twenty locally !
Can somebody help me with setting up Twenty locally ?
When I run these commands (the last one yarn),
nvm install # installs recommended node version
nvm use # use recommended node version
yarn
---------------------------
It throws the following error ----
00h00m00s 0/0: : ERROR: There are no scenarios; must have at least one.
What could be possibly wrong ?
I am referring this document ---
https://twenty.com/developers/local-setup
Twenty - Local Setup
Mostly for contributors or curious developers
25 Replies
Stack Overflow
Yarn ERROR: There are no scenarios; must have at least one
I tried to install Yarn and when I used the yarn command I got:
00h00m00s 0/0: : ERROR: There are no scenarios; must have at least one.
my yarn --version is 0.32. Why doesn't it work?
I would like to ask first that are you using "nvm install # installs recommended node version
nvm use # use recommended node version
yarn" as it is?
If yes ,then you should first run "nvm install 18 " as it is recommended version, then run "nvm use 18" to use this version then you run "corepack enable" to download yarn and then run "yarn"
Recommended Yarn version is 4
Thanks both of you. It worked
Just one more thing. When I start my application, I can see in the terminal that my frontend and server has started. I can see the logs there. Everything looks okay on the terminal. But when I try to access the localhost, I can't access it.
Twenty's server will be up and running at http://localhost:3000. The GraphQL API can be accessed at http://localhost:3000/graphql, and the REST API can be reached at http://localhost:3000/rest.
Twenty's frontend will be running at http://localhost:3001. Just log in using the seeded demo account: [email protected] (password: Applecar2025) to start using Twenty.
I can't access the localhost mentioned in the guide.
Now, you only have to use frontend : http://localhost:3001/
Start frontend and backend separately.Try this, if when you access frontend and any error occurs ,you can share it here.
As far as I remember if any error occurs,it is the memory limit exceeded error

starting frontend throws the above errors
When I start backend, there are no error just logs getting printed but the localhost is inaccessible.

Send logs of terminal for Frontend ,like you sent for backend
Start server in one terminal and then start front in another terminal and share logs of front

Although frontend has started running. But why this memory limit error occuring ?
And server still not running I guess. See below

I have run both frontend and backend in different terminals.
Ok , I faced the same issue earlier, just do this:
VITE_DISABLE_TYPESCRIPT_CHECKER=true and VITE_DISABLE_ESLINT_CHECKER=true in packages/twenty-front/.env
Let me know if it works or not for you
Hi, if you don't mind me piggybacking on this, I have the same issue. The server runs without issue, but the frontend quits after a while.
With your last recommended changes (with the .env), the frontend no longer quits inn the terminal, but the browser doesn't connect either. The page keeps loading infinitely

You can also do this along with the above step, in packages/twenty-front/package.json under "scripts" there is "build" in which set NODE_OPTIONS=--max-old-space-size=4096 , it would be 3000 in that make it 4096
Let me know if it works or not
I've just tried this (still with VITE_DISABLE_TYPESCRIPT_CHECKER=true and VITE_DISABLE_ESLINT_CHECKER=true in packages/twenty-front/.env active) and it's the same result.
It still loads infinitely (I don't even know why)
I then tried disabling the above .env variables (still with the memory limit set to 4096 and later 6144), and I get the Node memory issue. The odd thing is that I see the VM use as much as 7GB of RAM while it runs before quitting
In summary, with the .env variables disabled, I get a memory limit error and the frontend quits. With it enabled, the frontend runs without problem, but the browser never loads the page.
Please let me know if something isn't clear @shyamsundertard
Update: It seems like the infinite loading is it actually working, but my internet isn't so great
I managed to load the page successfully. When signing in with [email protected], there's an error toast with an accompanying error on the server terminal
'relation "core.user" does not exist'
, but I've managed to fix that with help of a previous post (https://discord.com/channels/1130383047699738754/1232694265826770985)
I still don't know why it takes forever to load the app, but it works now. Thank you @shyamsundertardIts credit goes to @charles and @martmull because they helped me with this when it occurred with me.
Big thanks to them. 20/20 👍🏾
@professor_snape sorry I hijacked your thread 😅. I hope you resolve your issues too 👍🏾
@professor_snape is you issue resolved?
@shyamsundertard Can you explain this ?

That heap memory is resolved by increasing the memory upto 4 GB. Thanks for that
But why this metadata version not found keeps on coming in the server terminal. Frontend is running fine.
No issues ! 🫡
I think this is because your database is not set properly.But @charles can you help him with this, I only knew about the Memory limit error and I helped him with that.
@professor_snape do you have redis configured?
The metadata are cached in redis and if you don't have it configured you could get into this kind of issues
Yes, I have redis installed. But do I need to anything additional in order to get metadata cached in redis.
your cache is likely corrupted, could you share its content using Redis Insight or equivalent?