edgeone 1.0.17 → 1.0.19

package/README.md

@@ -146,12 +146,13 @@ This section provides guidance on integrating EdgeOne CLI into your CI/CD pipeli
 The deploy command allows you to deploy a folder or ZIP package directly to EdgeOne Pages from your CI/CD pipeline without using Git-based deployment.
 
 ```plaintext
-edgeone pages deploy <directoryOrZip> -t <token>
+edgeone pages deploy <directoryOrZip> -n <projectName> -t <token>
 ```
 
 #### Parameters
 
 - `<directoryOrZip>`: Path of folder or ZIP package to deploy (required)
+- `-n, --name`: Project name for deployment (creates new or updates existing project) (required)
 - `-t, --token`: API Token for CI/CD pipelines (required)
 - `-e, --env`: Environment to deploy to, choices: 'production' or 'preview' (default: 'production')
 
@@ -159,10 +160,10 @@ edgeone pages deploy <directoryOrZip> -t <token>
 
 ```plaintext
 # Basic CI deployment to production
-edgeone pages deploy ./dist -t $EDGEONE_API_TOKEN
+edgeone pages deploy ./dist -n edgeone-pages-project -t $EDGEONE_API_TOKEN
 
 # CI deployment to preview environment
-edgeone pages deploy ./build.zip -e preview -t $EDGEONE_API_TOKEN
+edgeone pages deploy ./build.zip -n edgeone-pages-project -e preview -t $EDGEONE_API_TOKEN
 ```
 
 #### Obtaining an API Token

package/edgeone-bin/edgeone.js

@@ -1,6 +1,5 @@
 #!/usr/bin/env node
 var _a;
-"use strict";
 var __create = Object.create;
 var __defProp = Object.defineProperty;
 var __getOwnPropDesc = Object.getOwnPropertyDescriptor;