perf: setting up bun is unnecessary

[0x4007]

Resolves #50

I didn't test this because I'm not 100% of the syntax, but look how GitHub made their example for instant cold starts.

https://github.com/actions/typescript-action/blob/main/action.yml#L22-L24

[ubiquity-os-beta]

Caution

No labels are set.

[whilefoo]

https://github.com/ubiquity-whilefoo/daemon-pull-review/actions/runs/13975625604/job/39128551650
Looks like it works, the only downside is that we can't control the version - its v20 currently and current LTS version is v22

[0x4007]

https://github.com/ubiquity-whilefoo/daemon-pull-review/actions/runs/13975625604/job/39128551650 Looks like it works, the only downside is that we can't control the version - its v20 currently and current LTS version is v22

Instead of checking out the repo, we should consider a curl <raw git url>dist/index.js | node -e ?

[whilefoo]

Instead of checking out the repo, we should consider a curl <raw git url>dist/index.js | node -e ?

Usually there are multiple files in the dist folder and I don't think this way will make any faster than with git

[0x4007]

The point of ncc is to compile one file

And also to bundle all dependencies of course

[whilefoo]

I know but there are cases where it generates multiple files: https://github.com/ubiquity-os-marketplace/command-ask/tree/development/dist not sure if it actually uses them but there must be a reason
Also package.json is needed to run it as ESM

[0x4007]

Time for r&d

[gentlementlegen]

The reason for it to generate multiple file, is that it happens when external package also include external code that gets referenced within that external library. We could try using bun compiler once again since a lot of updates have been done, but that was actually what caused it to fail (external references).

Plus, you will have multiple files if you generate sourcemaps either way. And for ESM packages there will be a package.json telling node that it should run this as an ESM file as well.