r-package-development

Structure R package dependencies by using the Imports field for required packages and Suggests for optional ones. This approach ensures reliable package loading and avoids unnecessary dependency bloat for users.

Input validation in R package API design requires checking arguments at the appropriate functional level and returning actionable error messages. Consistent API patterns like `.by` and `{{ }}` ensure predictable, user-friendly function behavior.

Organize testthat tests by their specific purpose, such as validation or edge cases, and generate roxygen2 documentation stubs for all exported functions. This ensures comprehensive test coverage and consistent exported documentation.

An R package pre-release checklist should include running `devtools::check`, verifying testthat coverage, updating roxygen2 documentation, and confirming versioning. Finalizing these checks prevents common release pitfalls like hardcoded file paths.

Using `library()` inside R package code is an anti-pattern that modifies the global search path and causes fragile releases. Instead, list dependencies in the DESCRIPTION file and reference them using the `package::function()` syntax.

Choose base R over external dependencies when the required functionality is simple and stable, reducing the dependency footprint. Evaluate this during API design to keep your R package lightweight and easier to maintain.