Replies: 5 comments 9 replies
-
|
See #1734 — the PR hasn't been merged yet and we'd be happy to have more people test it. |
Beta Was this translation helpful? Give feedback.
6 replies
-
|
I think you also have to clone (and modify) client/duckdb.js if you want to use |
Beta Was this translation helpful? Give feedback.
-
|
The other thing to clarify for @fundef1 is that |
Beta Was this translation helpful? Give feedback.
-
|
thanks, I ended up using (copying) the approach of @Fil . Worked out of the box. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I am getting various errors trying to use OF version 1.12.0 when accessing DuckDB files created using latest CLI (v 1.1.0). They appear to derive from lack of forward compatibility. I have found work-arounds for a few of them (e.g. dropping keys/indices, materializing views as tables), but some errors persist. I'd rather not look for more workarounds, and have wasm compatibility with latest CLI. If you advise me the easiest way to install/configure Observable Framework to incorporate @Fil's PR, I'd be happy I'm not a real node jock. @mbostock , if you can correct how I should invoke npx or npm to test the PR with my db, I'll do it. I tried so far: Looking forward to all this new goodness... |
Beta Was this translation helpful? Give feedback.
-
|
Install Framework the usual way (note: I'm using npx @observablehq/framework@latest createopen "build": "yarn observable build",
"dev": "yarn observable preview",
"deploy": "yarn observable deploy",
"observable": "tsx node_modules/@observablehq/framework/src/bin/observable.ts"
"@observablehq/framework": "observablehq/framework#fil/duckdb-wasm-1.29",run In (this should show duckdb You can then edit the Let me know how it goes. |
Beta Was this translation helpful? Give feedback.
-
|
Splendid! Thanks for the guidance.
Not (yet) being familiar with yarn, and being unsure about its installation and versioning…
… I first tried just changing one line in my existing hello-framework/package.json:
`"@observablehq/framework": "observablehq/framework#fil/duckdb-wasm-1.29",`
And running:
`npm run dev -- --port 4321 --host 0.0.0.0 &`
Only to fail with:
```
dev
observable preview --port 4321 --host 0.0.0.0
sh: observable: command not found
```
So, I then made the remaining changes to package.json and figured out I probably needed to use `-g` when I installed yarn, as:
`npm -g install yarn
`
… and found that running yarn included:
`warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
`
but otherwise succeeded as hoped and all my DuckDB wasm vs CLI compatibility issues were resolved.
Hooray, and huge thanks,
I will follow up on this issue only if wasm/CLI compatibility issues arise.
|
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I have new issues with running with this PR. ISSUE: An OF app which works with
Steps to reproduce:
file:quakes.md:
edit: Apologies! I find this same issue regardless of using this PR or using latest. Either this is operator (me) error, or should be reported elsewhere (where?). Some Further details: browser: now also tested with chrome. Error message is a little different.
|
Beta Was this translation helpful? Give feedback.
2 replies
-
|
This feels surprising, on my machine the mime type for these resources appears to be correct ( Ca you share more information about your environment (OS, node version, and maybe the contents of package-lock.json?) |
Beta Was this translation helpful? Give feedback.
-
|
Maybe the issue is with the server that you run on the dist folder? How do you open the built site? |
Beta Was this translation helpful? Give feedback.
-
|
See my edits to original report. THis is not just on your PR. My bad... The web server is apache2 running on linux. I am browsing the static built site on firefox and chrome from windows box. package-lock.json: |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks for the tip re: apache. Researching the config needed for wasm now. Will confirm success soon (I hope). |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Success confirmed after configuring apache2 to serve wasm.. oh, and, and clearing browser cache .... (doh). sorry for the noise here. All good again. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi I'm having trouble getting the latest version of duckdb.
I deleted the cache under .observablehq/cache and I can see observable pulling in 1.28.0 and repopulating the cache.
package.json says
the duckdb version under node_modules is indeed 1.29.0.
ont the forum it refers to package.json.
duckdb issue 1661 is closed... but I can't get it to work.
thanks!
Beta Was this translation helpful? Give feedback.
All reactions