From 4219784701d2b19d447a2a39720b657963085ca3 Mon Sep 17 00:00:00 2001 From: patricklafrance Date: Mon, 15 Apr 2024 11:48:27 -0400 Subject: [PATCH] docs: updated a troubleshoot issue --- docs/getting-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/getting-started.md b/docs/getting-started.md index 71d07f5..a02d693 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -214,7 +214,7 @@ To test your new Chromatic pipeline, follow these steps: ### Troubleshoot issues -If you encounter `pnpm-lock.yaml [file] (not found)` when executing the Chromatic pipeline, ensure that the pipeline point to the exact location of your project `package-lock.yaml` file. For example, if your `package-lock.yaml` is nested under a `/frontend` nested path, update `key: '"pnpm" | "$(Agent.OS)" | pnpm-lock.yaml'` for `key: '"pnpm" | "$(Agent.OS)" | $(System.DefaultWorkingDirectory)/frontend/pnpm-lock.yaml'`. +If you encounter `pnpm-lock.yaml [file] (not found)` when executing the Chromatic pipeline, ensure that the pipeline point to the exact location of your project `package-lock.yaml` file. For example, if your `package-lock.yaml` is nested under a `/frontend`, update `key: '"pnpm" | "$(Agent.OS)" | pnpm-lock.yaml'` for `key: '"pnpm" | "$(Agent.OS)" | $(System.DefaultWorkingDirectory)/frontend/pnpm-lock.yaml'`. If you encounter any other issues with the Chromatic pipeline, follow these steps: