Development tooling

development-tooling.md
Raw file

Three tools can build a Lux experience: Lux Lab, ServiceNow Lux Lab for VS Code, and the ServiceNow SDK. Lux and ServiceNow Lux Lab for VS Code build on the ServiceNow SDK foundation.

Tool comparison

The tools differ in how much of the ServiceNow SDK CLI they wrap in a UI, and where that UI lives.

Tool What it is Where it runs Best for
Lux Lab A ServiceNow application that combines a project explorer, code editor, instance browser, agent chat panel, source control, and build actions in one window Standalone desktop app, downloaded from Lux Lab. Working in a purpose-built tool, and agent-assisted page and widget authoring
Lux Lab for VS Code An extension adding Instance Explorer, Script Runner, Quick Preview, and Lux: commands to VS Code Inside Visual Studio Code Working in VS Code with Lux tooling alongside an existing setup
ServiceNow SDK The CLI that scaffolds, builds, and deploys a Lux application (now-sdk init / build / install) Terminal, in any editor Full control, scripting, and continuous integration (CI) pipelines

Lux Lab and ServiceNow Lux Lab for VS Code are separate products that ship side by side. Pick whichever fits your workflow. Neither is a track you graduate from.

Both wrap the ServiceNow SDK rather than replacing it. Lux Lab runs now-sdk commands on your behalf when you build and deploy. The VS Code extension requires ServiceNow SDK 4.14 or later to be installed.

Next steps

After you pick a tool, see Create your first Lux experience, which uses the Now SDK CLI directly.

Search documentation
Search document titles and file paths on the australia branch