syscall: fs_js.go accesses a fs.O_DIRECTORY constant that's not defined in browsers

[dmitshur]

At Go tip, js/wasm programs inside a browser run into a panic during init of syscall package:

panic: syscall/js: call of Value.Int on undefined

goroutine 1 [running]:
syscall/js.Value.float({{}, 0x0, 0x0}, {0x1f10b5, 0x9})
	syscall/js/js.go:523 +0x10
syscall/js.Value.Int(...)
	syscall/js/js.go:540
syscall.init()
	syscall/fs_js.go:32 +0x37

I see the problem and sent CL 634455 to fix it.

CC @golang/js.

[gabyhelp]

Related Issues

• syscall/js: running web assembly in Wasmer is failing on bad type flag #40366 (closed)
• syscall/js: panic in os.Getpid() when called from wasm in a browser #34627 (closed)

Related Code Changes

• syscall: on wasm, do not panic if "process" global is not defined

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

[gopherbot]

Change https://go.dev/cl/634455 mentions this issue: lib/wasm: provide fs.constants.O_DIRECTORY definition