From fd57c62070826d9f0fe415c1d24ea9ccd30e63a5 Mon Sep 17 00:00:00 2001 From: Alon Dahari Date: Wed, 24 Jan 2024 14:42:44 +0000 Subject: [PATCH] Reorder first two paragraphs in part 2 This is so the right snippet shows up in the home page. --- _posts/2024-01-24-npm-1password-plugin-part-2.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2024-01-24-npm-1password-plugin-part-2.md b/_posts/2024-01-24-npm-1password-plugin-part-2.md index 5e1d51e..6e6f662 100644 --- a/_posts/2024-01-24-npm-1password-plugin-part-2.md +++ b/_posts/2024-01-24-npm-1password-plugin-part-2.md @@ -5,10 +5,10 @@ categories: - Open Source --- -_This is part 2 of a series of articles about adding an NPM shell plugin to 1Password. For more context, please check out [part 1]({% link _posts/2024-01-17-creating-npm-1password-plugin-part-1.md %})._ - So we have our basic implementation of the plugin, now it's time to make it better. This next step is pretty short and straight forward. We need to describe in the plugin which commands in our NPM CLI would require auth from 1password. +_This is part 2 of a series of articles about adding an NPM shell plugin to 1Password. For more context, please check out [part 1]({% link _posts/2024-01-17-creating-npm-1password-plugin-part-1.md %})._ + An example of when we don't need to authenticate is when the command includes the `--help` or `--version` flags. In our case, when running `npm uninstall` for example, we would never need to authenticate. The relevant file here is `npm.go`, which now looks like this: