Comments (6)
bartlomieju
commented on May 29, 2024
1
This is because we currently don't support "lifecycle hooks" when installing npm dependencies (eg. postinstall script). We have a PR that implements that that's WIP: #23558.
You can work around this for now if you use "bring your own node modules" - by installing using npm/yarn/pnpm.
from deno.
bartlomieju
commented on May 29, 2024
1
It's an internal bug in Deno, but it seems easy enough to fix it to make example from DuckDB's page work. I'll try to have it done tonight.
from deno.
nshiab
commented on May 29, 2024
Thank you!
from deno.
MaximePawlakFr
commented on May 29, 2024
Hi @nshiab , have you succeeded?
I tried but I got this error:
============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.
Platform: macos aarch64
Version: 1.40.4
Args: ["deno", "run", "--allow-all", "data/index.ts"]
thread 'main' panicked at cli/napi/js_native_api.rs:2508:56:
called `Result::unwrap()` on an `Err` value: BadType { actual: "v8::data::Value", expected: "v8::data::Array" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
My data/index.ts contains:
import duckdb from "duckdb";
console.log(duckdb)
const db = new duckdb.Database(":memory:");
console.log(db)
The steps are:
- setup the project with npm:
npm init npm install duckdb- try to run:
deno run --allow-all ./data/index.ts
error: Uncaught (in promise) Error: Cannot find module 'MY_PATH/node_modules/.deno/[email protected]/node_modules/duckdb/lib/binding/duckdb.node'
Require stack:
- MY_PATH/node_modules/.deno/[email protected]/node_modules/duckdb/lib/duckdb-binding.js
- MY_PATH/node_modules/.deno/[email protected]/node_modules/duckdb/lib/duckdb.js
- MY_PATH/node_modules/.deno/[email protected]/node_modules/duckdb/lib/duckdb.js
at Function.Module._resolveFilename (node:module:622:15)
at Function.Module._load (node:module:500:27)
at Module.require (node:module:675:19)
at require (node:module:789:16)
at Object.<anonymous> (file://MY_PATH/node_modules/.deno/[email protected]/node_modules/duckdb/lib/duckdb-binding.js:4:15)
at Object.<anonymous> (file://MY_PATH/node_modules/.deno/[email protected]/node_modules/duckdb/lib/duckdb-binding.js:7:4)
at Module._compile (node:module:731:34)
at Object.Module._extensions..js (node:module:745:10)
at Module.load (node:module:656:32)
at Function.Module._load (node:module:537:12)
- then move to duckdb:
cd node_modules/duckdb - install it:
npm install - I can see the missing
duckdb.nodeunder node_modules > duckdb > lib > binding > duckdb.node - run again:
deno run --allow-all ./data/index.ts - and finally get:
============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.
Platform: macos aarch64
Version: 1.40.4
Args: ["deno", "run", "--allow-all", "./data/index.ts"]
thread 'main' panicked at cli/napi/js_native_api.rs:2508:56:
called `Result::unwrap()` on an `Err` value: BadType { actual: "v8::data::Value", expected: "v8::data::Array" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
By adding RUST_BACKTRACE=1, I get:
============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.
Platform: macos aarch64
Version: 1.40.4
Args: ["deno", "run", "--allow-all", "./data/index.ts"]
thread 'main' panicked at cli/napi/js_native_api.rs:2508:56:
called `Result::unwrap()` on an `Err` value: BadType { actual: "v8::data::Value", expected: "v8::data::Array" }
stack backtrace:
0: _rust_begin_unwind
1: core::panicking::panic_fmt
2: core::result::unwrap_failed
3: core::result::Result<T,E>::unwrap
4: _napi_set_element
5: __ZNK4Napi6Object3SetIA11_cEEbjRKT_
6: __ZN10NodeDuckDBC2EN4Napi3EnvENS0_6ObjectE
7: __ZN4Napi5AddonI10NodeDuckDBE4InitENS_3EnvENS_6ObjectE
8: _napi_register_module_v1
9: deno_napi::op_napi_open<NP>::v8_fn_ptr
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
And by adding RUST_BACKTRACE=full, I get:
============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.
Platform: macos aarch64
Version: 1.40.4
Args: ["deno", "run", "--allow-all", "./data/index.ts"]
thread 'main' panicked at cli/napi/js_native_api.rs:2508:56:
called `Result::unwrap()` on an `Err` value: BadType { actual: "v8::data::Value", expected: "v8::data::Array" }
stack backtrace:
0: 0x1018f46b0 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hade97c44b56fc870
1: 0x100bcd6b0 - core::fmt::write::h81cbefbffc581dab
2: 0x101901918 - std::io::Write::write_fmt::h125c60058ebfe43c
3: 0x1018f4508 - std::sys_common::backtrace::print::hfa54be0dd0cf5860
4: 0x10190838c - std::panicking::default_hook::{{closure}}::h4235e0929057f079
5: 0x1019080d0 - std::panicking::default_hook::hcf67171e7c25be94
6: 0x100b05c18 - deno::setup_panic_hook::{{closure}}::h71a800dcbf73da30
7: 0x101908a2c - std::panicking::rust_panic_with_hook::h1767d40d669aa9fe
8: 0x1018f49e8 - std::panicking::begin_panic_handler::{{closure}}::h83ff281d56dc913c
9: 0x1018f4954 - std::sys_common::backtrace::__rust_end_short_backtrace::h2f399e8aa761a4f1
10: 0x1019086b4 - _rust_begin_unwind
11: 0x100bd78cc - core::panicking::panic_fmt::hc32404f2b732859f
12: 0x100bd16f0 - core::result::unwrap_failed::h2ea3b6e22f1f6a7c
13: 0x1007888a0 - core::result::Result<T,E>::unwrap::h2d955a3171e3fa0a
14: 0x10078f060 - _napi_set_element
15: 0x11a7719c0 - __ZNK4Napi6Object3SetIA11_cEEbjRKT_
16: 0x11a7710a4 - __ZN10NodeDuckDBC2EN4Napi3EnvENS0_6ObjectE
17: 0x11a7728a0 - __ZN4Napi5AddonI10NodeDuckDBE4InitENS_3EnvENS_6ObjectE
18: 0x11a771f38 - _napi_register_module_v1
19: 0x101408960 - deno_napi::op_napi_open<NP>::v8_fn_ptr::h315a352275b5cff8
Have you managed to use duckdb in Deno?
What could I do?
Best
from deno.
MaximePawlakFr
commented on May 29, 2024
--Update--
I've upgraded to deno 1.43.1 (was 1.40.4), and now I get this error:
error: Uncaught (in promise) Error: Error in native callback
at Object.Module._extensions..node (node:module:704:20)
at Module.load (node:module:597:32)
at Function.Module._load (node:module:484:12)
at Module.require (node:module:609:19)
at require (node:module:715:16)
at Object.<anonymous> (file:MYPATH/node_modules/.deno/[email protected]/node_modules/duckdb/lib/duckdb-binding.js:4:15)
at Object.<anonymous> (file:MYPATH/node_modules/.deno/[email protected]/node_modules/duckdb/lib/duckdb-binding.js:7:4)
at Module._compile (node:module:659:34)
at Object.Module._extensions..js (node:module:673:10)
at Module.load (node:module:597:32)
Do you have any idea?
from deno.
nshiab
commented on May 29, 2024
Hi @MaximePawlakFr!
For now, I am using node/npm. But @bartlomieju is working on it #23558.
from deno.
Related Issues (20)
- Missing completions in VSCode
- repl_cwd is flaky HOT 1
- NODE_DEBUG env var should be handled internally
- LSP cannot get completion info when file has `using` or `await using` declaration HOT 1
- upgrade_prompt is flaky
- Crash in deno_io due to dependency issue
- npm:web-push not working
- ReferenceError: EISDIR is not defined | node pollyfill is missing a constant HOT 1
- Deno panic when running modules from jsr.io via https specifiers HOT 1
- Fatal process out of memory: Oilpan: CagedHeap reservation. HOT 6
- undefined symbol: node_module_register HOT 1
- Loading React types cripples LSP performance HOT 1
- Cannot read files from `/proc/self/fd` since Deno 1.43 HOT 8
- `node:fs/promises`: Neither `fd.read` nor `fd.write` honor the `position` argument
- std/node/_events.mjs assumes existence of process, crashes on calling process.emitWarning
- Improved types for `Deno.serve` in 2.0
- `deno doc` stack overflows on namespace exporting itself
- rejection_handled_web_process is flaky
- `npm:@grpc/grpc-js` support HOT 2
- Permission regression with `deno compile` HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from deno.