The Freshworks developer platform now supports running apps on Node.js 24. FDK 10.0.0 includes updates that support app creation, testing, validation, and packaging in a local development environment based on Node.js 24.
What’s new
With FDK v10.0.0, you can build and run apps using Node.js 24.x, giving you access to the latest performance improvements and features from the Node.js ecosystem.
Migration timeline
Support for Node.js 18 will be deprecated by March 20, 2026 for new apps and on April 10, 2026 for existing app upgrades. After April 10, 2026 existing apps using Node.js 18 will continue working as expected. Ensure you migrate to FDK 10.0.0 before the deprecation deadline.
Key dates
March 20, 2026: Deprecation date for new app submissions built on Node.js 18
April 10, 2026: Deprecation date for existing app submissions built on Node.js 18
After April 10, 2026, the platform will accept new versions of existing app submissions only if they are built using Node.js 24.x.
FDK and compatible Node.js versions
FDK version
Node.js version
Status
Node version Supported till
10.0.0 or later
Node 24.x
Live
December 2027
9.0.0 - 9.8.2
Node 18.x
Planned for deprecation (March 20, 2026 for new apps; April 10, 2026 for existing apps)
March 2026
8.0.0 - 8.6.7
Node 14.x
Deprecated as of December 2023
December 2023
7.0.0 - 7.5.1
Node 12.x
Deprecated as of September 30, 2022
September 2022
Prior to 7.0.0
Node 10.x
Deprecated
Getting started
Upgrade to the latest FDK version to start building with Node.js 24:
For migration guidance and compatibility details, see FDK and compatible Node.js versions. If you have any queries feel free to comment under this post or reach out to our team via Devassist
After April 10, 2026 existing apps using Node.js 18 will continue working as expected. Thanks for pointing out! We updated the post for everyone. Thanks.
Hey Thomas, you will have to install the specific version 24.11.x, you could use 24.11.0. If you have multiple Node versions installed, you can manage them using nvm, please find the OS specific instructions in these docs.
Thank you for your fast response - Unfortunately, I do not have Admin access on my Windows laptop.
So I need to reach out to our IT to support me installing the correct version.
So because of your post, we went for 24 latest.
I will get back to them and ask if they will provide me 24.11.
already got an answer - IT will only provide latest stable versions, arguing with security as reason why.
Is there any chance that you will allow later than 24.11?
Like you did with v18 where the documentation says v18.13 or later and I was on v18.19 or v18.20 lately.
all my variables got lint error. please help me to resolve this. its happen after my app got updated.
this is an example:
Lint errors: app\scripts\data\test1.js::1: ‘data1’ is assigned a value but never used. app\scripts\data\test2.js::1: ‘data1’ is assigned a value but never used.
Please ensure that the following are addressed for quick review process: app\scripts\app.js::6: ‘client’ declared and assigned in different scopes. Possible asynchronous race condition. app\scripts\data\test1.js::1: ‘data1’ is never reassigned. Use ‘const’ instead. app\scripts\data\test2.js::1: ‘data1’ is never reassigned. Use ‘const’ instead.
Lint errors: app\scripts\app.js::246: ‘STATUS_OPEN’ is assigned a value but never used. app\scripts\app.js::247: ‘STATUS_PROCESSING’ is assigned a value but never used. app\scripts\app.js::248: ‘STATUS_UNDER_INVESTIGATION’ is assigned a value but never used. app\scripts\app.js::249: ‘STATUS_WAITING_FOR_CUSTOMER’ is assigned a value but never used. app\scripts\app.js::250: ‘STATUS_PENDING’ is assigned a value but never used. app\scripts\app.js::251: ‘STATUS_RESOLVED’ is assigned a value but never used. app\scripts\app.js::252: ‘STATUS_CLOSED’ is assigned a value but never used. app\scripts\app.js::253: ‘ISSUE_TYPE_TASK’ is assigned a value but never used.
Hi,
Regarding the lint issue, It looks like our current linting validator is not detecting variable usage within HTML files.
We will work on a fix for this issue.
As a temporary workaround, you can run the FDK command with lint validation disabled:
app\scripts\data\test1.js::1: ‘data1’ is assigned a value but never used.
app\scripts\app.js::6: ‘client’ declared and assigned in different scopes. Possible asynchronous race condition.