(aws-cdk): Information for Requesting Deno Support
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 267
- Avg merge
- 1d 25m
- Merged PRs (30d)
- 14
Description
### General Issue
Information for Requesting Deno Support
### The Question
I'd like to know what the proper procedures and steps are required to start the discussion around formal support for Deno (https://deno.land). Deno is an alternative to Node that supports TypeScript and ESM natively. While it's a close cousin, many of the mechanisms have significant differences, namely dependency management. Presently, to make use of AWS CDK for Deno apps, users must run Node along side Deno.
I'd like to propose Deno support for AWS CDK, as it's already authored in TypeScript for Node support, but I'm honestly not sure where to begin.
### CDK CLI Version
1.131.0
### Framework Version
_No response_
### Node.js Version
_No response_
### OS
_No response_
### Language
Typescript
### Language Version
_No response_
### Other information
_No response_
Contributor guide
Research direction
Start with the issue's 16-comment discussion and the jsii repository context; no source files, tests, or entry points are named. Clarify whether Deno support belongs in jsii and what compatibility work would be required. Done is a maintainer-approved support path or an explicit decision and next steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno, node.js, typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100