aboutsummaryrefslogtreecommitdiff
path: root/site/posts/2018-08-01-verifying-npm-ci-reproducibility.org
diff options
context:
space:
mode:
authorEuAndreh <eu@euandre.org>2020-01-25 15:33:37 -0300
committerEuAndreh <eu@euandre.org>2020-01-25 15:33:37 -0300
commitf3e264cf0dadd6436bc9df62560f1a17850b3721 (patch)
tree24449afcca72af2c6f665d47924dfc4ec860ab46 /site/posts/2018-08-01-verifying-npm-ci-reproducibility.org
parentUse feed.xml as the canonical file, leave atom.xml for those trying to discov... (diff)
downloadeuandre.org-f3e264cf0dadd6436bc9df62560f1a17850b3721.tar.gz
euandre.org-f3e264cf0dadd6436bc9df62560f1a17850b3721.tar.xz
Use <code> tags in titles
Diffstat (limited to '')
-rw-r--r--site/posts/2018-08-01-verifying-npm-ci-reproducibility.org2
1 files changed, 1 insertions, 1 deletions
diff --git a/site/posts/2018-08-01-verifying-npm-ci-reproducibility.org b/site/posts/2018-08-01-verifying-npm-ci-reproducibility.org
index da3947d..7d19632 100644
--- a/site/posts/2018-08-01-verifying-npm-ci-reproducibility.org
+++ b/site/posts/2018-08-01-verifying-npm-ci-reproducibility.org
@@ -1,5 +1,5 @@
---
-title: Verifying npm ci reproducibility
+title: Verifying <code>npm ci</code> reproducibility
date: 2018-08-01
---
When [[https://blog.npmjs.org/post/161081169345/v500][npm@5]] came bringing [[https://docs.npmjs.com/files/package-locks][package-locks]] with it, I was confused about the benefits it provided, since running =npm install= more than once could resolve all the dependencies again and yield yet another fresh =package-lock.json= file. The message saying "you should add this file to version control" left me hesitant on what to do[fn:npm-install].