SuiteScript Pro fills the gap between general JavaScript tooling and the NetSuite concepts your project actually uses: N/* modules, entry points, governance, SDF objects, File Cabinet paths, and local script IDs.
JetBrains already gives you an excellent editor. SuiteScript Pro adds the NetSuite-specific layer it cannot infer on its own, so you can understand a project and move through it without keeping Oracle reference pages and XML searches open beside your code.
Complete supported modules, members, option keys, and enum values. Open offline signatures, summaries, and governance details without leaving the editor.
Detect project roots and understand manifest.xml, Objects, File Cabinet, and deploy.xml as connected parts of one local project.
Complete and navigate project-local customrecord_*, custrecord_*, customscript_*, and customdeploy_* IDs instead of searching XML by hand.
Create SuiteScript 2.0 or 2.1 files, paired script and SDF object definitions, and common snippets with the correct entry-point shape.
Catch common API-version, entry-point, AMD import, and Client Script module-context problems while the relevant file is still open.
Run Oracle SuiteCloud CLI Validate or confirmed Deploy configurations from the IDE when the separately installed CLI is part of your workflow.
Open a folder containing src/manifest.xml. SuiteScript Pro detects the SDF project and reports which core project parts are present. There is no separate plugin account or project import.
In a SuiteScript file, complete N/* imports and module members, inspect signatures and governance with Quick Documentation, and jump between entry points with File Structure. The built-in guide keeps the shortcuts and workflows close by.
Work in SDF XML with local object IDs and File Cabinet paths available to the editor. Command-click a supported local ID to open its definition instead of manually searching the project.
SuiteScript Pro has no Ngaio account, telemetry, cloud analysis service, or Ngaio backend. Its editor assistance reads the local files already opened by your IDE and does not upload your source code to Ngaio.
If you run a SuiteCloud configuration, Oracle's separately installed CLI owns authentication, account selection, network activity, and deployment. The plugin stores no SuiteCloud credentials, and Deploy always asks for confirmation.
JetBrains Marketplace manages the trial, payment, renewal, and license. There is no Ngaio checkout, license key, or local trial timer.
JetBrains understands JavaScript and TypeScript, but not NetSuite's module catalog, governance rules, SuiteScript entry points, SDF object IDs, or File Cabinet conventions. SuiteScript Pro supplies that missing domain layer while keeping the normal JetBrains editing experience.
WebStorm, IntelliJ IDEA, and PhpStorm from 2024.1 through 2026.2. IntelliJ IDEA releases before the unified 2025.3 product require an edition with JavaScript support.
No. Editor analysis runs locally, and the plugin has no Ngaio backend or telemetry. JetBrains may perform Marketplace license checks. If you choose to run Oracle's SuiteCloud CLI, that separate tool controls its own authentication and network calls.
No. Completion, documentation, SDF discovery, navigation, templates, inspections, and structure support work without it. Install Oracle's CLI separately only if you want Validate or Deploy run configurations.
No. SuiteScript Pro is an independent Ngaio product and is not affiliated with or endorsed by Oracle.