Building R packages
Open
Nobody has claimed this yet.
book
devtools
r-package
usethis
- Dominant language
- No language data
- Stars
- 17
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Free books
- R packages (1st edition).
- R packages (WIP) (2nd edition -- with usethis).
- Chapter: The Whole Game (quick overview of the entire process).
Prepare your system:
install.packages(c("devtools", "roxygen2", "testthat", "knitr"))
Simplify your workflow:
usethis::use_devtools()
● Include this code in '.Rprofile' to make devtools available in all interactive sessions.
if (interactive()) {
suppressMessages(require(devtools))
}
[Copied to clipboard]
● Modify 'C:/Users/Mauro/Documents/.Rprofile'
● Restart R for changes to take effect
Videos
- Packages & Code (13' 15'').
- Documentation (15' 01'').
- Create a package website (1' 26'').
- Unit testing (15' 20'').
Thanks @vintented for motivating this post.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue body is a standalone collection of R package-building books, videos, and setup commands, but it names no repository file, documentation location, or specific change. Review the repository structure and existing resource entries first; the work is done only when the intended resource content and placement are defined and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100