feat: global config file - e.g. `~/.config/marp/marprc`

[nikhilmaddirala]

• Problem: I need to create ./.marprc configuration for every project I am working on. But most of my projects have the same configuration, so I keep copying the same .marprc file to every new project I'm working on.
• Proposed Solution: Implement user level configs in a location like ~/.config/marp/marprc or ~/.marprc that are automatically sourced by marp; let the user level configs be overriden by project level configs in ./.marprc if needed.

[yhatt]

Hmm. Implicit personal configuration can lead to unintended troubleshooting. (Marp CLI v3.x and earlier had supported global configuration ~/.marprc, but this was unintentional: #643 (comment))

In practice, require()/import in a global JavaScript configuration file marp.config.js will be unintuitive behavior as indicating ESLint's RFC in below, and can lead complex implementation to fix that.

And considering (essentially) project-dependent configuration values as personal global settings tends to treat as "bad practice" in several projects, and I also agree about that.

References

• ESLint
  • https://github.com/eslint/rfcs/blob/main/designs/2019-deprecating-personal-config/README.md
  • Update: Personal Config Loads Global-Installed Packages eslint/rfcs#28

Workaround

alias marp='/path/to/marp -c ~/.marprc'