fix(docker): node-jiti directory created in project root

[dargmuesli]

Environment

Docker
jiti 1.17.1
node 19.7.0-alpine

Reproduction

https://github.com/dargmuesli/nuxt-jiti

Describe the bug

1. docker build -t nuxt-jiti .
2. docker run --rm -it nuxt-jiti /bin/sh
3. ls -la
4. see that there is a node-jiti directory in the project's root

I'd expect the directory to be under /tmp.

Additional context

1. remove "postinstall": "nuxt prepare" from the package.json
2. append RUN pnpm nuxt prepare to the Dockerfile
3. run all steps above
4. see that node-jiti is created in /tmp, as expected

[pi0]

Hi thanks for reporting the issue and repro. I still didn't check repro but we do use os.tmpDir() it is strange not happening. Is tmpDir inside container also / ??

[dargmuesli]

I've checked that as well and looked into the code, I'm wondering the same. $TMPDIR is /tmp inside that container. Almost sounds like a NodeJS bug on alpine Linux maybe.

[dargmuesli]

Manually running path.join(os.tmpdir(), "node-jiti") works without a flaw.

/srv/app # node
Welcome to Node.js v19.7.0.
Type ".help" for more information.
> path.join(os.tmpdir(), "node-jiti")
'/tmp/node-jiti'

The difference lies in whether nuxt prepare is run in the postinstall hook or outside. How could that be? 🤔

[dargmuesli]

It seems this is a problem with pnpm only. I've updated the linked repo and created a ticket for pnpm:

• fix: postinstall hook sets $TMPDIR pnpm/pnpm#6140

As it looks like this is not a problem with this repo, I'm closing this issue.

[pi0]

Nice finding!! Is there a way we can hotfix maybe detecting TMPDIR===CWD()?

[dargmuesli]

We could detect that, but I don't know what we shall set it to then... 🤔

[pi0]

we can try to clear the env, use os.tmpdir() (and restore to keep pnpm working as it was)

[pi0]

[dargmuesli]

Good idea, that looks like a fair workaround! 🙌

[dargmuesli]

Reopening this to have it closed by the #123