* using log directory ‘/srv/hornik/tmp/CRAN_pretest/lavinteract.Rcheck’ * using R Under development (unstable) (2025-10-28 r88973) * using platform: x86_64-pc-linux-gnu * R was compiled by Debian clang version 19.1.7 (7) Debian flang-new version 19.1.7 (7) * running under: Debian GNU/Linux forky/sid * using session charset: UTF-8 * checking for file ‘lavinteract/DESCRIPTION’ ... OK * checking extension type ... Package * this is package ‘lavinteract’ version ‘0.2.1’ * package encoding: UTF-8 * checking CRAN incoming feasibility ... [3s/5s] NOTE Maintainer: ‘Giuseppe Corbelli ’ New submission Possibly misspelled words in DESCRIPTION: Rosseel (12:285) The Title field should be in title case. Current version is: ‘Post-estimation Utilities for 'lavaan' Fitted Models’ In title case that is: ‘Post-Estimation Utilities for 'lavaan' Fitted Models’ * checking package namespace information ... OK * checking package dependencies ... OK * checking if this is a source package ... OK * checking if there is a namespace ... OK * checking for executable files ... OK * checking for hidden files and directories ... OK * checking for portable file names ... OK * checking for sufficient/correct file permissions ... OK * checking serialization versions ... OK * checking whether package ‘lavinteract’ can be installed ... [3s/3s] OK * checking package directory ... OK * checking for future file timestamps ... OK * checking DESCRIPTION meta-information ... OK * checking top-level files ... OK * checking for left-over files ... OK * checking index information ... OK * checking package subdirectories ... OK * checking code files for non-ASCII characters ... WARNING Found the following file with non-ASCII characters: R/lav_vif.R Portable packages must use only ASCII characters in their R code and NAMESPACE directives, except perhaps in comments. Use \uxxxx escapes for other characters. Function ‘tools::showNonASCIIfile’ can help in finding non-ASCII characters in files. * checking R files for syntax errors ... OK * checking whether the package can be loaded ... [1s/1s] OK * checking whether the package can be loaded with stated dependencies ... [1s/1s] OK * checking whether the package can be unloaded cleanly ... [1s/1s] OK * checking whether the namespace can be loaded with stated dependencies ... [1s/1s] OK * checking whether the namespace can be unloaded cleanly ... [1s/1s] OK * checking loading without being on the library search path ... [1s/1s] OK * checking whether startup messages can be suppressed ... [1s/1s] OK * checking use of S3 registration ... OK * checking dependencies in R code ... OK * checking S3 generic/method consistency ... OK * checking replacement functions ... OK * checking foreign function calls ... OK * checking R code for possible problems ... [5s/5s] OK * checking Rd files ... [0s/0s] OK * checking Rd metadata ... OK * checking Rd line widths ... OK * checking Rd cross-references ... OK * checking for missing documentation entries ... OK * checking for code/documentation mismatches ... WARNING Codoc mismatches from Rd file 'lav_vif.Rd': lav_slopes Code: function(fit, outcome, pred, modx, interaction, data = NULL, modx.values = NULL, modx.labels = NULL, pred.range = NULL, conf.level = 0.95, x.label = NULL, y.label = NULL, legend.title = NULL, colors = NULL, line.size = 0.8, alpha = 0.2, table = TRUE, digits = 2, modx_n_unique_cutoff = 4L, return_data = FALSE) Docs: function(fit, data = NULL, quiet = TRUE) Argument names in code not in docs: outcome pred modx interaction modx.values modx.labels pred.range conf.level x.label y.label legend.title colors line.size alpha table digits modx_n_unique_cutoff return_data Argument names in docs not in code: quiet Mismatches in argument names: Position: 2 Code: outcome Docs: data Position: 3 Code: pred Docs: quiet * checking Rd \usage sections ... WARNING Undocumented arguments in Rd file 'lav_slopes.Rd' ‘x’ ‘...’ ‘object’ Undocumented arguments in Rd file 'lav_vif.Rd' ‘x’ ‘digits’ ‘cutoff’ ‘...’ ‘object’ Objects in \usage without \alias in Rd file 'lav_vif.Rd': ‘lav_slopes’ Functions with \usage entries need to have the appropriate \alias entries, and all their arguments documented. The \usage entries must correspond to syntactically valid R code. See chapter ‘Writing R documentation files’ in the ‘Writing R Extensions’ manual. * checking Rd contents ... OK * checking for unstated dependencies in examples ... OK * checking examples ... [2s/2s] OK * checking PDF version of manual ... [3s/3s] OK * checking HTML version of manual ... [0s/0s] OK * checking for non-standard things in the check directory ... OK * checking for detritus in the temp directory ... OK * DONE Status: 3 WARNINGs, 1 NOTE