create-clivly 0.3.0-next.7 → 0.4.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/README.md +8 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -6,16 +6,23 @@ app. This is the `create-*` entry point for `clivly init`: it runs exactly what
|
|
|
6
6
|
runtime.
|
|
7
7
|
|
|
8
8
|
```bash
|
|
9
|
-
npm create clivly
|
|
9
|
+
npm create clivly
|
|
10
10
|
# or
|
|
11
11
|
npx create-clivly
|
|
12
12
|
# or
|
|
13
13
|
pnpm create clivly
|
|
14
14
|
```
|
|
15
15
|
|
|
16
|
+
Clivly's stable packages publish on npm's `latest` tag. Use `@next` only when
|
|
17
|
+
you are intentionally validating a prerelease build.
|
|
18
|
+
|
|
16
19
|
It writes your `clivly.config.ts`, scaffolds the CRM routes, extends your
|
|
17
20
|
Drizzle schema, and (unless `--no-login`) pairs this machine to your workspace.
|
|
18
21
|
|
|
22
|
+
If you run it from a workspace root, it looks for a supported Drizzle app in
|
|
23
|
+
that repo and scaffolds there. If it finds more than one, it stops and shows
|
|
24
|
+
you the candidate directories instead of guessing.
|
|
25
|
+
|
|
19
26
|
## Flags
|
|
20
27
|
|
|
21
28
|
These are forwarded straight to `clivly init`:
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "create-clivly",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.4.0",
|
|
4
4
|
"private": false,
|
|
5
5
|
"type": "module",
|
|
6
6
|
"description": "Scaffold Clivly into your app — the create-* entry point for `clivly init`.",
|
|
@@ -33,7 +33,7 @@
|
|
|
33
33
|
}
|
|
34
34
|
},
|
|
35
35
|
"dependencies": {
|
|
36
|
-
"clivly": "0.
|
|
36
|
+
"clivly": "0.4.0"
|
|
37
37
|
},
|
|
38
38
|
"author": "Joseph Amani",
|
|
39
39
|
"engines": {
|