Ollie

I'm still having this issue with a regex that also contains `\.`. I cloned dev branch and ran the unit test posted by JarLob above, it still failed with both...

Here is my particular regex: ```js var urlRegex = /(https?)\:\/\/[A-Za-z0-9\.\-]+(\/[A-Za-z0-9\?\&\=;\+!'\(\)\*\-\._~%]*)*/gi; ``` The error occurs on this line: https://github.com/sebastienros/esprima-dotnet/blob/dev/src/Esprima/Scanner.cs#L602 when processing the first `\` escape character in the line;

I did further reading and this seems to be related to the `broadcast-channel` package itself not being handled (or maybe not being configured correctly to be handled) by webpack and...

I'm not sure why it didn't happen previously to me with v3 as it seems both query v3 and v4 are using the same version of the broadcast-channel package, which...

No problem, appreciate the help. Nami has moved to the new API as far as I understand. The `key` string is 84 bytes. Calling the WASM from node I was...

This looks like it could be extremely helpful, thank you! I will take a closer look tomorrow evening

Thanks @gavinharris-dev I think I've managed to get where I need now. I have a couple of questions: 1. `baseAddress` is not declared here - I was able to construct...

I'm having this issue as well. Initially using an audio session id of 0, but now even when I grab the ExoPlayer's session id directly from my background service it...

I've implemented a working solution for now where I handle the whole validation myself, which works fine. The `onChange` firing when the form validates would offer the same functionality, the...

Is this still being considered for a fix? I've again found myself in a similar position in a different application where it would be desirable for me to encapsulate the...