Derek Bailey

@Ryanmtate Are you still interesting in doing this?

Good news, this is progressing internally. We will have an official NuGet package at some point!

Thanks for the report. @bjornharrtell Can you take a look?

Sorry, I haven't use TS or flexbuffers myself, so I didn't investigate this. ``` // At this point serializedBuffer is Uint8Array(7) [50, 51, 52, 53, 4, 88, 1] ``` Shouldn't...

Yeah, i think have to add these as dependencies to some target so they don't get deleted.

@dg0yt Maintainer of upstream project here, but I wasn't responsible for vcpkg integration. What needs to be done here?

The npm package (4.2.1) is outdated or pointing to the 'classes' branch then, most definitions are still 'classes' in the npm package.

That will only matter if you have more than 256 Union members. See this known issues #6796

I'm trying to understand the issue here. Are you worried that the enum backing type is now a `unit8_t`?

So one important thing to consider is that build systems like bazel (and Blaze within Google) require that all generated files be known and explicitly stated in the build rules....