Deno build?

[unicomp21]

No description provided.

[timostamm]

Do you know what is required to support Deno?

[unicomp21]

Does this help?

https://www.brunnerliv.io/articles/create-your-first-module-with-deno

[timostamm]

No. Have you actually tried running protobuf-ts with Deno?

What failed specifically, and how do you propose to solve it? If Deno requires special code paths, how do we ensure they continue to function as the code base moves along?

[unicomp21]

As an aside, the nats client support for Deno, might be a good template.

https://github.com/nats-io/nats.js/search?l=Markdown&q=deno

[unicomp21]

If Deno requires special code paths, how do we ensure they continue to function as the code base moves along?
Tests?

[timostamm]

Tests?

Would you like to contribute them?

[unicomp21]

Maybe, looks like the codegen will need to change for both cases. Thinking it over.

[timostamm]

Please reopen if there are any news. For a start, we'd need to know what exactly fails to run with Deno.

[QuantumGhost]

I'm trying to use protobuf-ts with Deno.

I have tried to import @protobuf-ts/runtime directly in Deno with esm.sh. However, since the import statements in generated code have no .ts extension and Deno not allowing import without filename extension, I cannot import the generated code in Deno.

Example

What's expected:

The generated import statements have .ts extension, for example:

import { Hat } from "./service-twirp-example.ts";
import { Size } from "./service-twirp-example.ts";

I think #233 may help this.