| \n\n[ServiceNow IDE\\[Omitted image \"servicenow-ide-logo.png\"\\] Alt text:Develop applications in code in an IDE on the ServiceNow AI Platform.](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-ide-family-release/servicenow-ide-landing.md)\n\n | \n\n[ServiceNow SDK\\[Omitted image \"servicenow-sdk-logo.png\"\\] Alt text:Develop applications in code locally and upload changes to an instance.](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/servicenow-sdk/servicenow-sdk-landing.md)\n\n |
| \n\nFeature\n\n | \n\nServiceNow IDE\n\n | \n\nServiceNow SDK\n\n |
|---|---|---|
| \n\nDevelopment environment\n\n | \n\nOnline ServiceNow instance\n\n | \n\nLocal development and the ability to work offline\n\n |
| \n\nUser interface\n\n | \n\nIDE based on Visual Studio Code for the Web\n\n | \n\nVisual Studio Code Desktop\n\n |
| \n\nCollaboration\n\n | \n\nView any user's changes in real time in code or embedded ServiceNow AI Platform user interfaces.Collaborate with other developers on applications in source control.\n\n | \n\nDownload changes from an instance and install local changes to an instance using the ServiceNow SDK CLI to collaborate with other users. Collaborate with other developers on applications in source control.\n\n |
| \n\nSource control\n\n | \n\nSupports the most common Git functionality and integrating with a Git provider of your choice.One concurrent branch per repository per instance\\(or developer sandbox\\).\n\n | \n\nFull support\n\n |
| \n\nApplication conversion\n\n | \n\nSupport for converting existing applications not created with the ServiceNow IDE or ServiceNow SDK.\n\n | \n\nSupport for converting existing applications not created with the ServiceNow IDE or ServiceNow SDK.\n\n |
| \n\nServiceNow Fluent\n\n | \n\nFull supportThe ServiceNow Fluent Language server is included with the ServiceNow IDE.\n\n | \n\nFull supportThe ServiceNow Fluent Language server can be installed from the Visual Studio Code Extension Marketplace.\n\n |
| \n\nJavaScript modules and third-party libraries\n\n | \n\nFull support\n\n | \n\nFull support\n\n |
| \n\nServiceNow Otto for Code\n\n | \n\nCode auto-complete support for scripts.For information about activation, see [ServiceNow Otto for Code](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/api-reference/scripts/now-assist-code-landing.md).\n\n | \n\nNot supported\n\n |
| \n\nBuild Agent\n\n | \n\nFull support. Build Agent is accessed from a chat panel in the ServiceNow IDE.For information about activation, see [Build Agent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/build-agent.md).\n\n | \n\nBuild Agent skills are available beginning with ServiceNow SDK version 4.6.0.\n\n |
| \n\nDirectory or file\n\n | \n\nDescription\n\n |
|---|---|
| \n\n.vscode\n\n | \n\nDirectory containing recommended Visual Studio Code extensions.\n\n |
| \n\ndist\n\n | \n\nDirectory containing the build artifacts for packaging. This directory includes the following subdirectories:- `app`: Directory containing the built metadata XML files.\n- `static`: Directory containing the built static asset files.\n\n |
| \n\nmetadata\n\n | \n\nDirectory containing the application metadata \\(XML\\) of the application, such as table schemas and business rules, organized in the same directory structure as existing ServiceNow applications.\n\n **Note:** Application metadata shouldn't be edited from the XML files. Edit application metadata in the source code or on the ServiceNow AI Platform.\n\n |
| \n\nnode\\_modules\n\n | \n\nDirectory containing the third-party Node.js modules on which your application depends.\n\n |
| \n\nsrc\n\n | \n\nDirectory containing the source code of your application. This directory includes the following subdirectories:- `client`: Directory containing the client-side files for developing user interfaces.\n- `fluent`: Directory containing ServiceNow Fluent code in `.now.ts` files. The `generated` subdirectory contains the application files converted to ServiceNow Fluent.\n- `server`: Directory containing JavaScript module code in `.js` or `.ts` files.\n\n |
| \n\ntarget\n\n | \n\nDirectory containing an installable package \\(`.zip` file\\) to upload to an instance.\n\n |
| \n\n.eslintrc\n\n | \n\nFile containing the ESLint configuration. ESLint helps identify and fix issues in the application code.\n\n |
| \n\n.gitignore\n\n | \n\nFile containing a list of directories or files for Git to ignore. These files aren't tracked in source control.\n\n |
| \n\nnow.config.json\n\n | \n\nFile containing the ServiceNow application configuration. The `now.config.json` file must be in the base directory for an application. You can configure aspects of an application by adding support parameters. For more information, see [Custom application configuration in source code](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/app-config-source-code.md).\n\n |
| \n\nnow.prebuild.mjs\n\n | \n\nAuto-updated file containing complete information about dependencies and their versions. This file is only available with the ServiceNow SDK.\n\n |
| \n\npackage-lock.json\n\n | \n\nAuto-updated file containing complete information about dependencies and their versions. This file is only available with the ServiceNow SDK.\n\n |
| \n\npackage.json\n\n | \n\nFile containing information about your application and custom or third-party module dependencies. The `package.json` file must be in the base directory for an application. On an instance, the `package.json` path is specified in the **Package JSON** field of the custom application record \\[sys\\_app\\] in the format ` |