@webflow/webflow-cli 2.0.0 → 2.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/CHANGELOG.md +32 -0
- package/dist/index.js +113 -109
- package/dist/index.js.map +1 -1
- package/package.json +4 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,37 @@
|
|
|
1
1
|
# @webflow/webflow-cli
|
|
2
2
|
|
|
3
|
+
## 2.1.0
|
|
4
|
+
|
|
5
|
+
### Minor Changes
|
|
6
|
+
|
|
7
|
+
- 7815a63: Align `webflow cloud` with the "Apps" product naming.
|
|
8
|
+
|
|
9
|
+
- Add a `-n, --app-name` flag to `webflow cloud init` and `webflow cloud deploy`, and a `-a, --app-id` flag to `webflow cloud deploy`. The legacy `--project-name` (both commands) and `--project-id` (`deploy`) flags continue to work but are now deprecated and emit a warning. The `-p` short flag has been replaced by `-a`.
|
|
10
|
+
- Rename the `cloud.project_id` field in `webflow.json` to `cloud.app_id`. New deploys always write `cloud.app_id`. Existing manifests with `cloud.project_id` are read transparently — no manual migration needed. The legacy field will be removed in a future major release.
|
|
11
|
+
|
|
12
|
+
### Patch Changes
|
|
13
|
+
|
|
14
|
+
- 2c369de: Fix pluralization in the workspace app-limit error: a limit of `1` now correctly reads "1 Cloud app" instead of "1 Cloud apps".
|
|
15
|
+
|
|
16
|
+
- 2c369de: Show the workspace plan name and app limit in the `webflow cloud create` error when the workspace has reached its app limit. The message now reads, for example:
|
|
17
|
+
|
|
18
|
+
> Your "Starter" workspace is limited to 2 Cloud apps.
|
|
19
|
+
> Upgrade your plan or remove unused apps to create a new one.
|
|
20
|
+
|
|
21
|
+
- 07af4e7: Fix `webflow cloud init` to prompt for authentication before asking project-name, framework, and mount-path questions. Previously, unauthenticated runs would collect all answers and then fail at site lookup, leaving a half-set-up scaffold. Auth errors now surface immediately.
|
|
22
|
+
|
|
23
|
+
- 7ff78f5: Fix `webflow cloud init --no-input --site-id <id>` not connecting the project to the site and skipping DevLink export. Passing `--site-id` now forces the existing-site flow even in non-interactive mode. `--new` and `--site-id` are now mutually exclusive — passing both fails fast with a clear error.
|
|
24
|
+
|
|
25
|
+
- 600a2f6: Skip the "New domain vs existing site" prompt in `webflow cloud init` when the workspace has no Webflow sites. The init flow goes straight to the standalone (new app) path and shows a short note instead.
|
|
26
|
+
|
|
27
|
+
- 03aea02: Suppress the DevLink Export error in `webflow cloud init` when the connected site or workspace is on a plan without DevLink Export. Instead of a red error chain, the CLI now shows a one-line notice and continues normally:
|
|
28
|
+
|
|
29
|
+
```
|
|
30
|
+
ℹ Skipped component export — requires a paid Site or Workspace plan. Upgrade at https://webflow.com/pricing.
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
`webflow export` used directly is unchanged — it still surfaces the full error.
|
|
34
|
+
|
|
3
35
|
## 2.0.0
|
|
4
36
|
|
|
5
37
|
### Major Changes
|