From a3b933a1ecd2a5675d45d031454d57c4d11ae9e1 Mon Sep 17 00:00:00 2001 From: Landon Reed Date: Fri, 7 Jun 2019 09:38:43 -0400 Subject: [PATCH] fix(README): fix wording; also trigger version bump after dep bumps Automated ependency bumps for security in #264, #265, and #266 will not trigger a semver release. I'm using this wording tweak in README to handle this. --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 465c2f1..a5a54b7 100644 --- a/README.md +++ b/README.md @@ -25,7 +25,7 @@ ## Node -We pin mastarm to a specific version of node due to inconsistencies across installation and building when using multiple versions. *Node 8 is now required to run mastarm*. +We pin mastarm to a specific version of node due to inconsistencies across installation and building when using multiple versions. *Node 8 is now required to run mastarm*. ## Install @@ -240,7 +240,8 @@ also pass in an arbitrary number of paths to directories or files to lint. `lint-messages` is somewhat opinionated about how messages should be used in code. They should be imported from a local module called `messages`, and referred to using dot notation. It will work regardless -of whether you import the top-level messages object or named children; the following all work: +of whether you import the top-level messages object or named children. The following import strategies +all work: import messages from '../utils/messages' import msgs from './messages'