| 1 | Create New ExtensionCreate a baseline extension — Get started by creating the files needed for a basic Hello World extension. | Create New Extensiongulp extension:create | Create New ExtensionExtension developer tools create a Workspace directory and a subdirectory that contains the files and initial module for your extension. This is where you develop your extension, using the starter files created by the developer tools as an example. |
| Update Existing ExtensionFetch existing extensions — You need to download files for the active extensions to use as the basis for your customizations. | Update Existing Extensiongulp extension:fetch | Update Existing ExtensionExtension developer tools download Files for any custom extensions that are activated.HTML and Sass files for the currently active theme. Do not modify these files. The Sass and HTML files downloaded using this command are for reference only. |
| 2 | Develop or revise your extension — Create or update files needed to implement custom features or functionality, including JavaScript, SuiteScript, JSON, HTML templates, Sass files, and more. Use your chosen editor in the local Workspace directory created by the extension developer tools. | — | Develop and store your files in the local Workspace directory and subdirectories. |
| 3 | Fetch active theme — You must download files for the active theme before you can deploy an extension or test it on a local server.The extension developer tools require theme files to compile a local distribution for testing on a local server. The developer tools also use these theme files to run a test compilation before deploying.Note If you used the gulp extension:fetch command to update an existing extension in stage 1, you can skip this stage. The fetch command you issued in stage 1 downloads both active theme and extension files. | gulp extension:theme | Extension developer tools download HTML and Sass files for the active theme. Do not modify these files. The Sass and HTML files downloaded using this command are for reference only. |
| 4 | Test locally — You should test your extension locally so you can identify any issues and correct them before deployment.Note If you are developing an extension that includes SuiteScript or JSON files, you must deploy your files to your NetSuite account and activate the extension for these changes to be accessible by the local server. | gulp extension:local | Extension developer tools compile all source files into a LocalDistribution/tmp directory. When you start a local server, the local Commerce app/website uses the Sass, template, and other files from this directory so you can view and adjust your extension in one or more browsers. Changes you make to source files are immediately visible in your local browser. |
| 5 | Deploy your extension — You need to deploy your extension to NetSuite so you can activate it for your Commerce website. | gulp extension:deploy | Extension developer tools validate your code, copy your extension files into a local DeployDistribution directory, and update the manifest.json file. The developer tools then upload these files to your NetSuite account, making them available for activation. |
| 6 | Activate extension — Activating your extension applies it to a Commerce website domain. You can activate your extension using the SuiteCommerce Extension Manager in NetSuite. | — | Your custom extension is active and its functionality is available in the domain you selected during activation. |