Jason Rogers

For what it's worth (maybe as a reference?), Stardog recently added visualization along these lines to its Stardog Studio product (initial release blog post, with some gifs, [here](https://www.stardog.com/blog/picture-this-visual-results-in-studio/)). The visualization...

Sounds good.

Thanks for this issue. However, I don't think stardog.js should accept a filename, because I don't think it should be in the business of reading files from a user's system...

We're currently working on a 2.0 release of stardog.js, which may improve things here. If it doesn't, it's something that we can consider doing then. Thanks!

> The following code restricts the accepted query params to `graph-uri`. That is the only supported param, at the moment. But the inflexibility means each new param requires a stardog.js...

Example: https://github.com/stardog-union/stardog.js/blob/v2-typescript/lib/db/main.ts#L26 Currently, TypeScript can flag errors when you supply params that are unexpected. Does that seem too inconvenient to be of benefit? It's pretty nice to not have to...

> Am I wrong to think that a user of stardog.js could then ignore the error? Or, could the type simply be open to other stuff so it validates known...

Let's wait and see (for now, at least) whether a user of stardog.js (other than ourselves) wants this.

@nolanlawson Nice minimal repro, and thanks for the workaround. As far as my team is concerned, that workaround is probably sufficient -- and _extremely_ minimal in cost -- for us...

I just want to comment that everything described by @anderoonies happens for me as well. For what's worth, I am also on an M1 Mac, but on macOS Monterey.