Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prune dependency tree #485

Open
1 of 3 tasks
crsh opened this issue Oct 15, 2021 · 1 comment
Open
1 of 3 tasks

Prune dependency tree #485

crsh opened this issue Oct 15, 2021 · 1 comment

Comments

@crsh
Copy link
Owner

crsh commented Oct 15, 2021

Currently, papaja has some pretty heavy (indirect) dependecies, which we could strive to remove. Here are some ideas:

  • gsl keeps giving users and our CI a hard time during installation. We rely on it indirectly through MBESS as a suggest. This should be solved shortyl, as MBESS has moved gsl to suggests.
  • stringr imports stringi, which takes a long time to install. The following packages we import use stringr:
    • knitr: The package uses stringr quite a bit, but there is an open PR to remove stringr over the medium term.
    • rmarkdown: There is only one call to stringr, which can probably be easily removed.
    • broom: There are several uses of stringr, but they should, in principle, be easy to remove.
  • broom: Has a heavy tidyverse dependency tree. We use it in some apa_print()-methods, but there we could switch to our alternative internal workflow (i.e. canonize() etc.) or use/support the output of a different package, such as parameters. Arguments for broom are the large number of supported models and it's widespread use, which makes it penatrable for independent contributors.
@mariusbarth
Copy link
Collaborator

With the newest version of arm (1.12-2), we do not depend on Hmisc and its imports, anymore 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants