cabloy 5.1.87 → 5.1.89
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/CHANGELOG.md +12 -0
- package/README.md +27 -0
- package/cabloy-docs/fullstack/quickstart.md +27 -0
- package/cabloy-docs/pnpm-workspace.yaml +1 -0
- package/package.json +1 -1
- package/pnpm-workspace.yaml +1 -0
- package/vona/pnpm-workspace.yaml +1 -0
- package/zova/pnpm-workspace.yaml +1 -0
package/CHANGELOG.md
CHANGED
package/README.md
CHANGED
|
@@ -55,6 +55,33 @@ npm create cabloy
|
|
|
55
55
|
|
|
56
56
|
The generated project already includes `CLAUDE.md` and the `.claude/` workspace assets. This path creates a Cabloy Basic project baseline. Open this project in Claude Code and start coding immediately with project-specific guidance.
|
|
57
57
|
|
|
58
|
+
#### pnpm 11 supply-chain protection note
|
|
59
|
+
|
|
60
|
+
`pnpm` 11 enables the `minimumReleaseAge` supply-chain protection by default. Newly published packages may be blocked for a short time window before `pnpm` allows installation.
|
|
61
|
+
|
|
62
|
+
This matters for `npm create cabloy` because the command downloads Cabloy from npm and then automatically runs `npm run init`. If your environment blocks newly published packages during that flow, temporarily set `pnpm_config_minimum_release_age=0` for the current shell session and rerun the command.
|
|
63
|
+
|
|
64
|
+
**Windows PowerShell**
|
|
65
|
+
|
|
66
|
+
```powershell
|
|
67
|
+
$env:pnpm_config_minimum_release_age = "0"
|
|
68
|
+
npm create cabloy
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
**Windows Command Prompt**
|
|
72
|
+
|
|
73
|
+
```cmd
|
|
74
|
+
set pnpm_config_minimum_release_age=0 && npm create cabloy
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
**macOS / Linux**
|
|
78
|
+
|
|
79
|
+
```bash
|
|
80
|
+
pnpm_config_minimum_release_age=0 npm create cabloy
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
If you already created the project directory and only need to rerun initialization, use the same environment variable with `npm run init`.
|
|
84
|
+
|
|
58
85
|
For **Cabloy Start**, purchase access to the licensed private repository, clone `git@github.com:cabloy/cabloy-start.git`, and run `npm run init`. For the complete Start onboarding flow, read the [Cabloy Start](https://docs.cabloy.com/editions/cabloy-start) page.
|
|
59
86
|
|
|
60
87
|
Then continue with the framework docs:
|
|
@@ -26,6 +26,33 @@ npm create cabloy
|
|
|
26
26
|
|
|
27
27
|
The generated project already includes `CLAUDE.md` and the `.claude/` workspace assets. This path creates a Cabloy Basic project baseline. Open this project in Claude Code and start coding immediately with project-specific guidance.
|
|
28
28
|
|
|
29
|
+
### pnpm 11 supply-chain protection note
|
|
30
|
+
|
|
31
|
+
`pnpm` 11 enables the `minimumReleaseAge` supply-chain protection by default. Newly published packages may be blocked for a short time window before `pnpm` allows installation.
|
|
32
|
+
|
|
33
|
+
This matters for `npm create cabloy` because the command downloads Cabloy from npm and then automatically runs `npm run init`. If your environment blocks newly published packages during that flow, temporarily set `pnpm_config_minimum_release_age=0` for the current shell session and rerun the command.
|
|
34
|
+
|
|
35
|
+
#### Windows PowerShell
|
|
36
|
+
|
|
37
|
+
```powershell
|
|
38
|
+
$env:pnpm_config_minimum_release_age = "0"
|
|
39
|
+
npm create cabloy
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
#### Windows Command Prompt
|
|
43
|
+
|
|
44
|
+
```cmd
|
|
45
|
+
set pnpm_config_minimum_release_age=0 && npm create cabloy
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
#### macOS / Linux
|
|
49
|
+
|
|
50
|
+
```bash
|
|
51
|
+
pnpm_config_minimum_release_age=0 npm create cabloy
|
|
52
|
+
```
|
|
53
|
+
|
|
54
|
+
If you already created the project directory and only need to rerun initialization, use the same environment variable with `npm run init`.
|
|
55
|
+
|
|
29
56
|
## 3. Start the backend
|
|
30
57
|
|
|
31
58
|
```bash
|
package/package.json
CHANGED
package/pnpm-workspace.yaml
CHANGED
package/vona/pnpm-workspace.yaml
CHANGED