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 would be nice to get end-to-end support for them.
How would you implement this feature?
I'm currently running the Checkly CLI under Deno 2 and it works. Although the end-to-end experience isn't en point yet, since the CLI is not aware of the runtime.
So for some stuff you need to fiddle around a bit to get it running:
imports in Deno are using the full name incl. suffix my/file/name.ts which fails when transpiling this via TSC on the deploy stage
Type resolution not always works and requires "manual" imports
When transpiling code, the CLI falls back to TSC instead of the runtime
The text was updated successfully, but these errors were encountered:
What problem does this feature solve?
As a customer/user of the CLI, I'd like to use different JS runtimes other than
node
. There are currently two alternative JS runtimes on the rise:It would be nice to get end-to-end support for them.
How would you implement this feature?
I'm currently running the Checkly CLI under Deno 2 and it works. Although the end-to-end experience isn't en point yet, since the CLI is not aware of the runtime.
So for some stuff you need to fiddle around a bit to get it running:
my/file/name.ts
which fails when transpiling this via TSC on the deploy stageThe text was updated successfully, but these errors were encountered: