Replies: 3 comments 2 replies
-
First, I would first try clearing your npm cache; you probably have the older version of parquet-wasm cached here. rm -rvf src/.observablehq/cache/_npm Second, you’ll want to use Your logs output suggest that you’re using DuckDB, which isn’t evident from your code, so perhaps there’s something else that’s going on here? This code works for me to load a Parquet file: ```js
const gaia = FileAttachment("lib/gaia-sample.parquet").parquet();
```
```js
display(gaia);
``` If you want to use DuckDB, this also worked for me using Framework’s SQL cells: ---
sql:
gaia: lib/gaia-sample.parquet
---
```sql
SELECT * FROM gaia LIMIT 10
``` Of course you can also use ```js
const gaia = FileAttachment("lib/gaia-sample.parquet").parquet();
```
```js
const db = DuckDBClient.of({gaia});
```
```js
db.sql`SELECT * FROM gaia LIMIT 10`
``` |
Beta Was this translation helpful? Give feedback.
-
Thank you for the quick answer and sorry for the noise. I indeed cleared the node cache several times before opening an issue, but always got the error. As you noticed it, I'm experimenting with various input and performed an update 1.6.0->1.7.0. I wonder if the browser's cache is faulty as I do not have the issue when opening a private window. I'm on Safari/MacOS. The same uri called from two windows:
|
Beta Was this translation helpful? Give feedback.
-
I removed the whole |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello 👋,
using observable framework 1.7.0 with bun/yarn and doing something relatively simple in a md file:
Log from the terminal:
And in the browser, an error:
I don't really understand with two versions of parquet are being loaded. Any idea?
Beta Was this translation helpful? Give feedback.
All reactions