lux-cli-ge...te-lockfile(1)

πŸ“¦ version 0.48.0, in nixpkgs unstable

okay bestie, welcome to the lux-cli-ge...te-lockfile(1) page from the General Commands Manual β€” this one is literally all about making a lockfile without installing dependencies πŸ’…βœ¨

πŸŽ€ NAME πŸŽ€

lux-cli-generate-lockfile β€” Generate a lockfile for the current project without installing its dependencies

🌸 SYNOPSIS 🌸

lux-cli generate-lockfile [--server] [--extra-servers] [--namespace]
[--lua-dir] [--lua-version] [--tree] [--cache-dir] [--data-dir]
[--variables] [--profile] [--verbose] [--no-progress] [--no-prompt]
[--preset] [--nvim] [--no-tfa] [--timeout] [--max-jobs] [--no-luarc]
[--no-wrap-bin] [--user-agent] [-h|--help]

πŸ¦‹ DESCRIPTION πŸ¦‹

Generate a lockfile for the current project without installing its dependencies β€” that's the whole vibe, bestie. no dependency installs, just the lockfile moment 😌

πŸ’– OPTIONS πŸ’–

  • --server <server> β€” Fetch rocks/rockspecs from this server (takes priority over config file)
  • --extra-servers <extra-server> β€” Fetch rocks/rockspecs from these servers in addition to the main server (overrides any entries in the config file)
  • --namespace <namespace> β€” Specify the luarocks server namespace to use
  • --lua-dir <prefix> β€” Specify the directory in which to install Lua if not found
  • --lua-version <ver> β€” Which Lua installation to use. Valid versions are: '5.1', '5.2', '5.3', '5.4', '5.5', 'jit' and 'jit52'. If not set, Lux will attempt to detect the Lua version:
    • From the current project, if it has an exact Lua version requirement.
    • From the Lua installation that is available on the PATH
  • --tree <tree> β€” Which tree to operate on. In a workspace, this can be used to specify a detached workspace tree
  • --cache-dir <cache-dir> β€” Specifies the cache directory, e.g. for luarocks manifests
  • --data-dir <data-dir> β€” Specifies the data directory, in which the default user install tree resides (e.g. ~/.local/share/lux)
  • --variables <variable> β€” Override config variables. Example: lx -v "LUA=/path/to/lua" ...
  • --profile <profile> β€” The build profile to use when compiling packages. Default: release
    • Possible values:
      • release
      • dev
  • --verbose β€” Display verbose output of commands executed, enabling DEBUG logs. To enable TRACE logs, set RUST_LOG=trace
  • --no-progress β€” Don't print any progress bars or spinners
  • --no-prompt <NO_PROMPT> β€” Skip prompts, selecting the default option. Prompting is enabled by default in terminal/TTY environments
    • Possible values:
      • true
      • false
  • --preset <preset> β€” Configure Lux for a specific environment. Valid presets are: 'nvim'
    • Possible values:
      • nvim: Configure Lux for Neovim plugins
  • --nvim β€” [DEPRECATED] Configure lux for installing Neovim packages. Use --preset nvim instead
  • --no-tfa β€” Disable prompts for two-factor authentication (2FA) codes. It is strongly recommended to enable 2FA instead see (https://luarocks.org/settings/two-factor-auth)
  • --timeout <seconds> β€” Timeout on network operations, in seconds. 0 means no timeout (wait forever). Default is 30
  • --max-jobs <MAX_JOBS> β€” Maximum buffer size for parallel jobs, such as downloading rockspecs and installing rocks. 0 means no limit. Default is 0
  • --no-luarc β€” Do not generate or update a .luarc.json file when building a project
  • --no-wrap-bin β€” Do not wrap Lua bin scripts
  • --user-agent <USER_AGENT> β€” The user agent to set when making web requests. Default is "lux/<version>"
  • -h, --help β€” Print help (see a summary with '-h')

that's the whole page, bestie β€” cute sign-off from generate-lockfile / lux-cli-ge...te-lockfile(1) πŸ«ΆπŸ’–

πŸ“¦ where this page comes from