npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

atomic-write

v0.1.1

Published

Provides an atomic implementation of fs.writeFile

Downloads

844

Readme

Atomic Write

Provides atomic implementation of fs.writeFile by first writing to a temporary file and renaming to the final destination.

Caveats

This is only garenteeed to be atomic on local filesystems. And only when the temporary directory is on the same filesystem as the actual file to be written. And possibly only on some kernels.

Quickstart

var aWrite = require('atomic-write');

//writeFile has the same interface as fs.writeFile
aWrite.writeFile('/tmp/file', 'example data', function(err, result){
  if(err){
    return console.log(err);
  }
  
  console.log("File written");
});

Module API

  • writeFile(filename, data, options, callback) Atomically write a file.

  • Context() Constructor that creates a new atomic-write context where you can change the implementation of atomic-write's internal functions can be changed without effecting the global atomic-write context.

Internal functions

These functions can be re-implemented in new Contexts if atomic-writes defaults don't suite your task.

  • tempDirectory(filePath, cb) Yields the directory in which the temporary file will be created. By default this is the same directory as where the final file will be created. Calls the callback with an error if one occured, and the directory.

  • tempFilename(filePath, cb) Yields the basename of the temporary file that will be created. By default this is a unix style hidden file with an md5 sum of the the pathname and current time in milliseconds along with the real basename of the file. Calls the callback with an error if one occured, and the basename.

  • tempFilepath(filePath, cb) Yields the path to the temporary file that will be created. By default this is join of the result of tempDirectory and tempFilename.

warning In the default implemenation if tempFilename already exists tempFilePath will be called recursively with the same arguments until a unique filename is found. If your implemenation of tempFilename is purely functional your gonna have a bad time.