---
sourceDocument: Brazil Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/application-development

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Explore

# Exploring the UI component CLI extension {#ariaid-title1}

Release version: Brazil  
Updated October 24, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Learn about UI component CLI extension concepts and features.

The UI component CLI extension abstracts the workflows that you use to build Next Experience UI Framework components. Instead of running separate tools for each stage, you run commands from the ServiceNow CLI.

## Component development workflow

The extension supports the following stages of component development:

* Project scaffolding, which creates the files that a new project needs.
* A local development server, which runs components so that you can evaluate and iterate on them.
* Deployment, which installs the component into a ServiceNow instance.

Figure 1. Next Experience UI component development workflow

## Scope and deployment

Next Experience UI Framework components deploy to a ServiceNow instance as part of a scoped application. Each component is written to the records of a specific scope.

You define the scope name for a project in the now-ui.json file. When the component deploys, its records are written to the tables that belong to that scope. Only one project can deploy to a single scope.

A valid scope name meets the following requirements:

* It is unique on the instance.
* It uses snake case and has no more than 18 characters.
* It follows the form `x_customerprefix_componentname`, where the customer prefix matches the value of the `glide.appcreator.company.code` system property.

If you don't provide a scope name, the extension creates one from the vendor prefix and the package name. A scope name that does not meet these requirements can prevent the project from deploying.