Builder and viewer are not starting locally

[Dmitriy-Metelya]

Got stuck starting builder and viewer locally

Hi. I got stuck at step 5 of your local setup manual.
Windows 11, bun 1.1.42, node 22, docker 27.4.0, nvm 0.39.7

To Reproduce

1. Accomplish first 4 steps of local setup: packages, install, enviroment and database running.
2. bunx turbo dev --filter=builder... --filter=viewer...

Expected behavior

Builder and viewer running on default ports of localhost.

Failed with errors:

[baptisteArno]

Are you sure you ran bun install? What's the output of this command?

[Dmitriy-Metelya]

Are you sure you ran bun install? What's the output of this command?

I am.

$ bun install
[0.00ms] ".env"
bun install v1.1.42 (50eec002)
Saved yarn.lock

$ husky

+ @biomejs/[email protected]
+ @tolgee/[email protected]
+ [email protected]
+ [email protected]
+ [email protected]
+ [email protected]

485 packages installed [38.72s]

Blocked 1 postinstall. Run `bun pm untrusted` for details.

then

$ bun pm untrusted
[0.00ms] ".env"
bun pm untrusted v1.1.42 (50eec002)

.\node_modules\msw @2.4.11
 » [postinstall]: node -e "try{require('./config/scripts/postinstall')}catch(e){}"

.\node_modules\workerd @1.20240718.0
 » [postinstall]: node install.js

.\node_modules\puppeteer @22.15.0
 » [postinstall]: node install.mjs

These dependencies had their lifecycle scripts blocked during install.

If you trust them and wish to run their scripts, use `bun pm trust`.

[baptisteArno]

Can you run git status? What does it say?

[Dmitriy-Metelya]

I'm not sure how but versions turned out to be lower than they are in actual repository. I'm sure I got the repo initially with

"packageManager": "[email protected]",
  "engines": {
    "node": "^22"
  },

last week, so here I just actualized them. From the beginning with up to date bun and node versions I had the same problems, described in issue.

[baptisteArno]

Ok, can you nuke the project and clone it again? Then make sure you have bun 1.1.42 and node v22 installed.

Then once you ran bun install make sure node_modules/solid-elements exists

[Sinnay-p]

Sorry for hijacking the issue but i am facing similar issue when i try to run the project locally. My problem is a bit different

[Dmitriy-Metelya]

Ok, can you nuke the project and clone it again? Then make sure you have bun 1.1.42 and node v22 installed.

Then once you ran bun install make sure node_modules/solid-elements exists

Done. Just the same result, but 17 similar error messages more. Now I remember why node was 20 - I experimented with node versions trying to get rid of errors.

So with bun 1.1.42 and node 22.13.1 node_modules/solid-element and other packages are there.

[Sinnay-p]

Ok, can you nuke the project and clone it again? Then make sure you have bun 1.1.42 and node v22 installed.
Then once you ran bun install make sure node_modules/solid-elements exists

Done. Just the same result, but 17 similar error messages more. Now I remember why node was 20 - I experimented with node versions trying to get rid of errors.

So with bun 1.1.42 and node 22.13.1 node_modules/solid-element and other packages are there.

Are you getting the same errors regarding the isolated-vm on bun?

[ernaneluis]

I am also facing same problem

[baptisteArno]

Which error?

1. Describe the bug
2. How to reproduce it
3. What you expected