typebot.io icon indicating copy to clipboard operation
typebot.io copied to clipboard

Builder and viewer are not starting locally

Open Dmitriy-Metelya opened this issue 1 year ago • 13 comments

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:

Image

Image

Image

Dmitriy-Metelya avatar Feb 04 '25 17:02 Dmitriy-Metelya

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

baptisteArno avatar Feb 05 '25 10:02 baptisteArno

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`.

Dmitriy-Metelya avatar Feb 05 '25 18:02 Dmitriy-Metelya

Can you run git status? What does it say?

baptisteArno avatar Feb 07 '25 09:02 baptisteArno

Image

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.

Dmitriy-Metelya avatar Feb 07 '25 13:02 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

baptisteArno avatar Feb 07 '25 13:02 baptisteArno

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

Image

Image

Sinnay-p avatar Feb 09 '25 23:02 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.

Dmitriy-Metelya avatar Feb 10 '25 12:02 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.

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

Sinnay-p avatar Feb 10 '25 21:02 Sinnay-p

I am also facing same problem

ernaneluis avatar Feb 11 '25 01:02 ernaneluis

Which error?

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

baptisteArno avatar Feb 17 '25 10:02 baptisteArno

Running docker compose -f docker-compose.build.yml build will reproduce it.

magick93 avatar Aug 04 '25 20:08 magick93

@magick93 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

baptisteArno avatar Aug 06 '25 13:08 baptisteArno

This happens to me as well, both locally and following the manual deploy guide


 bunx turbo build --filter=viewer...
turbo 2.5.3

• Packages in scope: @typebot.io/ai, @typebot.io/anthropic-block, @typebot.io/blink-block, @typebot.io/blocks-base, @typebot.io/blocks-bubbles, @typebot.io/blocks-core, @typebot.io/blocks-inputs, @typebot.io/blocks-integrations, @typebot.io/blocks-logic, @typebot.io/bot-engine, @typebot.io/cal-com-block, @typebot.io/chat-api, @typebot.io/chat-node-block, @typebot.io/chat-session, @typebot.io/conditions, @typebot.io/credentials, @typebot.io/deepseek-block, @typebot.io/dify-ai-block, @typebot.io/elevenlabs-block, @typebot.io/emails, @typebot.io/env, @typebot.io/events, @typebot.io/forge, @typebot.io/forge-repository, @typebot.io/gmail-block, @typebot.io/groq-block, @typebot.io/groups, @typebot.io/js, @typebot.io/legacy, @typebot.io/lib, @typebot.io/logs, @typebot.io/mistral-block, @typebot.io/nocodb-block, @typebot.io/open-router-block, @typebot.io/openai-block, @typebot.io/perplexity-block, @typebot.io/playwright, @typebot.io/posthog-block, @typebot.io/prisma, @typebot.io/qrcode-block, @typebot.io/react, @typebot.io/results, @typebot.io/rich-text, @typebot.io/runtime-session-store, @typebot.io/schemas, @typebot.io/segment-block, @typebot.io/settings, @typebot.io/theme, @typebot.io/together-ai-block, @typebot.io/tsconfig, @typebot.io/typebot, @typebot.io/ui, @typebot.io/user, @typebot.io/variables, @typebot.io/whatsapp, @typebot.io/workspaces, @typebot.io/zendesk-block, @typebot.io/zod, bot-engine, typebot-js, viewer
• Running build in 61 packages
• Remote caching disabled
@typebot.io/prisma:db:generate: cache bypass, force executing 0435b361da5aee8e
@typebot.io/prisma:db:generate:
@typebot.io/prisma:db:generate: $ dotenv -e ./.env -e ../../.env -- tsx scripts/db-generate.ts
@typebot.io/env:build: cache hit (outputs already on disk), suppressing logs 1b3954b7a89065f2
typebot-js:build: cache hit (outputs already on disk), suppressing logs 37a4504b5d8d2741
@typebot.io/prisma:db:generate: Executing for PostgreSQL schema
@typebot.io/prisma:db:generate: Prisma schema loaded from postgresql/schema.prisma
@typebot.io/prisma:db:generate:
@typebot.io/prisma:db:generate: ✔ Generated Prisma Client (v6.9.0) to ./../../node_modules/@prisma/client in 478ms
@typebot.io/prisma:db:generate:
@typebot.io/prisma:db:generate: Start by importing your Prisma Client (See: https://pris.ly/d/importing-client)
@typebot.io/prisma:db:generate:
@typebot.io/prisma:db:generate: Tip: Want to turn off tips and other hints? https://pris.ly/tip-4-nohints
@typebot.io/prisma:db:generate:
@typebot.io/prisma:db:generate:
bot-engine:build: cache hit (outputs already on disk), suppressing logs e11909b40c1a2ca2
@typebot.io/js:build: cache hit (outputs already on disk), suppressing logs 3e9ea7b204049909
@typebot.io/react:build: cache hit (outputs already on disk), suppressing logs b8556c3fb06ad24e
viewer:build: cache miss, executing 9fca84a62a08c9e8
viewer:build:
viewer:build: $ dotenv -e ./.env -e ../../.env -- next build
viewer:build: - event [next-runtime-env] read environment variables prefixed with 'NEXT_PUBLIC_' from process.env.
viewer:build: - ready [next-runtime-env] wrote browser runtime environment variables to '/opt/typebot.io/typebot.io/apps/viewer/public/__ENV.js'.
viewer:build:    â–² Next.js 15.3.0
viewer:build:
viewer:build:    Creating an optimized production build ...
viewer:build: Failed to compile.
viewer:build:
viewer:build: ../../packages/runtime-session-store/node_modules/isolated-vm/isolated-vm.js
viewer:build: Module not found: Can't resolve './out/isolated_vm'
viewer:build:
viewer:build: https://nextjs.org/docs/messages/module-not-found
viewer:build:
viewer:build: Import trace for requested module:
viewer:build: ../../packages/runtime-session-store/src/index.ts
viewer:build: ./src/app/api/integrations/openai/streamer/route.ts
viewer:build:
viewer:build: ../../packages/variables/node_modules/isolated-vm/isolated-vm.js
viewer:build: Module not found: Can't resolve './out/isolated_vm'
viewer:build:
viewer:build: https://nextjs.org/docs/messages/module-not-found
viewer:build:
viewer:build: Import trace for requested module:
viewer:build: ../../packages/variables/src/codeRunners.ts
viewer:build: ../../packages/variables/src/parseVariables.ts
viewer:build: ./src/app/api/integrations/openai/streamer/route.ts
viewer:build:
viewer:build: ../../packages/runtime-session-store/node_modules/isolated-vm/isolated-vm.js
viewer:build: Module not found: Can't resolve './out/isolated_vm'
viewer:build:
viewer:build: https://nextjs.org/docs/messages/module-not-found
viewer:build:
viewer:build: Import trace for requested module:
viewer:build: ../../packages/runtime-session-store/src/index.ts
viewer:build: ./src/pages/api/typebots/[typebotId]/blocks/[blockId]/executeWebhook.ts
viewer:build:
viewer:build: ../../packages/variables/node_modules/isolated-vm/isolated-vm.js
viewer:build: Module not found: Can't resolve './out/isolated_vm'
viewer:build:
viewer:build: https://nextjs.org/docs/messages/module-not-found
viewer:build:
viewer:build: Import trace for requested module:
viewer:build: ../../packages/variables/src/codeRunners.ts
viewer:build: ../../packages/variables/src/parseVariables.ts
viewer:build: ./src/pages/api/integrations/stripe/createPaymentIntent.ts
viewer:build:
viewer:build: ../../packages/variables/node_modules/isolated-vm/isolated-vm.js
viewer:build: Module not found: Can't resolve './out/isolated_vm'
viewer:build:
viewer:build: https://nextjs.org/docs/messages/module-not-found
viewer:build:
viewer:build: Import trace for requested module:
viewer:build: ../../packages/variables/src/executeFunction.ts
viewer:build: ../../packages/forge/blocks/openai/src/actions/askAssistant.ts
viewer:build: ../../packages/forge/blocks/openai/src/index.ts
viewer:build: ../../packages/forge/repository/src/definitions.ts
viewer:build: ../../packages/blocks/core/src/helpers.ts
viewer:build: ../../packages/deprecated/bot-engine/dist/index.js
viewer:build: ./src/components/TypebotPageV2.tsx
viewer:build: ./src/pages/[[...publicId]].tsx
viewer:build:
viewer:build:
viewer:build: > Build failed because of webpack errors
viewer:build: error: script "build" exited with code 1
viewer:build: ERROR: command finished with error: command (/opt/typebot.io/typebot.io/apps/viewer) /root/.bun/bin/bun run build exited (1)
viewer#build: command (/opt/typebot.io/typebot.io/apps/viewer) /root/.bun/bin/bun run build exited (1)

 Tasks:    6 successful, 7 total
Cached:    5 cached, 7 total
  Time:    26.293s
Failed:    viewer#build

 ERROR  run failed: command  exited (1)

isolated-vm is installed correctly:

Image

This also happens locally

localhosted avatar Aug 08 '25 17:08 localhosted