@deepnote/cli 0.1.0
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/LICENSE +201 -0
- package/README.md +387 -0
- package/dist/bin.cjs +7 -0
- package/dist/bin.d.cts +1 -0
- package/dist/bin.d.ts +1 -0
- package/dist/bin.js +8 -0
- package/dist/cli-BDKrMj8W.js +5350 -0
- package/dist/cli-DwaGOOLX.cjs +5452 -0
- package/dist/index.cjs +12 -0
- package/dist/index.d.cts +113 -0
- package/dist/index.d.ts +113 -0
- package/dist/index.js +3 -0
- package/package.json +68 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [2025] [Deepnote Inc]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,387 @@
|
|
|
1
|
+
# @deepnote/cli
|
|
2
|
+
|
|
3
|
+
Command-line interface for running Deepnote projects locally and on Deepnote Cloud.
|
|
4
|
+
|
|
5
|
+
> **Note:** This project is under active development and is not ready for production use. Expect breaking changes.
|
|
6
|
+
|
|
7
|
+
## Installation
|
|
8
|
+
|
|
9
|
+
```bash
|
|
10
|
+
npm install -g @deepnote/cli
|
|
11
|
+
# or
|
|
12
|
+
pnpm add -g @deepnote/cli
|
|
13
|
+
# or
|
|
14
|
+
yarn global add @deepnote/cli
|
|
15
|
+
```
|
|
16
|
+
|
|
17
|
+
## Quick Start
|
|
18
|
+
|
|
19
|
+
```bash
|
|
20
|
+
# Show help
|
|
21
|
+
deepnote --help
|
|
22
|
+
|
|
23
|
+
# Show version
|
|
24
|
+
deepnote --version
|
|
25
|
+
|
|
26
|
+
# Inspect a .deepnote file
|
|
27
|
+
deepnote inspect path/to/file.deepnote
|
|
28
|
+
|
|
29
|
+
# Inspect with JSON output (for scripting)
|
|
30
|
+
deepnote inspect path/to/file.deepnote --output json
|
|
31
|
+
|
|
32
|
+
# Inspect with TOON output (for LLMs, 30-60% fewer tokens)
|
|
33
|
+
deepnote inspect path/to/file.deepnote --output toon
|
|
34
|
+
|
|
35
|
+
# Validate a .deepnote file
|
|
36
|
+
deepnote validate path/to/file.deepnote
|
|
37
|
+
|
|
38
|
+
# Run a project/notebook file (.deepnote, .ipynb, .py, .qmd)
|
|
39
|
+
deepnote run path/to/file.deepnote
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
## Commands
|
|
43
|
+
|
|
44
|
+
### `inspect [path]`
|
|
45
|
+
|
|
46
|
+
Inspect and display metadata from a `.deepnote` file.
|
|
47
|
+
Path is optional: when omitted, the CLI discovers the first `.deepnote` file in the current directory.
|
|
48
|
+
|
|
49
|
+
```bash
|
|
50
|
+
deepnote inspect my-project.deepnote
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
**Output includes:**
|
|
54
|
+
|
|
55
|
+
- File path and project name
|
|
56
|
+
- Project ID and file format version
|
|
57
|
+
- Creation, modification, and export timestamps
|
|
58
|
+
- Number of notebooks and blocks
|
|
59
|
+
- List of notebooks with their block counts
|
|
60
|
+
|
|
61
|
+
**Options:**
|
|
62
|
+
|
|
63
|
+
| Option | Description | Default |
|
|
64
|
+
| -------------------- | --------------------------------------- | ------- |
|
|
65
|
+
| `-o, --output <fmt>` | Output format: `json`, `toon`, or `llm` | text |
|
|
66
|
+
|
|
67
|
+
**Examples:**
|
|
68
|
+
|
|
69
|
+
```bash
|
|
70
|
+
# Basic inspection
|
|
71
|
+
deepnote inspect my-project.deepnote
|
|
72
|
+
|
|
73
|
+
# Inspect first .deepnote file in current directory
|
|
74
|
+
deepnote inspect
|
|
75
|
+
|
|
76
|
+
# JSON output for scripting
|
|
77
|
+
deepnote inspect my-project.deepnote --output json
|
|
78
|
+
|
|
79
|
+
# TOON output for LLM consumption (30-60% fewer tokens)
|
|
80
|
+
deepnote inspect my-project.deepnote --output toon
|
|
81
|
+
|
|
82
|
+
# Use with jq to extract specific fields
|
|
83
|
+
deepnote inspect my-project.deepnote --output json | jq '.project.name'
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
### `run [path]`
|
|
87
|
+
|
|
88
|
+
Run a project/notebook file locally. Supported formats: `.deepnote`, `.ipynb`, `.py`, `.qmd`.
|
|
89
|
+
Path is optional: when omitted, the CLI discovers the first `.deepnote` file in the current directory.
|
|
90
|
+
|
|
91
|
+
```bash
|
|
92
|
+
deepnote run my-project.deepnote
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
**Options:**
|
|
96
|
+
|
|
97
|
+
| Option | Description | Default |
|
|
98
|
+
| ----------------------- | --------------------------------------------------------- | -------------- |
|
|
99
|
+
| `--python <path>` | Path to Python interpreter or virtual environment | auto-detected |
|
|
100
|
+
| `--cwd <path>` | Working directory for execution | file directory |
|
|
101
|
+
| `--notebook <name>` | Run only the specified notebook | all notebooks |
|
|
102
|
+
| `--block <id>` | Run only the specified block | all blocks |
|
|
103
|
+
| `-i, --input <key=val>` | Set input variable value (can be repeated) | |
|
|
104
|
+
| `--list-inputs` | List input variables without running | `false` |
|
|
105
|
+
| `-o, --output <fmt>` | Output format: `json`, `toon`, or `llm` | text |
|
|
106
|
+
| `--dry-run` | Show execution plan without running | `false` |
|
|
107
|
+
| `--top` | Display resource usage (CPU/memory) during execution | `false` |
|
|
108
|
+
| `--profile` | Show per-block timing and memory summary | `false` |
|
|
109
|
+
| `--open` | Open project in Deepnote Cloud after successful execution | `false` |
|
|
110
|
+
| `--context` | Include analysis context in machine-readable output | `false` |
|
|
111
|
+
|
|
112
|
+
**Examples:**
|
|
113
|
+
|
|
114
|
+
```bash
|
|
115
|
+
# Run all notebooks
|
|
116
|
+
deepnote run my-project.deepnote
|
|
117
|
+
|
|
118
|
+
# Run a Jupyter notebook directly (auto-converted)
|
|
119
|
+
deepnote run notebook.ipynb
|
|
120
|
+
|
|
121
|
+
# Run with a specific Python virtual environment
|
|
122
|
+
deepnote run my-project.deepnote --python path/to/venv
|
|
123
|
+
|
|
124
|
+
# Run only a specific notebook
|
|
125
|
+
deepnote run my-project.deepnote --notebook "Data Analysis"
|
|
126
|
+
|
|
127
|
+
# Output results as JSON for CI/CD pipelines
|
|
128
|
+
deepnote run my-project.deepnote --output json
|
|
129
|
+
|
|
130
|
+
# Output results as TOON for LLM consumption
|
|
131
|
+
deepnote run my-project.deepnote --output toon
|
|
132
|
+
```
|
|
133
|
+
|
|
134
|
+
### `validate <path>`
|
|
135
|
+
|
|
136
|
+
Validate a `.deepnote` file against the schema.
|
|
137
|
+
|
|
138
|
+
```bash
|
|
139
|
+
deepnote validate my-project.deepnote
|
|
140
|
+
```
|
|
141
|
+
|
|
142
|
+
**Options:**
|
|
143
|
+
|
|
144
|
+
| Option | Description | Default |
|
|
145
|
+
| -------------------- | ------------------------------ | ------- |
|
|
146
|
+
| `-o, --output <fmt>` | Output format: `json` or `llm` | text |
|
|
147
|
+
|
|
148
|
+
**Examples:**
|
|
149
|
+
|
|
150
|
+
```bash
|
|
151
|
+
# Validate a file
|
|
152
|
+
deepnote validate my-project.deepnote
|
|
153
|
+
|
|
154
|
+
# JSON output for CI/CD pipelines
|
|
155
|
+
deepnote validate my-project.deepnote --output json
|
|
156
|
+
```
|
|
157
|
+
|
|
158
|
+
### `completion <shell>`
|
|
159
|
+
|
|
160
|
+
Generate shell completion scripts for tab completion.
|
|
161
|
+
|
|
162
|
+
**Supported shells:** `bash`, `zsh`, `fish`
|
|
163
|
+
|
|
164
|
+
**Installation:**
|
|
165
|
+
|
|
166
|
+
```bash
|
|
167
|
+
# Bash (add to ~/.bashrc or ~/.bash_profile)
|
|
168
|
+
deepnote completion bash >> ~/.bashrc
|
|
169
|
+
source ~/.bashrc
|
|
170
|
+
|
|
171
|
+
# Zsh (add to ~/.zshrc)
|
|
172
|
+
deepnote completion zsh >> ~/.zshrc
|
|
173
|
+
source ~/.zshrc
|
|
174
|
+
|
|
175
|
+
# Fish (save to completions directory)
|
|
176
|
+
deepnote completion fish > ~/.config/fish/completions/deepnote.fish
|
|
177
|
+
```
|
|
178
|
+
|
|
179
|
+
## Global Options
|
|
180
|
+
|
|
181
|
+
These options work with all commands:
|
|
182
|
+
|
|
183
|
+
| Option | Description |
|
|
184
|
+
| --------------- | -------------------------------------------------- |
|
|
185
|
+
| `-h, --help` | Display help information |
|
|
186
|
+
| `-v, --version` | Display the CLI version |
|
|
187
|
+
| `--no-color` | Disable colored output |
|
|
188
|
+
| `--debug` | Show debug information for troubleshooting |
|
|
189
|
+
| `-q, --quiet` | Suppress non-essential output (errors still shown) |
|
|
190
|
+
|
|
191
|
+
## Environment Variables
|
|
192
|
+
|
|
193
|
+
| Variable | Description |
|
|
194
|
+
| ------------- | ------------------------------------------ |
|
|
195
|
+
| `NO_COLOR` | Set to any value to disable colored output |
|
|
196
|
+
| `FORCE_COLOR` | Set to `1` to force colors, `0` to disable |
|
|
197
|
+
|
|
198
|
+
The CLI follows the [NO_COLOR](https://no-color.org/) and [FORCE_COLOR](https://force-color.org/) standards.
|
|
199
|
+
|
|
200
|
+
## Exit Codes
|
|
201
|
+
|
|
202
|
+
The CLI uses standard exit codes for scripting:
|
|
203
|
+
|
|
204
|
+
| Code | Name | Description |
|
|
205
|
+
| ---- | ------------- | --------------------------------------------- |
|
|
206
|
+
| `0` | Success | Command completed successfully |
|
|
207
|
+
| `1` | Error | General error (runtime failures) |
|
|
208
|
+
| `2` | Invalid Usage | Invalid arguments, file not found, wrong type |
|
|
209
|
+
|
|
210
|
+
**Example usage in scripts:**
|
|
211
|
+
|
|
212
|
+
```bash
|
|
213
|
+
#!/bin/bash
|
|
214
|
+
if deepnote inspect project.deepnote --output json > /dev/null 2>&1; then
|
|
215
|
+
echo "Valid .deepnote file"
|
|
216
|
+
else
|
|
217
|
+
exit_code=$?
|
|
218
|
+
if [ $exit_code -eq 2 ]; then
|
|
219
|
+
echo "Invalid file or arguments"
|
|
220
|
+
else
|
|
221
|
+
echo "Unexpected error"
|
|
222
|
+
fi
|
|
223
|
+
fi
|
|
224
|
+
```
|
|
225
|
+
|
|
226
|
+
## Output Formats
|
|
227
|
+
|
|
228
|
+
The CLI supports output formats via the `-o, --output` option:
|
|
229
|
+
|
|
230
|
+
| Format | Description |
|
|
231
|
+
| ------ | --------------------------------------------------------------------------------------- |
|
|
232
|
+
| `json` | Standard JSON format for scripting and CI/CD pipelines |
|
|
233
|
+
| `toon` | [TOON format](https://toonformat.dev/) - LLM-optimized, 30-60% fewer tokens |
|
|
234
|
+
| `llm` | Alias to the best LLM format for each command (`toon` when available, otherwise `json`) |
|
|
235
|
+
|
|
236
|
+
## JSON Output Schema
|
|
237
|
+
|
|
238
|
+
### `inspect --output json`
|
|
239
|
+
|
|
240
|
+
```typescript
|
|
241
|
+
interface InspectOutput {
|
|
242
|
+
success: true;
|
|
243
|
+
path: string;
|
|
244
|
+
project: {
|
|
245
|
+
name: string;
|
|
246
|
+
id: string;
|
|
247
|
+
};
|
|
248
|
+
version: string;
|
|
249
|
+
metadata: {
|
|
250
|
+
createdAt: string;
|
|
251
|
+
modifiedAt: string | null;
|
|
252
|
+
exportedAt: string | null;
|
|
253
|
+
};
|
|
254
|
+
statistics: {
|
|
255
|
+
notebookCount: number;
|
|
256
|
+
totalBlocks: number;
|
|
257
|
+
};
|
|
258
|
+
notebooks: Array<{
|
|
259
|
+
name: string;
|
|
260
|
+
blockCount: number;
|
|
261
|
+
isModule: boolean;
|
|
262
|
+
}>;
|
|
263
|
+
}
|
|
264
|
+
|
|
265
|
+
// On error:
|
|
266
|
+
interface InspectError {
|
|
267
|
+
success: false;
|
|
268
|
+
error: string;
|
|
269
|
+
}
|
|
270
|
+
```
|
|
271
|
+
|
|
272
|
+
### `run --output json`
|
|
273
|
+
|
|
274
|
+
```typescript
|
|
275
|
+
interface RunOutput {
|
|
276
|
+
success: boolean;
|
|
277
|
+
path: string;
|
|
278
|
+
executedBlocks: number;
|
|
279
|
+
totalBlocks: number;
|
|
280
|
+
failedBlocks: number;
|
|
281
|
+
totalDurationMs: number;
|
|
282
|
+
blocks: Array<{
|
|
283
|
+
id: string;
|
|
284
|
+
type: string;
|
|
285
|
+
label: string;
|
|
286
|
+
success: boolean;
|
|
287
|
+
durationMs: number;
|
|
288
|
+
outputs: Array<{
|
|
289
|
+
output_type: "stream" | "execute_result" | "display_data" | "error";
|
|
290
|
+
// For stream outputs:
|
|
291
|
+
name?: "stdout" | "stderr";
|
|
292
|
+
text?: string;
|
|
293
|
+
// For execute_result/display_data:
|
|
294
|
+
data?: Record<string, unknown>;
|
|
295
|
+
// For error outputs:
|
|
296
|
+
ename?: string;
|
|
297
|
+
evalue?: string;
|
|
298
|
+
traceback?: string[];
|
|
299
|
+
}>;
|
|
300
|
+
error?: string;
|
|
301
|
+
}>;
|
|
302
|
+
}
|
|
303
|
+
|
|
304
|
+
// On error before execution starts:
|
|
305
|
+
interface RunError {
|
|
306
|
+
success: false;
|
|
307
|
+
error: string;
|
|
308
|
+
}
|
|
309
|
+
```
|
|
310
|
+
|
|
311
|
+
### `validate --output json`
|
|
312
|
+
|
|
313
|
+
```typescript
|
|
314
|
+
// When validation runs (file found and readable):
|
|
315
|
+
interface ValidationResult {
|
|
316
|
+
success: true;
|
|
317
|
+
path: string;
|
|
318
|
+
valid: boolean;
|
|
319
|
+
issues: Array<{
|
|
320
|
+
path: string; // JSON path to the invalid field (e.g., "notebooks.0.blocks.1")
|
|
321
|
+
message: string;
|
|
322
|
+
code: string; // Zod error code (e.g., "invalid_type", "unrecognized_keys")
|
|
323
|
+
}>;
|
|
324
|
+
}
|
|
325
|
+
|
|
326
|
+
// On error (file not found, resolution error, or runtime failure):
|
|
327
|
+
interface ValidationError {
|
|
328
|
+
success: false;
|
|
329
|
+
error: string;
|
|
330
|
+
}
|
|
331
|
+
```
|
|
332
|
+
|
|
333
|
+
The `success` field indicates whether the command completed:
|
|
334
|
+
|
|
335
|
+
- `success: true` - validation ran, check `valid` for the result
|
|
336
|
+
- `success: false` - operational error (file not found, etc.)
|
|
337
|
+
|
|
338
|
+
## Programmatic Usage
|
|
339
|
+
|
|
340
|
+
The CLI can also be used programmatically:
|
|
341
|
+
|
|
342
|
+
```typescript
|
|
343
|
+
import { createProgram, run, ExitCode } from "@deepnote/cli";
|
|
344
|
+
|
|
345
|
+
// Run with custom arguments
|
|
346
|
+
run(["node", "deepnote", "inspect", "project.deepnote"]);
|
|
347
|
+
|
|
348
|
+
// Or create and configure the program manually
|
|
349
|
+
const program = createProgram();
|
|
350
|
+
program.parse([
|
|
351
|
+
"node",
|
|
352
|
+
"deepnote",
|
|
353
|
+
"inspect",
|
|
354
|
+
"project.deepnote",
|
|
355
|
+
"--output",
|
|
356
|
+
"json",
|
|
357
|
+
]);
|
|
358
|
+
```
|
|
359
|
+
|
|
360
|
+
## Error Messages
|
|
361
|
+
|
|
362
|
+
The CLI provides helpful error messages with suggestions:
|
|
363
|
+
|
|
364
|
+
```bash
|
|
365
|
+
$ deepnote inspect missing-file.deepnote
|
|
366
|
+
# Error: File not found: /path/to/missing-file.deepnote
|
|
367
|
+
#
|
|
368
|
+
# Did you mean?
|
|
369
|
+
# - my-project.deepnote
|
|
370
|
+
# - another-project.deepnote
|
|
371
|
+
|
|
372
|
+
$ deepnote inspect notebook.ipynb
|
|
373
|
+
# Error: Unsupported file type: .ipynb
|
|
374
|
+
#
|
|
375
|
+
# Jupyter notebooks (.ipynb) are not directly supported.
|
|
376
|
+
# Use the @deepnote/convert package to convert to .deepnote format.
|
|
377
|
+
```
|
|
378
|
+
|
|
379
|
+
## Related Packages
|
|
380
|
+
|
|
381
|
+
- [`@deepnote/blocks`](../blocks) - Core package for working with Deepnote blocks
|
|
382
|
+
- [`@deepnote/convert`](../convert) - Convert between Jupyter and Deepnote formats
|
|
383
|
+
- [`@deepnote/runtime-core`](../runtime-core) - Runtime engine for executing notebooks
|
|
384
|
+
|
|
385
|
+
## License
|
|
386
|
+
|
|
387
|
+
Apache-2.0
|
package/dist/bin.cjs
ADDED
package/dist/bin.d.cts
ADDED
|
@@ -0,0 +1 @@
|
|
|
1
|
+
export { };
|
package/dist/bin.d.ts
ADDED
|
@@ -0,0 +1 @@
|
|
|
1
|
+
export { };
|