Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: npm/cacache
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v15.0.0
Choose a base ref
...
head repository: npm/cacache
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v15.0.1
Choose a head ref
  • 2 commits
  • 4 files changed
  • 1 contributor

Commits on Apr 28, 2020

  1. Use move-file instead of move-file-concurrently

    Cacache only ever moves individual files, and move-file-concurrently
    does a lot more than that, and has a lot of very outdated deps.
    
    move-file does the same basic thing, but for a single file only, and
    without the additional deps that are better to remove.
    
    It does mean that, since copyFile is not an atomic operation, we can
    end up files getting corrupted in some extremely unlikely situations,
    but that will just be treated as a cache miss by most users anyhow.
    
    Fix #33
    isaacs committed Apr 28, 2020
    Configuration menu
    Copy the full SHA
    92b1251 View commit details
    Browse the repository at this point in the history
  2. 15.0.1

    isaacs committed Apr 28, 2020
    Configuration menu
    Copy the full SHA
    14567c3 View commit details
    Browse the repository at this point in the history
Loading