Repository navigation
duobrain v0.1.5
Note: v0.1.5 was not published to npm: a copy installed from its npm package would not have been able to run
update. npm releases start at v0.1.6. Installing v0.1.5 from Git works.
duobrain v0.1.5
duobrain is now on npm. The first person adds it to a project with one command, without cloning the
duobrain repository first.
Changed
- Install with
npx. In the product repository, runnpx duobrain@0.1.5 install. It vendors the same
runtime files into.duobrain/and pinsv0.1.5inVENDOR.json, exactly like an install from a Git
download. Nothing is installed globally. Installing from a Git download still works. - Updates are unchanged.
updatein a vendored copy keeps installing from the Git release tags, so a
copy installed from npm and one installed from Git update the same way. The partner still only pulls. - The npm package contains only what
installvendors:bin,src,guides,skills,package.json,
LICENSEandREADME.md. - The README and Getting started guide drop the "local alpha" label.
Upgrading
Nothing to do for existing projects: node .duobrain/bin/duobrain.js update moves a vendored copy to
v0.1.5 as before.
Verification
npm run release:check now checks that package.json is publishable and that its files match the
runtime files install copies. The package was packed with npm pack and installed into a fresh
product repository with npm exec, then init, status --brief and update --check ran from the
vendored copy.