fs.mkdir, fs.mkdtemp(Sync) return ENOENT for the documentation example (Windows, run from git bash)

Version: v8.4.0
Platform: Windows 10
Subsystem: git for Windows bash

The problem does not occur when node is started from a Windows shell - so it may be a git bash bug in the end?

Originally reported as flow-upgrade issue: facebook/flow#4647 (comment)

Code taken from https://nodejs.org/dist/latest-v8.x/docs/api/fs.html#fs_fs_mkdtemp_prefix_options_callback

fs.mkdtemp('/tmp/foo-', (err, folder) => {
  if (err) throw err;
  console.log(folder);
  // Prints: /tmp/foo-itXde2
});

When I run this from the node console started in the git for Windows bash I get

> fs.mkdtemp('/tmp/foo-', (err, folder) => {
...   if (err) throw err;
...   console.log(folder);
...   // Prints: /tmp/foo-itXde2
... });
undefined
> Error: ENOENT: no such file or directory, mkdtemp '/tmp/foo-XXXXXX'

/tmp exists and is accessible and writable, I can run mkdir /tmp/foo _from the bash command line.

The problem becomes visible in the full error message:

> { Error: ENOENT: no such file or directory, mkdir 'C:\tmp\FOO'
  errno: -4058,
  code: 'ENOENT',
  syscall: 'mkdir',
  path: 'C:\\tmp\\FOO' }

Highlight: path: 'C:\\tmp\\FOO'

Update, actually the path translation issue is not so clear, I only get the "C" drive absolute path from mkdir but mkdtemp shows the correct path (still shows the exact same behavior though, both the problem and the workaround):

$ node
> fs.mkdir('/tmp/FOO', err => console.error(err))
undefined
> { Error: ENOENT: no such file or directory, mkdir 'C:\tmp\FOO'
  errno: -4058,
  code: 'ENOENT',
  syscall: 'mkdir',
  path: 'C:\\tmp\\FOO' }

> fs.mkdtemp('/tmp/FOO', err => console.error(err))
undefined
> { Error: ENOENT: no such file or directory, mkdtemp '/tmp/FOOXXXXXX'
  errno: -4058,
  code: 'ENOENT',
  syscall: 'mkdtemp',
  path: '/tmp/FOOXXXXXX' }

By the way, if I create C:\tmp (outside node) all those commands work:

me@me-MAINPC MINGW64 ~/Projects/one (master)
$ mkdir /C/tmp

me@me-MAINPC MINGW64 ~/Projects/one (master)
$ node
> fs.mkdir('/tmp/FOO', err => console.error(err))
undefined
> null

> fs.mkdtemp('/tmp/FOO', err => console.error(err))
undefined
> null

/tmp/... will be resolved to C:\tmp\... on Windows. If C:\tmp is not present you will get ENOENT, just like with fs.mkdtemp('/nonexisting/...') on Linux.

You should probably use platform specific temp folder, something like:

const tempFolder = process.platform === 'win32' ? process.env['TEMP'] : '/tmp';
fs.mkdtemp(path.join(tempFolder, 'foo-'), ...);

@lll000111

@lll000111 do you still have issue with mkdtemp?

doc: make mkdtemp example work on Windows

Navigation Menu

Repository navigation

fs.mkdir, fs.mkdtemp(Sync) return ENOENT for the documentation example (Windows, run from git bash) #14960

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

fs.mkdir, fs.mkdtemp(Sync) return ENOENT for the documentation example (Windows, run from git bash) #14960

Description

Activity

lll000111 commented on Aug 21, 2017

bzoz commented on Aug 21, 2017

bzoz commented on Aug 24, 2017

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions