Louis

Did you try to delete your packager lock? It seems to be broken. This error should happen with any node package, not only this one.

the app doesn't even start when using the newest expo SDK with this package. Important breaking changes

I had the same problem. For me it was that the PYTHONPATH environment variable was not set to where graphenelibos was installed for me. Use `whereis graphenelibos` to locate the...

The issue is not the colon, but rather the newline. I'll investigate on how newlines can be used in the request.

The issue was that the imported (and also any manually written) parameter values have not been encoded thus resulting in invalid bruno files. Fix is created. With the fix, everything...

Thanks for your collection! I could recreate your issue and created a fix for it. When importing the collection, the parameters now look as expected:  This actually affected not...

I think adjusting the Bru Lang is the correct way to go in the long term. I haven't checked all the Bruno updates since then. Since the Bru Lang will...

@helloanoop I believe we can close the PR #804 (fix for #802) then? The issue will be resolved when the Bru Lang supports multiline strings right?

It's in the official documentation now: https://github.com/suren-atoyan/monaco-react?tab=readme-ov-file#use-monaco-editor-as-an-npm-package I believe we can close this issue.

I just ran the function locally on my mac. I could not reproduce the error there. It has to do with the Windows Function environment in combination with the new...