drop2run 0.1.0 → 0.1.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/README.md
CHANGED
|
@@ -2,6 +2,15 @@
|
|
|
2
2
|
|
|
3
3
|
Publish a static site to [Drop2Run](https://dropto.run) from the command line.
|
|
4
4
|
|
|
5
|
+
```bash
|
|
6
|
+
npm i -g drop2run
|
|
7
|
+
drop2run login
|
|
8
|
+
drop2run deploy dist
|
|
9
|
+
```
|
|
10
|
+
|
|
11
|
+
Node 20 or newer. That is the whole of it: `login` opens a browser and stores a token, `deploy` prints the
|
|
12
|
+
URL. Full documentation at [dropto.run/docs/cli](https://dropto.run/docs/cli).
|
|
13
|
+
|
|
5
14
|
```
|
|
6
15
|
drop2run login [--device] Sign in and store a token
|
|
7
16
|
drop2run logout Remove the stored token
|
|
@@ -94,10 +103,25 @@ credential, and which of them has not used it since it was made. It prints prefi
|
|
|
94
103
|
`token revoke` is refused with a message rather than treated as `list` — somebody will type it, and
|
|
95
104
|
listing instead would read as having worked.
|
|
96
105
|
|
|
106
|
+
---
|
|
107
|
+
|
|
108
|
+
Everything below is for whoever maintains this package. It is here rather than in the monorepo's docs
|
|
109
|
+
because it is about this directory — but it is on the npm page too, so it says who it is for.
|
|
110
|
+
|
|
97
111
|
## Releasing
|
|
98
112
|
|
|
99
|
-
|
|
100
|
-
|
|
113
|
+
The current version is whatever `package.json` says; the first release with `login` in it was `0.1.0`,
|
|
114
|
+
published 02/09/2026. `0.0.0` is also on the registry and is not a release — it held the bare name
|
|
115
|
+
`drop2run` (brief §9.1) and predates `login` entirely, so nothing should ever be pinned to it.
|
|
116
|
+
|
|
117
|
+
Check a publish from outside rather than from its own output, because the failure worth ruling out is a
|
|
118
|
+
tarball with no `dist` — which the publish log looks perfectly happy about:
|
|
119
|
+
|
|
120
|
+
```
|
|
121
|
+
$ npx drop2run@<version> --version
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
Publishing is one command:
|
|
101
125
|
|
|
102
126
|
```bash
|
|
103
127
|
cd packages/cli && npm publish
|
|
@@ -121,7 +145,7 @@ The bundle itself works. `@drop2run/core` and `@drop2run/node` are resolved by b
|
|
|
121
145
|
installed, and `vite build` folds both into `dist/index.js`, so the tarball has no import pointing at
|
|
122
146
|
something npm cannot fetch.
|
|
123
147
|
|
|
124
|
-
## Running it from
|
|
148
|
+
## Running it from the monorepo
|
|
125
149
|
|
|
126
150
|
```bash
|
|
127
151
|
cd packages/cli && npm run build
|
package/dist/index.js
CHANGED
|
@@ -1191,7 +1191,7 @@ async function run(argv) {
|
|
|
1191
1191
|
const positional = argv.filter((argument) => !argument.startsWith("-"));
|
|
1192
1192
|
const [command, ...rest] = positional;
|
|
1193
1193
|
if (argv.includes("--version")) {
|
|
1194
|
-
const { version } = await import("./package-
|
|
1194
|
+
const { version } = await import("./package-BGfKrpb3.js").then(
|
|
1195
1195
|
(module) => module.default
|
|
1196
1196
|
);
|
|
1197
1197
|
return { text: version, json: { version }, code: 0 };
|