Developer docs

Trouble shooting

A quick reference log of issues and resolutions. See also Worktree and Workspace Setup Guide | Trouble shooting notes.


Issue

Cause

Recommended Solution

Linting error when importing from aliases that start with: ‘@@’ or '~'

Workspaces does not work well with Babel when it comes to recognizing un-standard paths.

Find the alias for the import in babel.config.json and use the original path.

yarn workspace <workspace-name> add <depency-name> command fails.

Yarn workspace documented bug.

In the root package.json file, in the engines field, make sure the yarn field is set to 1.19.1

When trying to import using the @department-of-veteran-affairs/platform-<app> format , Unable to resolve path to module ... eslintimport/no-unresolved, or unresolved path

If you have added a new file or child directory to platform, this is likely because you did not specify the path alias in babel.config.json

Check or add the path to babel.config.json. Example:
{...
"module-resolver", { ... "alias": { ... "@department-of-veterans-affairs/component-library/LoadingIndicator": "@department-of-veterans-affairs/react-components/LoadingIndicator",
...}
...}
...}


You may need to restart VS Code to see changes take effect.


Help and feedback