@runsnative/recipe-header

The canonical RunsNative header recipe. This package carries source, not a runtime — nothing here is imported by your application. It is the upstream that @runsnative/recipe copies from and later diffs against.

npm i -D @runsnative/recipe @runsnative/recipe-header
npx recipe add header --dir src/chrome

That materializes four files and a recipe.json manifest recording, per file, whether it is synced or owned:

| File | Surface | Meaning | |---|---|---| | header.template.html | synced | Upstream owns it. recipe update 3-way-merges our changes in. | | header.wiring.js | synced | Same. | | header.config.js | owned | Yours. Edit freely — recipe check stays green. | | header.content.html | owned | Yours. Your nav items, your logo. |

Later:

npx recipe check header    # up-to-date / customized / update-available / locally-drifted
npx recipe update header   # merge upstream changes into synced files only
npx recipe eject header    # stop tracking; everything becomes owned

recipe check and recipe update read this package off your disk. They make no network call and need no RunsNative account — the tracked rung rides entirely on npm's own versioning and integrity hashes.

The header recipe arranges the <run-app-bar> primitive from @runsnative/components. A recipe is an arrangement you own; a component is a dependency you don't.

Version here is the recipe's semver, independent of the CLI's.

License: MIT.