icore 1.0.0 → 1.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +2 -2
- package/readme.md +17 -1
package/package.json
CHANGED
package/readme.md
CHANGED
|
@@ -1,5 +1,10 @@
|
|
|
1
1
|
# icore
|
|
2
2
|
|
|
3
|
+
[](https://www.npmjs.com/package/icore)
|
|
4
|
+
[](https://www.npmjs.com/package/icore)
|
|
5
|
+
[](https://www.npmjs.com/package/icore)
|
|
6
|
+
[](LICENSE)
|
|
7
|
+
|
|
3
8
|
Declarative command line interface mechanics for Node.js.
|
|
4
9
|
|
|
5
10
|
`icore` helps describe CLI commands with small option schemas and keeps command
|
|
@@ -16,6 +21,17 @@ It does not try to model your business domain. API calls, request building,
|
|
|
16
21
|
response mapping, and output formatting should stay in the application that uses
|
|
17
22
|
`icore`.
|
|
18
23
|
|
|
24
|
+
## Table of Contents
|
|
25
|
+
|
|
26
|
+
- [Installation](#installation)
|
|
27
|
+
- [Requirements](#requirements)
|
|
28
|
+
- [Basic Usage](#basic-usage)
|
|
29
|
+
- [Design Goals](#design-goals)
|
|
30
|
+
- [What icore Handles](#what-icore-handles)
|
|
31
|
+
- [What icore Does Not Handle](#what-icore-does-not-handle)
|
|
32
|
+
- [Option Schemas](#option-schemas)
|
|
33
|
+
- [API](#api)
|
|
34
|
+
|
|
19
35
|
## Installation
|
|
20
36
|
|
|
21
37
|
```sh
|
|
@@ -24,7 +40,7 @@ npm install icore
|
|
|
24
40
|
|
|
25
41
|
## Requirements
|
|
26
42
|
|
|
27
|
-
- Node.js `>=
|
|
43
|
+
- Node.js `>=16.9.0`
|
|
28
44
|
- TypeScript is supported through bundled declaration files.
|
|
29
45
|
|
|
30
46
|
## Basic Usage
|