Package Exports

@erillam/toolkit
@erillam/toolkit/dist/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@erillam/toolkit) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

toolkit-ng

CLI and Ink TUI for managing ECEF and WMS Docker stacks.

Requirements

Node.js 20+

Install

If you publish this package without a scope:

npm install -g toolkit-ng

If you publish it under a user or organization scope, replace the package name accordingly:

npm install -g @your-scope/toolkit-ng

Usage

Run the command from the parent directory that should act as the toolkit instance root.

toolkit --help
toolkit --print-instance-root
toolkit env ecef
toolkit install ecef
toolkit start ecef
toolkit stop ecef
toolkit pull ecef
toolkit status ecef
toolkit logs ecef app --follow

Without --action and without --non-interactive, the command opens the Ink TUI.

Development

From the repository:

npm install
npm run build
npm start -- --help

Publish

Review the package and publish it manually:

npm login
npm run release:check
npm publish

If you change the package name to a scoped name such as @your-scope/toolkit-ng, publish it as public:

npm publish --access public

The current checkout does not include a test/ directory, so the publish check focuses on build, CLI smoke validation and package contents.