Behavior is different from node with duckdb library

[fushihara]

Version: deno 2.1.4 windows 10 64bit
We created a simple database with npm's duckdb DB library.
In node.js, a single file named duckdb-direct.duckdb is created after program execution.
This is normal behavior.

However, when the same process is executed in Deno, after the program is completed
will leave a duckdb-direct.duckdb.wal file in addition to the duckdb-direct.duckdb file.

We have created a repository of the complete reproduced code below.
https://github.com/fushihara/duckdb-node-deno-issue

I am using only one library, the following duckdb library.
https://www.npmjs.com/package/duckdb

In node.js, however, only the duckdb-direct.duckdb file is created,
Deno creates two files: duckdb-direct.duckdb and duckdb-direct.duckdb.wal

Since the behavior is different from node.js, we determined that it is a node compatibility issue with deno, so we create an issue in the deno repository.