fix: Include not working with deno runtime

[stevefan1999-personal]

Related to cdk8s-team/cdk8s#2171 but with a consequence of a modern version of Node must be required. This is one of the few roadblocks left.

[stevefan1999-personal]

@iliapolo cc

[iliapolo]

@stevefan1999-personal can you please elaborate on how this is related to Deno support? Also, you mentioned:

modern version of Node must be required

Which one?

[stevefan1999-personal]

@stevefan1999-personal can you please elaborate on how this is related to Deno support? Also, you mentioned:

modern version of Node must be required

Which one?

Because Deno does not have a require function out of the box. And when you run that script you run with deno executable as well.

I don't remember starting from which Node you can use mjs as file extension running as ESM module exactly though.

[iliapolo]

ESM has been available as a stable feature since Node12 so we are good here.

See https://nodejs.org/docs/latest-v12.x/api/esm.html

Thanks!

[iliapolo]

@stevefan1999-personal there's a self-mutation failure:

diff --git a/.projen/tasks.json b/.projen/tasks.json
index 665e4a0..8fb9228 [10](https://github.com/cdk8s-team/cdk8s-core/actions/runs/10772681725/job/29870857444?pr=2704#step:8:11)0644
--- a/.projen/tasks.json
+++ b/.projen/tasks.json
@@ -494,4 +494,4 @@
     "PATH": "$(npx -c \"node --print process.env.PATH\")"
   },
   "//": "~~ Generated by projen. To modify, edit .projenrc.js and run \"npx projen\"."
-}
\ No newline at end of file
+}

It means some auto-generated files have not been fully committed. You need to run yarn build locally and push the resulting changes.

[iliapolo]

@stevefan1999-personal

This is one of the few roadblocks left.

What other roadblocks are you aware of?

[stevefan1999-personal]

@stevefan1999-personal

This is one of the few roadblocks left.

What other roadblocks are you aware of?

There is a problem with the type checker. While it is not fatal it is annoying and hard for debugging

[iliapolo]

@stevefan1999-personal

There is a problem with the type checker. While it is not fatal it is annoying and hard for debugging

Can you elaborate?

[iliapolo]

@stevefan1999-personal

You need to run yarn build locally and push the resulting changes.

Reminder ^

[github-actions]

This PR has not received a response in a while and will be closed soon. If you want to keep it open, please leave a comment below @mentioning a maintainer.

[pbar1]

Any chance of revisiting this? I've also just run into this using Deno. @iliapolo