• https://github.com/WasmEdge/WasmEdge/issues/1834

• [x] FileHandle
• [x] fsPromises.access
• [x] fsPromises.appendFile
• [x] fsPromises.chmod Unsupported
• [x] fsPromises.chown Unsupported
• [x] fsPromises.copyFile
• [x] fsPromises.cp
• [x] fsPromises.lchmod Unsupported
• [x] fsPromises.lchown Unsupported
• [x] fsPromises.lutimes
• [x] fsPromises.link
• [x] fsPromises.lstat
• [x] fsPromises.mkdir
• [x] fsPromises.mkdtemp
• [x] fsPromises.open
• [x] fsPromises.opendir
• [x] fsPromises.readdir
• [x] fsPromises.readFile
• [x] fsPromises.readlink
• [x] fsPromises.realpath
• [x] fsPromises.rename
• [x] fsPromises.rmdir
• [x] fsPromises.rm
• [x] fsPromises.stat
• [x] fsPromises.symlink
• [x] fsPromises.truncate
• [x] fsPromises.unlink
• [x] fsPromises.utimes
• [x] fsPromises.watch
• [x] fsPromises.writeFile
• [x] fsPromises.constants
• [x] fs.access
• [x] fs.accessSync
• [x] fs.appendFile
• [x] fs.appendFileSync
• [x] fs.chmod Unsupported
• [x] fs.chmodSync Unsupported
• [x] fs.chown Unsupported
• [x] fs.chownSync Unsupported
• [x] fs.close
• [x] fs.closeSync
• [x] fs.copyFile
• [x] fs.copyFileSync
• [x] fs.cp
• [x] fs.cpSync
• [x] fs.createReadStream
• [x] fs.createWriteStream
• [x] fs.exists
• [x] fs.existsSync
• [x] fs.fchmod Unsupported
• [x] fs.fchmodSync Unsupported
• [x] fs.fchown Unsupported
• [x] fs.fchownSync Unsupported
• [x] fs.fdatasync
• [x] fs.fdatasyncSync
• [x] fs.fstat
• [x] fs.fstatSync
• [x] fs.fsync
• [x] fs.fsyncSync
• [x] fs.ftruncate
• [x] fs.ftruncateSync
• [x] fs.futimes
• [x] fs.futimesSync
• [x] fs.lchmod Unsupported
• [x] fs.lchmodSync Unsupported
• [x] fs.lchown Unsupported
• [x] fs.lchownSync Unsupported
• [x] fs.link
• [x] fs.linkSync
• [x] fs.lstat
• [x] fs.lstatSync
• [x] fs.lutimes
• [x] fs.lutimesSync
• [x] fs.mkdir
• [x] fs.mkdirSync
• [x] fs.mkdtemp
• [x] fs.mkdtempSync
• [x] fs.open
• [x] fs.openSync
• [x] fs.opendir
• [x] fs.opendirSync
• [x] fs.read
• [x] fs.readSync
• [x] fs.readdir
• [x] fs.readdirSync
• [x] fs.readFile
• [x] fs.readFileSync
• [x] fs.readlink
• [x] fs.readlinkSync
• [x] fs.readv
• [x] fs.readvSync
• [x] fs.realpath
• [x] fs.realpathSync
• [x] fs.rename
• [x] fs.renameSync
• [x] fs.rmdir
• [x] fs.rmdirSync
• [x] fs.rm
• [x] fs.rmSync
• [x] fs.stat
• [x] fs.statSync
• [x] fs.symlink
• [x] fs.symlinkSync
• [x] fs.truncate
• [x] fs.truncateSync
• [x] fs.unlink
• [x] fs.unlinkSync
• [x] fs.unwatchFile Unsupported
• [x] fs.utimes
• [x] fs.utimesSync
• [x] fs.watch Unsupported
• [x] fs.watchFile Unsupported
• [x] fs.write
• [x] fs.writeSync
• [x] fs.writeFile
• [x] fs.writeFileSync
• [x] fs.writev
• [x] fs.writevSync
• [x] fs.Dir
• [x] fs.Dirent
• [ ] fs.FSWatcher Unsupported
• [ ] fs.StatWatcher Unsupported
• [x] fs.ReadStream
• [x] fs.Stats
• [x] fs.WriteStream
• [x] fs.constants

I have created a new React App and am using the wasmedge quickjs docs to build another SSR demo.

When I run the App via WasmEdge like this.

wasmedge --dir .:. wasmedge_quickjs.wasm ./server-build/index.js

I get the following error

TypeError: not a function
    at <anonymous> (./server-build/index.js:7568)

The error is pointing to the following line in the machine generated index.js file that is located in the server-build dir

var u = new aa.TextEncoder();

Hi I have a few observations whilst building a new React SSR application.

I get an error (in the client's browser console) as shown below, when the app is started. Interestingly, the page still loads successfully. But I am not wanting to just ignore this browser console error (in case we need to address this)

Uncaught TypeError: n.createRoot(...).hydrate is not a function

Here is my understanding of render vs hydrate

Render provides a way for the app to render a React element into the DOM and return a reference to the component.

Hydrate is essentially the same as render. However, hydrate is used to hydrate a container whose HTML contents were rendered by React's ReactDOMServer.

The original code in the src/index.js file (which the create-react-app command generated) is as follows

const root = ReactDOM.createRoot(document.getElementById('root'));
root.render(
  <React.StrictMode>
    <App />
  </React.StrictMode>
);

Interestingly the above original code works even when we have already implemented all of the other SSR conversions (server/index.js and rollup.config.js etc.) and are starting the server using wasmedge command (as apposed to npm).

Please note, that there is no error in the browser console with the above code (root.render).

We of course change the root.render to root.hydrate in our documentation so I went ahead and did that. The root.hydrate generates the above error. I then also tried importing and using ReactDOMServer instead of just ReactDOM but the error still persists.

Do you have any ideas about solving this error. Thanks so much Tim

Following the the instruction to run the example code in windows 10 environment but an error message. _wasmedge --dir .:. ../target/wasm32-wasi/release/wasmedge_quickjs.wasm hello.js WasmEdge Runtime error message: [error] Bind guest directory failed:52

Could you let me know the problem? thanks

Implement node os module in js, https://github.com/WasmEdge/WasmEdge/issues/1535 . Module name "os" has been used by quickjs, and in windows "node:os" is not a valid name, so I named "nodeos" temporarily. os.constants and os.networkInterfaces() return empty data. os.getPriority(), os.loadavg() and os.userInfo() return fake data. os.cpus() is unimplemented and will throw error. os.totalmem() always return 4294967296 (4GiB, as much as wasm32 can use) and os.freemem() is totalmem() - memory.size.

If run

$ cd example_js
$ wasmedge --dir .:. ../target/wasm32-wasi/release/wasmedge_quickjs.wasm hello.js WasmEdge Runtime

which written in readme will show ReferenceError: could not load module filename 'process'. The module files are not loaded into wasm environment (or maybe there has other way to access the module files that I don't know).

Or use this?

$ wasmedge --dir .:. ./target/wasm32-wasi/release/wasmedge_quickjs.wasm example_js/hello.js WasmEdge Runtime

Although the React App is very small, the performance of rendering it via wasmedge-quickjs is rather slow, compared to rendering it via a local node process:

# macbook pro 2019, i7, 32GB RAM
❯ hyperfine "wasmedge --dir .:. ../../target/wasm32-wasi/release/wasmedge_quickjs.wasm dist/main.js" "node dist/main.js"
Benchmark #1: wasmedge --dir .:. ../../target/wasm32-wasi/release/wasmedge_quickjs.wasm dist/main.js
  Time (mean ± σ):      1.843 s ±  0.024 s    [User: 1.793 s, System: 0.032 s]
  Range (min … max):    1.807 s …  1.877 s    10 runs

Benchmark #2: node dist/main.js
  Time (mean ± σ):      54.5 ms ±   2.8 ms    [User: 42.9 ms, System: 8.9 ms]
  Range (min … max):    51.4 ms …  64.7 ms    51 runs

Summary
  'node dist/main.js' ran
   33.80 ± 1.76 times faster than 'wasmedge --dir .:. ../../target/wasm32-wasi/release/wasmedge_quickjs.wasm dist/main.js' 

Are there any options to improve the performance for SSR in wasm?

https://github.com/second-state/wasmedge-quickjs/blob/main/example_js/react18_ssr/main.mjs#L8 Currently, the CSS can only be imported as a module in the example.

But in reality, the assets will be built with some random file names, something like main.073c9b0a.css. This requires the server can read the content from the file system.

As Wasi has supplied the files and env API, it would be great to add modules like 'wasi_fs' and 'wasi_env`.

Originates from this line: https://github.com/second-state/wasmedge-quickjs/blob/main/modules/http.js#L764

Machine details:

❯ uname -sr
Linux 5.15.0-46-generic

❯ uname -a
Linux bropletop 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

❯ wasmedge --version
wasmedge version 0.9.1

❯ cargo --version
cargo 1.62.0 (a748cf5a3 2022-06-08)

Using a pre-built image of the much simpler HTTP app works for me via cri-o and crun, but I'm not aware of such an image for the react examples, and I am unable to run the the simple HTTP example bytecode locally either (same error).

I have cloned this React blog software [1] which is also part of a comprehensive YouTube tutorial about React [2]. After building it using the standard npm commands (to make sure it worked) I then went ahead and update the source code and config to be rendered server side. I used the SSR [3] instructions from the WasmEdge book.

Everything was successful right up until the final command to start the server i.e. wasmedge --dir .:. wasmedge_quickjs.wasm ./server-build/index.js

Here is the error which was returned from that command.

[2022-04-26 10:31:26.387] [error] instantiation failed: unknown import, Code: 0x62
[2022-04-26 10:31:26.387] [error]     When linking module: "wasi_snapshot_preview1" , function name: "sock_setsockopt"
[2022-04-26 10:31:26.387] [error]     At AST node: import description
[2022-04-26 10:31:26.387] [error]     When linking module: "wasi_snapshot_preview1" , function name: "sock_setsockopt"
[2022-04-26 10:31:26.387] [error]     At AST node: import description
[2022-04-26 10:31:26.387] [error]     At AST node: import section
[2022-04-26 10:31:26.387] [error]     At AST node: module

[1] https://github.com/iamshaunjp/Complete-React-Tutorial/tree/lesson-32/dojo-blog [2] https://www.youtube.com/watch?v=j942wKiXFu8&list=PL4cUxeGkcC9gZD-Tvwfod2gaISzfRiP9d&index=1 [3] https://wasmedge.org/book/en/dev/js/ssr.html

Hi there! This project looks very very cool. However, I've tried running cargo run in the various example_js folders, but none of them seem to work.

target/wasm32-wasi/debug/embed_js_module.wasm: target/wasm32-wasi/debug/embed_js_module.wasm: cannot execute binary file

I also tried embedding some examples' rust code in an existing rust project of mine, and got errors containing:

...out/libquickjs.a, building for macOS-arm64 but attempting to link with file built for unknown-unsupported file format (...)
          Undefined symbols for architecture arm64:
            "_JS_AddModuleExport", referenced fro...

I'm assuming there is no arm64 support yet? Or am I missing some sort of runtime dependency?

If you have a standalone HTTP/HTTPS server module for QuickJS it would be helpful to publish that code standalone, so users don't necessarily need WasmEdge to import and run the server. Thanks.

Node's tty and readline module is implemented. getWindowSize and setRawMode is unsupported now.

As test, because test required assert module is in fs's pr, it will be added after fs's pr merged.

Hi,

I have a few questions:

1. Is the wasmedge-quickjs stable now?
2. I would like to know if is it possible to have a release with all the pre-built files, because some people may not want to re-build the quickjs on their host environment.
3. Is it possible to have version tags and changelogs when some new features are introduced?

Just follow the tutorial. Run the command nohup wasmedge --dir .:. /path/to/wasmedge_quickjs.wasm dist/main.mjs, and then try to visit "http://localhost:8001". Request pending and nothing returns. But It's worked fine with command node dist/main.mjs.

This does not seem to be working from this example on OSX

setTimeout(() => {
    print('timeout 2s');
}, 2000);

Originally posted by @vishalchandra in https://github.com/second-state/wasmedge-quickjs/issues/62#issuecomment-1275054954