Fresh installation won't run

Open-source projects Sealious Playground
1

I’m getting such an error after npm run watch using both ways to start new project. It happens both on Fedora 43 and MacOS

log (5.7 KB)

Error: ENOENT: no such file or directory, open 'dist/front.meta.json'
    at async open (node:internal/fs/promises:634:25)
    at async Object.writeFile (node:internal/fs/promises:1208:14)
    at async FrontendTSBuilder._build (file:///Users/jakub/Documents/sealcode/sealious-playground/node_modules/@sealcode/sealgen/lib/builders/frontend-ts-builder.js:33:5)
    at async Promise.all (index 4)
    at async build (file:///Users/jakub/Documents/sealcode/sealious-playground/node_modules/@sealcode/sealgen/lib/build.js:87:3)
    at async buildProject (file:///Users/jakub/Documents/sealcode/sealious-playground/node_modules/@sealcode/sealgen/lib/build.js:115:5)
    at async file:///Users/jakub/Documents/sealcode/sealious-playground/node_modules/@sealcode/sealgen/lib/cli.js:42:3 {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: 'dist/front.meta.json'
}
2

I couldn’t reproduce it. Just to make sure we’re following the same steps, could you record your session (starting from before the code is cloned) with https://asciinema.org/ and post it here?

3

seal3.demo (163.8 KB)

@kuba-orlik whats your npm version?

4

I’m using npm 10.9.4

From the asciinema I see you’re using sudo to run docker — I advise against it, as it messes with file permissions and can cause weird behavior. Please follow https://hub.sealcode.org/w/sealhub_workflow/narzedzia/docker_i_docker-compose/#rozwi%C4%85zywanie-problem%C3%B3w to enable communicating with docker without sudo, then try again, this time just using docker up instead of sudo docker up

5

ikik, due to fresh install i didnt set up it yet, but on macOS result without sudo is exactly the same.

6

I see. It’s starting to look like some kind of a race condition. What’s the output of npx sealgen build?

7

seal4.demo (27.2 KB)

8

Hm. This looks good. What happens after you run npm run watch now?

9

The error still exists in demo ive sent. I agree that it looks like race condition, sometimes even tmux tries to start, but its immediately closed. Maybe it can be correlated with my tmux setup? Maybe, will try for the science with default one.

Update: nah

10

Does the dist directory exist in your working directory?

11

Ok, I figure it out haha, the problem was with by shell, On my daily basis im using fish, when i switch to bash it works just fine!! lmao

12

Ah! We had a task for that — T2492

But I think it was solved. Apparently not. Maybe adding compatibility with fish-based setups could be your first contribution to our codebase? :smiley:

1 Like