@snyk/error-catalog-nodejs-public
Advanced tools
Comparing version 5.44.0 to 5.44.1
{ | ||
"name": "@snyk/error-catalog-nodejs-public", | ||
"version": "5.44.0", | ||
"version": "5.44.1", | ||
"type": "commonjs", | ||
@@ -5,0 +5,0 @@ "author": "snyk.io", |
@@ -60,3 +60,3 @@ /* | ||
* @description You can configure the CLI in different ways, for example via Environment Variables or configuration file. | ||
* If one parameter is configured multiple times, it is probably unintentional and might cause unexpected behaviour. | ||
* If one parameter is configured multiple times, it is probably unintentional and might cause unexpected behavior. | ||
* Review configured environment variables and ensure that everything is intentional. If so, you can skip this check by using --no-check. | ||
@@ -193,3 +193,3 @@ * | ||
* @name TooManyVulnerablePathsError | ||
* @description There are too many vulnerable paths to process the project. If your command supports it, consider the following:pruning repeated subdependencies (`snyk test -p`); excluding directories (`snyk test --all-projects --exclude=dir1,file2`); setting a detection depth (`snyk test --all-projects --detection-depth=3`). If the error still occurs, consider debugging or contact Snyk Support. | ||
* @description There are too many vulnerable paths to process the project. If your command supports it, consider the following:pruning repeated sub-dependencies (`snyk test -p`); excluding directories (`snyk test --all-projects --exclude=dir1,file2`); setting a detection depth (`snyk test --all-projects --detection-depth=3`). If the error still occurs, consider debugging or contact Snyk Support. | ||
* | ||
@@ -255,3 +255,3 @@ * See more: | ||
* - [https://docs.snyk.io/snyk-cli/commands/iac](https://docs.snyk.io/snyk-cli/commands/iac) | ||
* @summary IAC failue | ||
* @summary IAC failure | ||
* @category CLI | ||
@@ -258,0 +258,0 @@ * @param {string} details the specific details that causes this error |
@@ -95,3 +95,3 @@ /* | ||
* @description You can configure the CLI in different ways, for example via Environment Variables or configuration file. | ||
* If one parameter is configured multiple times, it is probably unintentional and might cause unexpected behaviour. | ||
* If one parameter is configured multiple times, it is probably unintentional and might cause unexpected behavior. | ||
* Review configured environment variables and ensure that everything is intentional. If so, you can skip this check by using --no-check. | ||
@@ -117,3 +117,3 @@ * | ||
description: `You can configure the CLI in different ways, for example via Environment Variables or configuration file. | ||
If one parameter is configured multiple times, it is probably unintentional and might cause unexpected behaviour. | ||
If one parameter is configured multiple times, it is probably unintentional and might cause unexpected behavior. | ||
Review configured environment variables and ensure that everything is intentional. If so, you can skip this check by using --no-check.`, | ||
@@ -335,3 +335,3 @@ errorCode: 'SNYK-CLI-0002', | ||
* @name TooManyVulnerablePathsError | ||
* @description There are too many vulnerable paths to process the project. If your command supports it, consider the following:pruning repeated subdependencies (`snyk test -p`); excluding directories (`snyk test --all-projects --exclude=dir1,file2`); setting a detection depth (`snyk test --all-projects --detection-depth=3`). If the error still occurs, consider debugging or contact Snyk Support. | ||
* @description There are too many vulnerable paths to process the project. If your command supports it, consider the following:pruning repeated sub-dependencies (`snyk test -p`); excluding directories (`snyk test --all-projects --exclude=dir1,file2`); setting a detection depth (`snyk test --all-projects --detection-depth=3`). If the error still occurs, consider debugging or contact Snyk Support. | ||
* | ||
@@ -358,3 +358,3 @@ * See more: | ||
status: 413, | ||
description: `There are too many vulnerable paths to process the project. If your command supports it, consider the following:pruning repeated subdependencies (\`snyk test -p\`); excluding directories (\`snyk test --all-projects --exclude=dir1,file2\`); setting a detection depth (\`snyk test --all-projects --detection-depth=3\`). If the error still occurs, consider debugging or contact Snyk Support.`, | ||
description: `There are too many vulnerable paths to process the project. If your command supports it, consider the following:pruning repeated sub-dependencies (\`snyk test -p\`); excluding directories (\`snyk test --all-projects --exclude=dir1,file2\`); setting a detection depth (\`snyk test --all-projects --detection-depth=3\`). If the error still occurs, consider debugging or contact Snyk Support.`, | ||
errorCode: 'SNYK-CLI-0009', | ||
@@ -444,3 +444,3 @@ level: 'error', | ||
* - [https://docs.snyk.io/snyk-cli/commands/iac](https://docs.snyk.io/snyk-cli/commands/iac) | ||
* @summary IAC failue | ||
* @summary IAC failure | ||
* @category CLI | ||
@@ -457,3 +457,3 @@ * @param {string} details the specific details that causes this error | ||
super({ | ||
title: 'IAC failue', | ||
title: 'IAC failure', | ||
type: 'https://docs.snyk.io/scan-with-snyk/error-catalog#snyk-cli-0012', | ||
@@ -460,0 +460,0 @@ status: 200, |
Sorry, the diff of this file is not supported yet
1003037