Open dav1d-wright opened 1 month ago
The TSC definitions should be usable without any extra work. Are you able to attach src/autogenerated_types.ts
or attach/link to a way I can reproduce the error?
@brendandahl Thank you for the prompt feedback, I am currently trying to put together an MRE that reproduces this issue. I'm afraid I don't think I can disclose any code as this is protected by IP. My first attempts to reproduce have unfortunately failed, as compilation seems to work. I will get back if I manage to reproduce it.
I did manage to reproduce the issue after all. It seems that the npm
build behaves differently depending on whether the file is called autogenerated_types.ts
or autogenerated_types.d.ts
. The former fails the build, the latter passes the build. As I'm not JS expert, I don't know if this is obvious behaviour or not.
I hope this helps. For now this workaround does the trick for us, so no urgency from our side. If there is anything else I can provide, just let me know!
And also: thanks for your work on this project :saluting_face:
I am trying to generate typescript bindings with embind, but getting the following error:
Is it expected for consumers of these typescript definitions to implement this function, or is this implementation generated automatically by embind in the .js file? I can't find anything regarding this in the documentation, and there isn't anything else that I could find in this repository, or on google. The consumers of this library are expecting a modularized NPM package, so I don't think I can turn off
MODULARIZE
.Any help is greatly appreciated!
Version of emscripten/emsdk:
Failing command line in full:
em++ invocation: