1171

Is the following the right way to create a directory if it doesn't exist?

It should have full permission for the script and readable by others.

var dir = __dirname + '/upload';
if (!path.existsSync(dir)) {
    fs.mkdirSync(dir, 0744);
}
3

25 Answers 25

2157

For individual dirs:

var fs = require('fs');
var dir = './tmp';

if (!fs.existsSync(dir)){
    fs.mkdirSync(dir);
}

Or, for nested dirs:

var fs = require('fs');
var dir = './tmp/but/then/nested';

if (!fs.existsSync(dir)){
    fs.mkdirSync(dir, { recursive: true });
}
10
  • 44
    If you're performing this operation on app boot or initialization, then its fine to block execution as you'd do the same thing if you were to do it async. If you're making a directory as a recurring operation then its bad practice but probably won't cause any performance issue, but its a bad habbit none-the-less. Only use for booting your app or otherwise one time operations.
    – tsturzl
    Aug 14, 2015 at 0:53
  • 28
    existsSync() isn't deprecated, exists() is though - nodejs.org/api/fs.html#fs_fs_existssync_path Oct 18, 2016 at 11:04
  • 2
    using *Sync methods is usually a no-no: don't want to block the event loop
    – Max Heiber
    Feb 13, 2017 at 21:23
  • 33
    Using sync methods it's fine for local scripts and such, obviously not a good idea for a server.
    – Pier
    Sep 3, 2017 at 19:58
  • 3
    What if a file exists with the same name? The code will continue as if there was a directory and probably throw an error later, when it tries writing to files in it. The answer by @josh3736 is much more complete and totally underrated.
    – Benni
    Jan 15, 2019 at 7:59
243

No, for multiple reasons.

  1. The path module does not have an exists/existsSync method. It is in the fs module. (Perhaps you just made a typo in your question?)

  2. The documentation explicitly discourage you from using exists.

    fs.exists() is an anachronism and exists only for historical reasons. There should almost never be a reason to use it in your own code.

    In particular, checking if a file exists before opening it is an anti-pattern that leaves you vulnerable to race conditions: another process may remove the file between the calls to fs.exists() and fs.open(). Just open the file and handle the error when it's not there.

    Since we're talking about a directory rather than a file, this advice implies you should just unconditionally call mkdir and ignore EEXIST.

  3. In general, you should avoid the *Sync methods. They're blocking, which means absolutely nothing else in your program can happen while you go to the disk. This is a very expensive operation, and the time it takes breaks the core assumption of node's event loop.

    The *Sync methods are usually fine in single-purpose quick scripts (those that do one thing and then exit), but should almost never be used when you're writing a server: your server will be unable to respond to anyone for the entire duration of the I/O requests. If multiple client requests require I/O operations, your server will very quickly grind to a halt.


    The only time I'd consider using *Sync methods in a server application is in an operation that happens once (and only once), at startup. For example, require actually uses readFileSync to load modules.

    Even then, you still have to be careful because lots of synchronous I/O can unnecessarily slow down your server's startup time.


    Instead, you should use the asynchronous I/O methods.

So if we put together those pieces of advice, we get something like this:

function ensureExists(path, mask, cb) {
    if (typeof mask == 'function') { // Allow the `mask` parameter to be optional
        cb = mask;
        mask = 0o744;
    }
    fs.mkdir(path, mask, function(err) {
        if (err) {
            if (err.code == 'EEXIST') cb(null); // Ignore the error if the folder already exists
            else cb(err); // Something else went wrong
        } else cb(null); // Successfully created folder
    });
}

And we can use it like this:

ensureExists(__dirname + '/upload', 0o744, function(err) {
    if (err) // Handle folder creation error
    else // We're all good
});

Of course, this doesn't account for edge cases like

  • What happens if the folder gets deleted while your program is running? (assuming you only check that it exists once during startup)
  • What happens if the folder already exists, but with the wrong permissions?
6
114

The mkdir method has the ability to recursively create any directories in a path that don't exist, and ignore the ones that do.

From the Node.js v10/11 documentation:

// Creates /tmp/a/apple, regardless of whether `/tmp` and /tmp/a exist.
fs.mkdir('/tmp/a/apple', { recursive: true }, (err) => {
    if (err) throw err;
});

NOTE: You'll need to import the built-in fs module first.

Now here's a little more robust example that leverages native ECMAScript Modules (with flag enabled and .mjs extension), handles non-root paths, and accounts for full pathnames:

import fs from 'fs';
import path from 'path';

function createDirectories(pathname) {
   const __dirname = path.resolve();
   pathname = pathname.replace(/^\.*\/|\/?[^\/]+\.[a-z]+|\/$/g, ''); // Remove leading directory markers, and remove ending /file-name.extension
   fs.mkdir(path.resolve(__dirname, pathname), { recursive: true }, e => {
       if (e) {
           console.error(e);
       } else {
           console.log('Success');
       }
    });
}

You can use it like createDirectories('/components/widget/widget.js');.

And of course, you'd probably want to get more fancy by using promises with async/await to leverage file creation in a more readable synchronous-looking way when the directories are created; but, that's beyond the question's scope.

4
  • 4
    Why const __dirname = path.resolve(); and not use the built-in __dirname? Feb 24, 2019 at 4:35
  • 4
    @TamusJRoyce __dirname is not available in es modules. Also, path.resolve() is process.cwd(), not __dirname anyway. To get the correct __dirname: stackoverflow.com/a/62892482/8280247 Jun 1, 2021 at 16:22
  • @ErikCampobadal good detail. yes. I was asking because it did not seem correct. es modules weren't widely used when this comment was posted. And although this question is about node.js. Your answer also compatible with deno - stackoverflow.com/a/61829368/458321 Jun 2, 2021 at 3:45
  • If I wanna create /var/log/a/b/c/, how to create them? Right now, it always threw error: Error: EACCES: permission denied, mkdir
    – Mystic
    Sep 13, 2021 at 2:49
51

With the fs-extra package you can do this with a one-liner:

const fs = require('fs-extra');

const dir = '/tmp/this/path/does/not/exist';
fs.ensureDirSync(dir);
3
  • 3
    Such an underrated answer! fs-extra has bacame a must have for me. I think it's an abberration to write 10+ lines juste to check if a folder exists...
    – TOPKAT
    May 6, 2020 at 10:07
  • 2
    While I would have loved for this to be simply baked in the core functionality, this is the best answer imo. Easy and clean Nov 28, 2020 at 11:18
  • 1
    I count 3 lines.
    – chovy
    Nov 11, 2022 at 23:51
45

I have found an npm module that works like a charm for this.

It simply does a recursive mkdir when needed, like a "mkdir -p ".

2
  • 6
    Why is that better/different from using the built-in mkdir with the { recursive: true } flag? Sep 18, 2021 at 9:29
  • 4
    I hope this is not sarcastic. Introducing a third-party library just to do something that is so basic and already implemented by a built-in module? This is the exact reason we are seeing the mess in the JS ecosystem.
    – Zhe
    Dec 24, 2021 at 15:47
43

The one line version:

// Or in TypeScript: import * as fs from 'fs';
const fs = require('fs');
!fs.existsSync(dir) && fs.mkdirSync(dir);
4
  • 13
    Alleged 1-liner not actually 1 line. Jun 7, 2020 at 13:24
  • 3
    @Hybridwebdev how about now ;) const fs = require('fs'); !fs.existsSync(dir) && fs.mkdirSync(dir);
    – Jack
    Jun 15, 2020 at 7:19
  • 8
    Mashing a bunch of code into 1 line doesn't make it a 1-liner. Jun 15, 2020 at 9:01
  • 11
    (fs => !fs.existsSync(dir) && fs.mkdirSync(dir))(require('fs')); Jun 22, 2020 at 3:22
31

solutions

  1. CommonJS
const fs = require('fs');
const path = require('path');

const dir = path.resolve(path.join(__dirname, 'upload');

if (!fs.existsSync(dir)) {
  fs.mkdirSync(dir);
}

// OR
if (!fs.existsSync(dir)) {
  fs.mkdirSync(dir, {
    mode: 0o744, // Not supported on Windows. Default: 0o777
  });
}

  1. ESM

update your package.json file config

{
  // declare using ECMAScript modules(ESM)
  "type": "module",
  //...
}
import fs from 'fs';
import path from 'path';
import { fileURLToPath } from 'url';

// create one custom `__dirname`, because it doesn't exist in es-module env.
// use `import.meta.url` to get the current module's URL, 
// then get the module's folder absolute path 
const __filename = fileURLToPath(import.meta.url);
const __dirname = path.dirname(__filename);
const dir = path.resolve(path.join(__dirname, 'upload');

if (!fs.existsSync(dir)) {
  fs.mkdirSync(dir);
}

// OR
if (!fs.existsSync(dir)) {
  fs.mkdirSync(dir, {
    mode: 0o744, // Not supported on Windows. Default: 0o777
  });
}

update 2022

import { existsSync } from 'node:fs';

refs

NodeJS Version: v18.2.0

https://nodejs.org/api/fs.html#fsexistssyncpath

https://nodejs.org/api/fs.html#fsmkdirsyncpath-options

https://nodejs.org/api/url.html#urlfileurltopathurl

https://github.com/nodejs/help/issues/2907#issuecomment-757446568

ESM: ECMAScript modules

https://nodejs.org/api/esm.html#introduction

3
  • shouldn't the update be made in the tsconfig if it's typescript related?
    – sagat
    Jun 17, 2022 at 13:32
  • @sagat This is not related to typescript.
    – Micka
    Jul 2, 2022 at 13:53
  • thx for clarifying. I was mixing up with the module attribute in compileOptions and package.json.
    – sagat
    Jul 3, 2022 at 14:02
22

You can just use mkdir and catch the error if the folder exists.
This is async (so best practice) and safe.

fs.mkdir('/path', err => { 
    if (err && err.code != 'EEXIST') throw 'up'
    .. safely do your stuff here  
    })

(Optionally add a second argument with the mode.)


Other thoughts:

  1. You could use then or await by using native promisify.

    const util = require('util'), fs = require('fs');
    const mkdir = util.promisify(fs.mkdir);
    var myFunc = () => { ..do something.. } 
    
    mkdir('/path')
        .then(myFunc)
        .catch(err => { if (err.code != 'EEXIST') throw err; myFunc() })
    
  2. You can make your own promise method, something like (untested):

    let mkdirAsync = (path, mode) => new Promise(
       (resolve, reject) => mkdir (path, mode, 
          err => (err && err.code !== 'EEXIST') ? reject(err) : resolve()
          )
       )
    
  3. For synchronous checking, you can use:

    fs.existsSync(path) || fs.mkdirSync(path)
    
  4. Or you can use a library, the two most popular being

    • mkdirp (just does folders)
    • fsextra (supersets fs, adds lots of useful stuff)
2
  • 1
    for the promising approach #1, you could re-arrange the catch. mkdir('/path').catch(err => { if (err.code != 'EEXIST') throw err;}).then(myFunc); May 23, 2018 at 22:00
  • And use !== instead of != Feb 28, 2019 at 22:08
19

One-line solution: Creates the directory if it does not exist

// import
const fs = require('fs')  // In JavaScript
import * as fs from "fs"  // in TypeScript
import fs from "fs"       // in Typescript

// Use
!fs.existsSync(`./assets/`) && fs.mkdirSync(`./assets/`, { recursive: true })
1
12

The best solution would be to use the npm module called node-fs-extra. It has a method called mkdir which creates the directory you mentioned. If you give a long directory path, it will create the parent folders automatically. The module is a superset of npm module fs, so you can use all the functions in fs also if you add this module.

10

The simple and modern answer for node v10 and above

As some answers pointed out, since node 10 you can use recursive:true for mkdir

What is not pointed out yet, is that when using recursive:true, mkdir does not return an error if the directory already existed.

So you can do:

fs.mkdir(dirPath,{recursive:true},(err) => {
    if(err) {
        //note: this does NOT get triggered if the directory already existed
        console.warn(err)
    }
    else{
        //directory now exists 
    }
})

Using promises

Also since node 10, you can get Promise versions of all fs functions by requiring from fs/promises

So putting those two things together, you get this simple solution:

import * as fs from 'fs/promises';

await fs.mkdir(dirPath, {recursive:true}).catch((err) => {
    //decide what you want to do if this failed
    console.error(err);
});

//directory now exists
1
  • the modern answer
    – stackers
    Feb 20, 2023 at 18:20
8

fs.exist() is deprecated. So I have used fs.stat() to check the directory status. If the directory does not exist, fs.stat() throws an error with a message like 'no such file or directory'. Then I have created a directory.

const fs = require('fs').promises;

const dir = './dir';
fs.stat(dir).catch(async (err) => {
  if (err.message.includes('no such file or directory')) {
    await fs.mkdir(dir);
  }
});
0
6
var dir = 'path/to/dir';
try {
  fs.mkdirSync(dir);
} catch(e) {
  if (e.code != 'EEXIST') throw e;
}
6
  • 4
    For Node.js v7.4.0, the documentation states that fs.exists() is deprecated, but fs.existsSync() is not. Could you add a link to a ressource saying that fs.existsSync() is depreciated?
    – francis
    Jan 30, 2017 at 21:00
  • 1
    Code-only answers are not very helpful to users who come to this question in the future. Please edit your answer to explain why your code solves the original problem
    – yivi
    Jan 30, 2017 at 21:42
  • 3
    @francis, hmm, I was looking at Node.js v5,nodejs.org/docs/latest-v5.x/api/fs.html#fs_fs_existssync_path Jan 31, 2017 at 16:19
  • 1
    Thanks! It seems that the function existed in version 0.12, got deprecated in version 4 and 5 and got restored in version 6 and 7... Kind of a zombi function...
    – francis
    Jan 31, 2017 at 17:54
  • 1
    Yes, apparently it is NOT deprecated now as of Apr 2018: nodejs.org/api/fs.html#fs_fs_existssync_path May 3, 2018 at 16:02
6

Use:

var filessystem = require('fs');
var dir = './path/subpath/';

if (!filessystem.existsSync(dir))
{
    filessystem.mkdirSync(dir);
}
else
{
    console.log("Directory already exist");
}
1
  • An explanation would be in order (but without "Edit:", "Update:", or similar - the answer should appear as if it was written today). May 4, 2021 at 16:57
5

For anyone else looking for this in 2023, you can now just do this with async/await - try/catch syntax:

import { stat, mkdir } from 'node:fs/promises';

const checkAndMakeDirectory = async (dir) => {
  try {
    await stat(dir);
  } catch (error) {
    if (error.code === "ENOENT") {
      try {
        await mkdir(dir);
      } catch (err) {
        console.error(err.message);
      }
    }
  }
}
4

With Node.js 10 + ES6:

import path from 'path';
import fs from 'fs';

(async () => {
  const dir = path.join(__dirname, 'upload');

  try {
    await fs.promises.mkdir(dir);
  } catch (error) {
    if (error.code === 'EEXIST') {
      // Something already exists, but is it a file or directory?
      const lstat = await fs.promises.lstat(dir);

      if (!lstat.isDirectory()) {
        throw error;
      }
    } else {
      throw error;
    }
  }
})();
3

I'd like to add a TypeScript Promise refactor of josh3736's answer.

It does the same thing and has the same edge cases. It just happens to use Promises, TypeScript typedefs, and works with "use strict".

// https://en.wikipedia.org/wiki/File_system_permissions#Numeric_notation
const allRWEPermissions = parseInt("0777", 8);

function ensureFilePathExists(path: string, mask: number = allRWEPermissions): Promise<void> {
    return new Promise<void>(
        function(resolve: (value?: void | PromiseLike<void>) => void,
            reject: (reason?: any) => void): void{
            mkdir(path, mask, function(err: NodeJS.ErrnoException): void {
                if (err) {
                    if (err.code === "EEXIST") {
                        resolve(null); // Ignore the error if the folder already exists
                    } else {
                        reject(err); // Something else went wrong
                    }
                } else {
                    resolve(null); // Successfully created folder
                }
            });
    });
}
3

From the documentation this is how you do it asynchronously (and recursively):

const fs = require('fs');
const fsPromises = fs.promises;

fsPromises.access(dir, fs.constants.F_OK)
   .catch(async() => {
                await fs.mkdir(dir, { recursive: true }, function(err) {
                    if (err) {
                      console.log(err)
                    }
                  })
    });
2

I had to create sub-directories if they didn't exist. I used this:

const path = require('path');
const fs = require('fs');

function ensureDirectoryExists(p) {
    //console.log(ensureDirectoryExists.name, {p});
    const d = path.dirname(p);
    if (d && d !== p) {
        ensureDirectoryExists(d);
    }
    if (!fs.existsSync(d)) {
        fs.mkdirSync(d);
    }
}
2

You can use the Node.js File System command fs.stat to check if a directory exists and fs.mkdir to create a directory with callback, or fs.mkdirSync to create a directory without callback, like this example:

// First require fs
const fs = require('fs');

// Create directory if not exist (function)
const createDir = (path) => {
    // Check if dir exist
    fs.stat(path, (err, stats) => {
        if (stats.isDirectory()) {
            // Do nothing
        } else {
            // If the given path is not a directory, create a directory
            fs.mkdirSync(path);
        }
    });
};
2

Just ignore EEXIST error:

mkdir(path, options).catch((err) => {
  if (err.code !== 'EEXIST') throw err
})

Perfect TypeScript modern solution:

import type {MakeDirectoryOptions, PathLike} from 'node:fs'
import {mkdir} from 'node:fs/promises'

export async function mkdirIfNotExists(path: PathLike, options?: MakeDirectoryOptions) {
  return mkdir(path, options).catch((err) => {
    if (err.code !== 'EEXIST') throw err
  })
}
1

Here is a little function to recursivlely create directories:

const createDir = (dir) => {
  // This will create a dir given a path such as './folder/subfolder' 
  const splitPath = dir.split('/');
  splitPath.reduce((path, subPath) => {
    let currentPath;
    if(subPath != '.'){
      currentPath = path + '/' + subPath;
      if (!fs.existsSync(currentPath)){
        fs.mkdirSync(currentPath);
      }
    }
    else{
      currentPath = subPath;
    }
    return currentPath
  }, '')
}
1

my solutions

  1. CommonJS

var fs = require("fs");

var dir = __dirname + '/upload';

// if (!fs.existsSync(dir)) {
//   fs.mkdirSync(dir);
// }

if (!fs.existsSync(dir)) {
  fs.mkdirSync(dir, {
    mode: 0o744,
  });
  // mode's default value is 0o744
}

  1. ESM

update package.json config

{
  //...
  "type": "module",
  //...
}
import fs from "fs";
import path from "path";

// create one custom `__dirname`, because it not exist in es-module env ⚠️
const __dirname = path.resolve();

const dir = __dirname + '/upload';

if (!fs.existsSync(dir)) {
  fs.mkdirSync(dir);
}

// OR
if (!fs.existsSync(dir)) {
  fs.mkdirSync(dir, {
    mode: 0o744,
  });
  // mode's default value is 0o744
}

refs

https://nodejs.org/api/fs.html#fsexistssyncpath

https://github.com/nodejs/help/issues/2907#issuecomment-671782092

0

Using async / await:

const mkdirP = async (directory) => {
  try {
    return await fs.mkdirAsync(directory);
  } catch (error) {
    if (error.code != 'EEXIST') {
      throw e;
    }
  }
};

You will need to promisify fs:

import nodeFs from 'fs';
import bluebird from 'bluebird';

const fs = bluebird.promisifyAll(nodeFs);
3
  • Where does promisifyAll() come from? Node.js? Some Node.js module? Something else? May 4, 2021 at 17:27
  • from the bluebird package
    – sdgfsdh
    May 4, 2021 at 17:50
  • Bluebird. May 4, 2021 at 18:32
0

A function to do this asynchronously (adjusted from a similar answer on SO that used sync functions, that I can't find now)

// ensure-directory.js
import { mkdir, access } from 'fs'

/**
 * directoryPath is a path to a directory (no trailing file!)
 */
export default async directoryPath => {
  directoryPath = directoryPath.replace(/\\/g, '/')

  // -- preparation to allow absolute paths as well
  let root = ''
  if (directoryPath[0] === '/') {
    root = '/'
    directoryPath = directoryPath.slice(1)
  } else if (directoryPath[1] === ':') {
    root = directoryPath.slice(0, 3) // c:\
    directoryPath = directoryPath.slice(3)
  }

  // -- create folders all the way down
  const folders = directoryPath.split('/')
  let folderPath = `${root}`
  for (const folder of folders) {
    folderPath = `${folderPath}${folder}/`

    const folderExists = await new Promise(resolve =>
      access(folderPath, error => {
        if (error) {
          resolve(false)
        }
        resolve(true)
      })
    )

    if (!folderExists) {
      await new Promise((resolve, reject) =>
        mkdir(folderPath, error => {
          if (error) {
            reject('Error creating folderPath')
          }
          resolve(folderPath)
        })
      )
    }
  }
}

Not the answer you're looking for? Browse other questions tagged or ask your own question.