Package Dependencies

Manage R package dependencies by correctly listing them under Imports, Suggests, Depends, LinkingTo, or Config/Needs/* sections in the DESCRIPTION file. This ensures robust code by defining exactly how packages interact with your code, tests, and vignettes.

Use Imports for packages strictly required for your R package to function, utilizing explicit namespace calls or @importFrom directives. Use Suggests for optional dependencies, implementing conditional checks and skip patterns in tests or vignettes when the dependency is absent.

Avoid circular dependencies in R packages by carefully structuring your DESCRIPTION file dependency types and utilizing explicit namespace usage. Properly segregating mandatory packages in Imports from optional ones in Suggests prevents recursive loading loops.

Use roxygen2 directives like @importFrom to explicitly import specific functions from another package's namespace into your R package. This approach keeps your namespace clean and avoids conflicts compared to importing an entire package.

Write conditional checks for suggested R packages using `requireNamespace()` to verify availability before execution. In tests, apply skip patterns if the dependency is missing, allowing your R package to gracefully handle optional functionality without failing.

Yes, R package dependency management supports explicit version specification in the DESCRIPTION file. Specifying minimum versions for dependencies like Imports or Suggests ensures your package uses compatible API features and prevents unexpected errors from older versions.