As part of our initiatives to better our app development environment and enable developers to build secure apps, the app development platform and the FDK are constantly upgraded. Though most of the upgrades are seamless and inherently handled by the FDK, at times upgrades entail migrating an app manually. In such cases, the FDK throws warning or error messages with appropriate links to resources that help in migration.
Important:When you run Freshworks CLI commands, an upgrade check is performed only if it hasn’t been performed in the last 24 hours. If a check has run in the last 24 hours, migration or upgrade warnings are not displayed.
The migration map
FDK and compatible Node.js versions
FDK version | Node.js version | Support for Node.js - status |
---|---|---|
9.0.0 or later | Node 18.x | Live |
8.0.0 - 8.6.7 | Node 14.x | Deprecated as of December, 2023. |
7.0.0 - 7.5.1 | Node 12.x | Deprecated as on September 30, 2022. |
Prior to 7.0.0 | Node 10.x | Deprecated. |
There is a major version mismatch between the Node.js version used to build the app and the current version on which the app is run.
The FDK displays a warning message (provided an upgrade check is not run in the last 24 hours). The message mentions the Node.js version on which the app is developed, the version on which the app is run currently, and prompts for continuation.
- Type Yes. The FDK,
- Deletes the existing coverage folder if the app has a serverless component. The folder contains the coverage summary captured as a result of the previous fdk run. Note:The coverage folder is retained for front-end apps.
- Deletes the existing node_modules folder. The folder contains the npm dependencies (specified in manifest.json) that were installed during the previous fdk run.
- Includes or updates the engines attribute in manifest.json. The updated engines.node and engines.fdk values reflect the Node.js and FDK versions on which the app is validated.
- Displays an error message stating that the earlier platform version is deprecated, if the app was built on an earlier platform version. The latest platform version is 2.3.
- Displays an error message stating that the parameter whitelisted-domains in manifest.json is deprecated.
- Migrate your app to the latest platform version.
- Run the fdk run command to test the app. This generates the coverage folder.
Migrate to the latest platform version
Construct request templates (config/requests.json)
If your app uses the request method to make secure HTTP calls to third-party domains, you should modify the app files such that they use the latest templated request method. To perform this,
- From the app’s root directory, navigate to the config folder and create a requests.json file.
- In requests.json, provide appropriate <requestTemplateName>s and create empty snapshots for all requests that the app uses. For information on how to create a snapshot, see Configure request templates.
- In your app.js or server.js files, look for the details of the schema and options attributes and move them to appropriate sections of config/requests.json - that is, fill in the snapshot.
Core request attributes
In app.js or server.js, look out for properties such as headers and URL. Move the values of these properties to the corresponding attributes in config/requests.json. The mapping is as follows:
options attributes
In app.js or server.js, look out for options such as headers, maxattempts, retryDelay, and isOAuth. Move the values of these options to the corresponding attributes in config/requests.json. The mapping is as follows:
manifest.json changes
platform-version: From the app’s root directory, navigate to manifest.json. Modify the platform-version value to 2.3.
In manifest.json, remove the deprecated attribute - whitelisted-domains.
If your app uses the request method to make secure HTTP calls to third-party domains, in manifest.json, list all request templates that the app intends to use. To do this, under product.<productName>, add a requests attribute of the following format.
"requests": { "<requestTemplateName>":{}, "<requestTemplateName1>": {} … }
Note:Ensure that the <requestTemplateName> is the same as that configured in config/requests.json.
To migrate a serverless SMI app built on FDK versions prior to 6.13.0, in manifest.json under product.<productName>, allow list all SMI functions/methods defined in the serverless component of the SMI app. To do this, in manifest.json, add an attribute - functions of the following format and list all SMI functions (server methods) defined in the exports code block of the app’s server.js file:
"functions": { "<serverMethodName1>": {}, "<serverMethodName2>": {} }
To migrate a serverless app built on FDK versions prior to 6.13.0, in manifest.json, under product.<productName> register all the serverless events defined in server.js and the corresponding callback methods. To do this, in manifest.json, add an attribute - events of the following format and list all serverless methods defined in the exports code block of the app’s server.js file:
"events": { "<eventName1>": { "handler": "<callbackFunctionName1>" }, "<eventName2>": { "handler": "<callbackFunctionName2>" } }
For more information, see App Manifest.
App code changes
- The latest FDK version supports app creation, testing, validation, and packing in a local developer environment that is based on Node.js 18. In your app code, ensure that the app code doesn’t contain any Node.js features that are deprecated.
- In the front-end HTML files (such as iparams.html), replace the existing client JS resource as follows:
Replace:with:<script src="https://static.freshdev.io/fdk/2.0/assets/fresh_client.js"></script>
<script src="{{{appclient}}}"></script>
- If your app uses the request method to make secure HTTP calls to third-party domains, you should modify the app.js file such that it uses the latest templated request method. To do this, look for the details similar to the ones mentioned in the following table and move them to the appropriate specified format.
Migrate to the latest FDK version
- Install Node.
- Install the Freshworks CLI. This upgrades your local FDK version to the latest FDK version. Important:The latest FDK version supports app creation, testing, validation, and packing in a local developer environment that is based on Node.js 18. Ensure that the app code doesn’t contain any Node.js features that are deprecated. Note:The latest FDK version contains support for the use of ES2020 features when building apps. This enables using ES2020 features such as optional chaining operators in your app code.