aboutsummaryrefslogtreecommitdiff
path: root/_posts/2018-08-01-verifying-npm-ci-reproducibility.md
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--_posts/2018-08-01-verifying-npm-ci-reproducibility.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/_posts/2018-08-01-verifying-npm-ci-reproducibility.md b/_posts/2018-08-01-verifying-npm-ci-reproducibility.md
index 5f6954b..efb5fea 100644
--- a/_posts/2018-08-01-verifying-npm-ci-reproducibility.md
+++ b/_posts/2018-08-01-verifying-npm-ci-reproducibility.md
@@ -1,8 +1,9 @@
---
-title: Verifying \<code\>npm ci\</code\> reproducibility
+title: Verifying "npm ci" reproducibility
date: 2018-08-01
layout: post
---- When
+---
+When
[npm\@5](https://blog.npmjs.org/post/161081169345/v500) came bringing
[package-locks](https://docs.npmjs.com/files/package-locks) with it, I
was confused about the benefits it provided, since running `npm install`