How do I load data from another package from within my package
来源： https://stackoverflow.com/questions/48715141/how-do-i-load-data-from-another-package-from-within-my-package
package-development
How do I load data from another package from within my package
来源： https://stackoverflow.com/questions/48715141/how-do-i-load-data-from-another-package-from-within-my-package
Package reverse dependency checks (especially on Windows)
问题 I would like to hear how folks do their reverse dependency checks on Windows these days. When using the "official", yet experimental function tools::check_packages_in_dir() as suggested by CRAN Repository Policy [1] on Windows, reverse dependencies are checked based on their sources, i.e., everything is to be compiled. This can take ages even for relatively few dependencies/suggested packages. Next to that, it is not very convenient as I hit a lot of missing packages in the process so that
Package reverse dependency checks (especially on Windows)
问题 I would like to hear how folks do their reverse dependency checks on Windows these days. When using the "official", yet experimental function tools::check_packages_in_dir() as suggested by CRAN Repository Policy [1] on Windows, reverse dependencies are checked based on their sources, i.e., everything is to be compiled. This can take ages even for relatively few dependencies/suggested packages. Next to that, it is not very convenient as I hit a lot of missing packages in the process so that
npm package development run executable
问题 I'm creating a module (foo) with an executable. I've used npm link to make sure the package can be tested locally. This module has a dependency (bar) with an executable. I want to access this executable inside my executable. mainProject | |- foo | |- bar // cli.js (foo/cli.js) import { spawnSync } from 'child_process'; async function main(argv: string[]) { const version = require('../package.json').version; commander .command('test') .action(async () => { const { stdout, stderr, error } =
Visualizing and keeping track of your package development state
问题 What is a good way of keeping track of the state of development and/or visualizing how all your R packages are linked to each other (and its "third-party" dependencies)? I usually try to apply a "divide and conquer" strategy which by now - 5 years down the road - lead to quite some amount of packages with a clear-cut functional scope. But I've reached a state where things have (perceivably) become so scattered that I can't wrap my head around all the dependencies and "where are the lego
Visualizing and keeping track of your package development state
问题 What is a good way of keeping track of the state of development and/or visualizing how all your R packages are linked to each other (and its "third-party" dependencies)? I usually try to apply a "divide and conquer" strategy which by now - 5 years down the road - lead to quite some amount of packages with a clear-cut functional scope. But I've reached a state where things have (perceivably) become so scattered that I can't wrap my head around all the dependencies and "where are the lego
How can I automatically add/update Depends/Imports/Suggests versions in DESCRIPTION?
问题 I like to keep my R packages up to date, and in developing my own package, I want to stick to @Hadley's advice: Generally, it’s always better to specify the version and to be conservative about which version to require. Unless you know otherwise, always require a version greater than or equal to the version you’re currently using. So, I'll need some of those here in DESCRIPTION : Imports: knitr (>= 1.13), rmarkdown (>= 1.0) Is there an existing tool to programmatically update the versions of
How to effectively deal with uncompressed saves during package check?
问题 In recent efforts to develop a package, I'm including datasets in the data/ folder of my package. In my specific case I have 5 datasets all of which are in data.table format (although the issues I describe below persist if I keep them as data.frame ). I've saved each one as individual .rda files and documented them appropriately. When I run check() from package devtools , I get the following warnings: checking data for ASCII and uncompressed saves ... WARNING Warning: large data file(s) saved
How to effectively deal with uncompressed saves during package check?
In recent efforts to develop a package, I'm including datasets in the data/ folder of my package. In my specific case I have 5 datasets all of which are in data.table format (although the issues I describe below persist if I keep them as data.frame ). I've saved each one as individual .rda files and documented them appropriately. When I run check() from package devtools , I get the following warnings: checking data for ASCII and uncompressed saves ... WARNING Warning: large data file(s) saved inefficiently: size ASCII compress data1.rda 129Kb TRUE gzip data2.rda 101Kb TRUE gzip data3.rda 1.6Mb