You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems unnecessary to create same wrappers as other languages use since deno is also TypeScript and only difference is some node functionality that is not supported. Denoify uses polyglots where it can, but also supports creating deno specific versions of files by using *.deno.ts files, but that would require libraries to write deno specific code.
Wondering a bit if its interesting to support deno and if denoify would be a good approach? It would have certain limits, but would make it possible to support deno if taking those limitations into account (not using unsupported functions) or using deno overrides.
guidanceQuestion that needs advice or information.needs-triageThis issue or PR still needs to be triaged.
1 participant
Converted from issue
This discussion was converted from issue #2967 on March 31, 2022 23:38.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
❓ Guidance
Affected Languages
TypeScript
orJavascript
Python
Java
C#
,F#
, ...)Go
General Information
The Question
I was playing around with supporting deno using denoify (https://github.com/garronej/denoify) and converted the constructs (https://github.com/2ttech/constructs/tree/deno_test/deno_lib), terraform cdktf (https://github.com/2ttech/terraform-cdk/tree/deno_test) and cdktf-provider-azurerm (https://github.com/2ttech/cdktf-provider-azurerm) just to see everything was working. Besides setting up some ports for libraries in package.json it required some minor changes to support non existing deno libraries. So far this was just done running denoify from command prompt, but it would be nice to be able to automatically create deno libraries.
It seems unnecessary to create same wrappers as other languages use since deno is also TypeScript and only difference is some node functionality that is not supported. Denoify uses polyglots where it can, but also supports creating deno specific versions of files by using *.deno.ts files, but that would require libraries to write deno specific code.
Wondering a bit if its interesting to support deno and if denoify would be a good approach? It would have certain limits, but would make it possible to support deno if taking those limitations into account (not using unsupported functions) or using deno overrides.
Beta Was this translation helpful? Give feedback.
All reactions