Question 1

How do I set up jsii for a new TypeScript library project?

Accepted Answer

Start by configuring your TypeScript project with jsii compiler flags and using the jsii-config tool for setup. Then, use jsii-pacmak to generate bindings, referencing the documentation website for detailed examples.

Question 2

What languages does jsii support right now?

Accepted Answer

jsii currently supports Python, Java, C#, and other .NET languages from a TypeScript source, as listed in the README. It focuses on these idiomatic bindings but does not easily extend to others like Go or Rust.

Question 3

jsii vs Protocol Buffers for cross-language libraries, which should I use?

Accepted Answer

jsii is better for generating idiomatic class-based libraries from TypeScript, offering native APIs in each language. Protocol Buffers are superior for defining service contracts and data serialization with broader language support and efficiency.

Question 4

How to handle debugging in jsii-generated code?

Accepted Answer

Debugging requires understanding the JavaScript bridge; use source maps and runtime logs from the jsii toolchain. Errors in TypeScript translate to native exceptions, but tracing issues can be more complex due to the layered architecture.

Question 5

Can jsii be used outside of AWS CDK projects?

Accepted Answer

Yes, jsii is a general-purpose framework for any polyglot library generation, not tied to AWS CDK. Its standalone toolchain allows use in various contexts, as evidenced by the open-source documentation.

Question 6

What are the performance costs of using jsii?

Accepted Answer

There is a performance overhead from the JavaScript bridge, which can impact latency-sensitive applications. However, for most library use cases like infrastructure tools, the trade-off is acceptable given maintenance benefits.

jsii

What is jsii?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions