Crisperit

Yeah web support would be really nice - I'm voting up for this 👍

As a workaround: Create the file `js_web.dart` ``` @JS() library js; import 'package:js/js.dart'; @JS('window.eval') external dynamic eval(dynamic arg); String evaluate(String jsCode) { return eval(jsCode).toString(); } ``` Create the file `js.dart`...

Same problem - have you found some solution?

@simolus3 I think that SharedWorker itself is an issue on mobile browsers - it is supported in 41.27% according to https://caniuse.com/sharedworkers I've tried to debug your basic example (https://github.com/simolus3/drift/tree/develop/examples/flutter_web_worker_example) https://drift-web-example.netlify.app/#/...

@simolus3 That implementation works for mine Edge mobile browser https://github.com/simolus3/drift/blob/develop/examples/app/lib/database/connection/web.dart#L21-L36 Only worker one is not working in my case

@zs-dima I've came to a conclusion that SharedWorker implementation does not work for mobile browsers and used the experimental approach https://drift.simonbinder.eu/web/#drift-wasm which works fine in all mine cases

@abner I can try to add web support - but I think `JavascriptRuntime` api is a bit not fit for interop JS. Here are the methods: ``` JsEvalResult callFunction(Pointer fn,...

Ah right - I've just copied the legacy config but you're right only `maxStringLen` and `maxArrayValues` makes the sense. Regardless of that in mine opinion it might be a high...