From 1fb95e85a2e91d84927f7ccae4e1d6512f425dcc Mon Sep 17 00:00:00 2001 From: Jan Sauer <jan@jansauer.de> Date: Wed, 12 Dec 2018 06:43:01 +0100 Subject: [PATCH] docs: Fix documentation typo (#2943) --- docs/adding-a-package-manager.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/adding-a-package-manager.md b/docs/adding-a-package-manager.md index 1eeaedcb11..c9bac8643f 100644 --- a/docs/adding-a-package-manager.md +++ b/docs/adding-a-package-manager.md @@ -43,7 +43,7 @@ This function doesn't necessarily need to _understand_ the file or even syntax t As a general approach, we want to extract _all_ dependencies from each dependency file, even if they contain values we don't support. For any that have unsupported values that we cannot renovate, this `extractPackageFile` function should set a `skipReason` to a value that would be helpful to someone reading the logs. -Also, if a file is passed to `extractPackageFile` that is a "false match" (e.g. not an actual package file, or contains no dependencies) then this function can return `null` to have it ignored and removed from the list of package files. A common case for this is in Meteor, where its `package.js` file name is not unique and there many be many non-Meteor paojects using that filename. +Also, if a file is passed to `extractPackageFile` that is a "false match" (e.g. not an actual package file, or contains no dependencies) then this function can return `null` to have it ignored and removed from the list of package files. A common case for this is in Meteor, where its `package.js` file name is not unique and there many be many non-Meteor projects using that filename. ##### `extractAllPackageFiles(packageFiles)` (async, optional) -- GitLab