dtoro
d4d99a7473
Problem: the hexagonal refactor churns the backend tree for nine more phases; the UI delivery stack (web/ SPA, cmd/desktop Wails wrapper, compose/web image) must move to its own repo first so doc/layout rewrites land once on a backend-only tree. Change: - New repo git.hubris.network/dtoro/oikos-web (v0.33.0): web/, desktop/ (updateURL repointed to oikos-web releases), compose/, own CI (web + desktop jobs), own deploy script (CI-green gate, TOCTOU guard, version-tagged images, prune-to-3), own webhook receiver on :9798 + launchd unit, own compose project publishing the same 8091:80. - Cutover executed on mac-mini in order: oikos stack's web service stopped+removed, oikos-web project brought up on 8091; outer Caddy untouched (targets the published port) — serving + Authentik flow + /wails 404 quirk verified post-cutover. - Stripped from oikos: web/, cmd/desktop/, compose/web/, desktop CI workflow, ci.yml web job, Makefile ui/desktop/desktop-package/install targets, the compose web service, oikos-web from deploy.sh's fallback prune list; wails + go-keyring dropped from go.mod, vendor synced. - README / CONTRIBUTING / AGENTS.md / .agents dev+operations docs now point at the new repo; mbse + mascot design docs carry a path note. Risk: production SPA serving depends on the new pipeline now; rollback is versioned-image re-up of the old web service from a pre-split checkout (port 8091). Desktop builds installed before the split still check dtoro/oikos releases — one manual reinstall, noted in the oikos-web release notes. Verification: go vet, make test (race), make generate-check, golangci (no new findings; baseline down 400→365); post-cutover curls — localhost:8091 200, /wails/runtime.js 404, outer Caddy 302 Authentik.
119 lines
3.0 KiB
Markdown
119 lines
3.0 KiB
Markdown
# Lilconfig ⚙️
|
|
[](https://badge.fury.io/js/lilconfig)
|
|
[](https://packagephobia.now.sh/result?p=lilconfig)
|
|
[](https://coveralls.io/github/antonk52/lilconfig)
|
|
|
|
A zero-dependency alternative to [cosmiconfig](https://www.npmjs.com/package/cosmiconfig) with the same API.
|
|
|
|
## Installation
|
|
|
|
```sh
|
|
npm install lilconfig
|
|
```
|
|
|
|
## Usage
|
|
|
|
```js
|
|
import {lilconfig, lilconfigSync} from 'lilconfig';
|
|
|
|
// all keys are optional
|
|
const options = {
|
|
stopDir: '/Users/you/some/dir',
|
|
searchPlaces: ['package.json', 'myapp.conf.js'],
|
|
ignoreEmptySearchPlaces: false
|
|
}
|
|
|
|
lilconfig(
|
|
'myapp',
|
|
options // optional
|
|
).search() // Promise<LilconfigResult>
|
|
|
|
lilconfigSync(
|
|
'myapp',
|
|
options // optional
|
|
).load(pathToConfig) // LilconfigResult
|
|
|
|
/**
|
|
* LilconfigResult
|
|
* {
|
|
* config: any; // your config
|
|
* filepath: string;
|
|
* }
|
|
*/
|
|
```
|
|
|
|
## Difference to `cosmiconfig`
|
|
Lilconfig does not intend to be 100% compatible with `cosmiconfig` but tries to mimic it where possible. The key differences are:
|
|
- **no** support for yaml files out of the box(`lilconfig` attempts to parse files with no extension as JSON instead of YAML). You can still add the support for YAML files by providing a loader, see an [example](#yaml-loader) below.
|
|
- **no** cache
|
|
|
|
### Options difference between the two.
|
|
|
|
|cosmiconfig option | lilconfig |
|
|
|------------------------|-----------|
|
|
|cache | ❌ |
|
|
|loaders | ✅ |
|
|
|ignoreEmptySearchPlaces | ✅ |
|
|
|packageProp | ✅ |
|
|
|searchPlaces | ✅ |
|
|
|stopDir | ✅ |
|
|
|transform | ✅ |
|
|
|
|
## Loaders examples
|
|
|
|
### Yaml loader
|
|
|
|
If you need the YAML support you can provide your own loader
|
|
|
|
```js
|
|
import {lilconfig} from 'lilconfig';
|
|
import yaml from 'yaml';
|
|
|
|
function loadYaml(filepath, content) {
|
|
return yaml.parse(content);
|
|
}
|
|
|
|
const options = {
|
|
loaders: {
|
|
'.yaml': loadYaml,
|
|
'.yml': loadYaml,
|
|
// loader for files with no extension
|
|
noExt: loadYaml
|
|
}
|
|
};
|
|
|
|
lilconfig('myapp', options)
|
|
.search()
|
|
.then(result => {
|
|
result // {config, filepath}
|
|
});
|
|
```
|
|
|
|
### ESM loader
|
|
|
|
Lilconfig v2 does not support ESM modules out of the box. However, you can support it with a custom a loader. Note that this will only work with the async `lilconfig` function and won't work with the sync `lilconfigSync`.
|
|
|
|
```js
|
|
import {lilconfig} from 'lilconfig';
|
|
|
|
const loadEsm = filepath => import(filepath);
|
|
|
|
lilconfig('myapp', {
|
|
loaders: {
|
|
'.js': loadEsm,
|
|
'.mjs': loadEsm,
|
|
}
|
|
})
|
|
.search()
|
|
.then(result => {
|
|
result // {config, filepath}
|
|
|
|
result.config.default // if config uses `export default`
|
|
});
|
|
```
|
|
|
|
## Version correlation
|
|
|
|
- lilconig v1 → cosmiconfig v6
|
|
- lilconig v2 → cosmiconfig v7
|