René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Import-safe entrypoints when run from non-canonical path: doesn't run","articleBody":"**Description:**\n\n**NB:**This issue may only occur when running this action outside of GitHub actions infrastructure.\n\nWhen running this action with a non-canonical path, such as appears to be happening on my Forgejo setup (see details below), the \"import-safe\" entrypoints fail to run, printing instead:\n\n> `the script is loaded as a module, so skipping the execution`\n\nThe cause seems to be:\n1. my runner loads actions into `/var/run`\n2. `/var/run` is a symlink to `/run`\n3. NodeJS appears to put a canonical path (as in: all symlinks get resolved) into `import.meta.url`\n4. `process.argv[1] === fileURLToPath(import.meta.url)` thus evaluates to false\n\nIt'd be fantastic if there were a way to make `setup-java` work under these circumstances.\n\n**Details**\n\nForgejo version: 16.0.3\nForgejo runner version: 13\nImage used to run action: ghcr.io/catthehacker/ubuntu:runner-24.04\n\n**Task version:**\nv6\n\n**Platform:**\n- [x] Ubuntu\n- [ ] macOS\n- [ ] Windows\n\n**Runner type:**\n- [ ] Hosted\n- [x] Self-hosted\n\n**Repro steps:**  \nI do not have a simple way to reproduce this, but here's a `Dockerfile` to demonstrate that `import.meta.url` contains a canonicalized path:\n\n```dockerfile\nFROM alpine\n\nRUN apk --no-cache add nodejs\nRUN mkdir dir\nRUN ln -s dir symlink\nRUN echo 'console.log(`process.argv[1]: ${process.argv[1]}`); console.log(`import.meta.url: ${import.meta.url}`)' > dir/test.js\n\nCMD node dir/test.js; node symlink/test.js\n```\n\n**Expected behavior:**\nI expect the action to run normally.\n\n**Actual behavior:**\nThe action says it won't run because the \"script was loaded as a module\"","author":{"url":"https://github.com/otaconix","@type":"Person","name":"otaconix"},"datePublished":"2026-09-07T18:04:44Z","url":"https://github.com/actions/setup-java/issues/1264"}