edgeone 1.2.29 → 1.3.0-beta.1

package/README.md

@@ -56,7 +56,7 @@ After successful login, execute the initialization command to initialize the bas
 edgeone pages init
 ```
 
-After initialization, an `edge-functions` or `node-functions` folder and sample functions will be generated in the root directory of the project. You can continue to add and develop functions in this folder.
+After initialization, an `edge-functions` or `cloud-functions` folder and sample functions will be generated in the root directory of the project. You can continue to add and develop functions in this folder.
 
 ### 4. Local Development
 
@@ -68,10 +68,10 @@ edgeone pages dev
 
 The run command by default creates a service locally on port 8088. Both the Pages Function service and the Pages project service run on the same port, with no need for additional proxying.
 
-You can access the front-end page via `http://localhost:8088/`. In the front-end project, use the Fetch API directly, where the access path is the path of function files in folder `edge-functions` or `node-functions`.
+You can access the front-end page via `http://localhost:8088/`. In the front-end project, use the Fetch API directly, where the access path is the path of function files in folder `edge-functions` or `cloud-functions`.
 
 ```javascript
-// ./node-functions/api/my-functions.js
+// ./cloud-functions/api/my-functions.js
 fetch('/api/my-functions', {
   method: 'POST',
   body: JSON.stringify({ data: 'example' }),
@@ -154,7 +154,7 @@ edgeone pages deploy [<directoryOrZip>] -n <projectName> -t <token> [-e <env>]
 - `-t, --token`: API Token for CI/CD pipelines (required for automated deployments)
 
 Note:
-- By default, when executing deploy, the CLI automatically builds and packages frontend code, `node-functions`, and `edge-functions` into the `.edgeone` folder and deploy to Pages.
+- By default, when executing deploy, the CLI automatically builds and packages frontend code, `cloud-functions` (or `node-functions` for legacy projects), and `edge-functions` into the `.edgeone` folder and deploy to Pages.
 - If you choose to build the project manually, you need to manually copy the Pages Functions related folder and `package.json` to dist (suppose the output directory is dist), then rerun `edgeone pages deploy ./dist`.
 
 #### CI/CD Pipeline Examples