@babel/register write cache fail in node:alpine docker container

Bug Report

• I would like to work on a fix!

Current Behavior In node:alpine docker image. The folder node_modules create by root. And node server runs by ‘node’ user. So node_modules isn’t writeable.

cache.js not handle ENOENT error. It just throw out and crash node server.

/home/node/app/node_modules/@babel/register/lib/cache.js:80
        throw e;
        ^

Error: ENOENT: no such file or directory, mkdir '/home/node/app/node_modules/.cache/@babel/register'
    at Object.mkdirSync (fs.js:856:3)
    at module.exports.sync (/home/node/app/node_modules/make-dir/index.js:97:6)
    at save (/home/node/app/node_modules/@babel/register/lib/cache.js:61:23)
    at processTicksAndRejections (internal/process/task_queues.js:79:11) {
  errno: -2,
  syscall: 'mkdir',
  code: 'ENOENT',
  path: '/home/node/app/node_modules/.cache/@babel/register'
}

Input Code

• REPL or Repo link if applicable:

var your => (code) => here;

Expected behavior/code A clear and concise description of what you expected to happen (or code).

Babel Configuration (babel.config.js, .babelrc, package.json#babel, cli command, .eslintrc)

• Filename: babel.config.js

{
  "your": { "config": "here" }
}

Environment

• Babel version(s): v7.8.3
• Node/npm version: Node v13.8.0/npm 6.13.6
• OS: Alpine Linux
• Monorepo: no
• How you are using Babel: register

Possible Solution

Additional context/Screenshots Add any other context about the problem here. If applicable, add screenshots to help explain.

[JLHwung]

As a workaround, you can disable the register cache via BABEL_DISABLE_CACHE env

ENV BABEL_DISABLE_CACHE 1

If node_modules is not writable due to permission errors, it should throw EACCESS instead of ENOENT. Babel will ignore the EACCESS error and produce warnings only.

Per http://man7.org/linux/man-pages/man3/errno.3.html

ENOENT: No such file or directory (POSIX.1-2001). Typically, this error results when a specified path‐name does not exist, or one of the components in the directory prefix of a pathname does not exist, or the specified pathname is a dangling symbolic link.

In your case, maybe /home/node/app/node_modules is a dangling symbolic link mounted by Docker. @cncolder Can you share the reproducing Dockerfile?

[JLHwung]

@cncolder Thanks for the reproduction Dockerfile. I can confirm this issue can be reproduced and thus I have filed one to the make-dir repo: https://github.com/sindresorhus/make-dir/issues/25

make-dir is used in babel-register to create cache directory. Note that this issue does not affect Babel 8, where make-dir has been replaced by native recursive fs.mkdir supported on node>=10.12.

It seems that fs.mkdir will throws ENOENT on the following cases and make-dir aligns to its behaviour.

mkdir -m 0100 foo
node -e "require('fs').mkdirSync('foo/bar')"
# Error: EACCES

node -e "require('fs').mkdirSync('foo/bar', { recursive: true })"
# Error: ENOENT

mkdir foo/bar
# Error: Permission Denied

It has been fixed recently on Node.js: (issue: https://github.com/nodejs/node/issues/31481)

Before we dropped node.js <= 13 support, we should workaround this node bug.