Illuminated Cloud Announcements

2.4.0.5 Salesforce CLI issue 3560 - IMPORTANT: The Salesforce CLI is in the process of implementing a set of security mitigation changes, some of them with breaking behavior . Starting with this build, IC accommodates for the changes around how connection access tokens are made available via CLI commands. For pre-2.136.8 CLI versions, IC will use continue to the org list and org display commands to get CLI-based connection access tokens; for 2.136.8+ CLI versions, IC will use the org auth show-access-token command. IC automatically determines the installed CLI version and, for efficiency, caches that value aggressively, though it should be resilient to CLI upgrades/downgrades while running. In support of Salesforce's goal of not having access tokens stored in-the-clear in the file system, IC no longer caches them persistently across IDE sessions. They are still cached aggressively in-memory, but if/when the IDE is restarted, IC will need to fetch access tokens for CLI-based ...

2.4.0.4 Issue 2951 - Added first-class support for UI Bundles and Salesforce Multi-Framework . Note that this feature requires native IDE JavaScript/TypeScript/CSS/React support, so you'll need to pair Illuminated Cloud with either a commercial JetBrains IDE or a free 2026.1+ JetBrains IDE. A demonstration video is available here. As part of this work, the Illuminated Cloud application-level settings tab LWC has been renamed UI Frameworks and now includes options for configuration of both Lightning Web Components and UI Bundles behavior. The new/changed options are: LWC Enable LWC local development - LWC local development support has existed for some time, but it wasn't possible to disable it. Now it can be disabled if desired, but it is enabled by default . Disable deploy-on-save of LWC source files when the local development server is running - This option was moved from the Deployment tab (previously called Validation and Deployment ) to be closer to its related setti...

2.4.0.3 Issue 2919  (redux) and  Issue 2955  - Improved handling of references to  *-meta.xml  files when those files are renamed, particularly in other XML files such as  package.xml  and permission sets/profiles. Issue 2949  - Prospective fix for an issue where loaded scratch org definition files in the create scratch org dialog could be based on stale cached information. Issue 2952  - Improved Apex offline debugger source position determination when stub/synthetic declarations are involved, e.g., default no-arg constructors. Issue 2956  - Fixed an issue where Apex coverage would not be displayed properly after unit test execution. Extended IC's assisted installation/configuration support for agentic AI tools to include more agentic AI JetBrains plugins and more/more recent Salesforce-specific support components. A demonstration video is available  here . In  Illuminated Cloud | Configure Application | Agentforce , the  ...

2.4.0.2 Issue 2950  - Updated the  *scratch-org-def.json  JSON schema for the latest-and-greatest settings types. Added support for aer-based profiling of executed unit tests via the  Profile " Run Configuration Name " with aer  Apex unit test executor. After aer test execution, the resulting profiling snapshot is automatically opened in the  Perfetto trace viewer  for review. Note that aer is a different Apex runtime than the Salesforce server and will have different performance characteristics, though the resulting profiling data should hopefully be directionally useful. It can, of course, also be used to understand aer-based test execution hotspots and bottlenecks. To profile org-based execution, use the Salesforce server Apex unit test profiling executor and IC's Log Analyzer. Added another aer unit test execution configuration option to add the  --skip-errors  option always when aer is executed. This option is  enabled by default ...

2.4.0.1 As noted in the previous release notes, starting with 2026.1,  free  JetBrains IDEs now include  first-class language support  for  JavaScript, TypeScript, and CSS  (i.e., without an active JetBrains subscription). Also as stated previously, the main things that are notably missing are the JavaScript debugger and Jest support, but I've addressed those omissions in IC. A  demonstration  of these features is available  here . Note that the items described below are  only  available in  free JetBrains 2026.1+  IDEs. All  commercial  JetBrains IDEs already have their own versions of the same features, and they will not work with earlier free JetBrains IDEs because they build on the 2026.1+ IDEs' free JavaScript and TypeScript support. Users pairing IC with a free JetBrains IDE are  strongly encouraged  to use 2026.1+ going forward. With that preface out of the way, IC now includes  first-class ...

2.4.0.0 Issue 2939  - Fixed an issue that could occur when an error is reported for a source file by the API or CLI with a simplified path, e.g.,  classes/Foo.cls , where the local path is more complex, e.g.,  classes/subfolder/Foo.cls . Now if no matches are found using the reported path, IC looks for a unique source file with the same name and, if found, reports against it. Issue 2941  - As of  2026.1 , IntelliJ IDEA includes  first-class language support  for JavaScript, TypeScript, and CSS  for free  (i.e., without an Ultimate subscription). This includes not just basic language support features like intelligent code completion, reference navigation, source code formatting, etc., but also extensive refactorings, static code analysis including integration of ESLint and Stylelint, tight npm integration, and much more. The main things that are notably missing are the JavaScript debugger and Jest support, but I'm working on a very tight integ...

2.3.9.9 Enabled support for the 2026.1 JetBrains IDEs that are now in a  release candidate state . As always, if you see issues with a pre-release IDE build, please revert to the most recent released build and let me know about the issues you've seen so that I can address them. Issue 2929  - Made sure that the connection icon includes a lock overlay consistently for connections that require write confirmation. It was most noticeably missing in the connection status bar widget. Issue 2936  - Fixed a  StackOverflowError  that could occur when overriding dynamic file types. Fixed a few issues with placeholder  *.object-meta.xml  files being incorrectly treated as full custom object files during metadata deployment and retrieval. Improved CLI-based deployment result reporting where some information was being sent to  successes  and  failures  instead of  files  in the JSON result. Added support for contextually-correct code co...