Since LWC was released without support in the Developer Console. Also, not intention to some kind of DX support I'm wondering is it going to die?

I google it and look for some official or unofficial information but nothing trustable is out there.

I know this forum is not for opinions and debates. But honestly, I think that Salesforce as a main cloud solution provider should give some web-based IDE.


The best current official source for information on the future of the Developer Console would be Nathan Totten (@ntotten). ‏ The last official thing I saw was in The Future of Salesforce IDEs blog post.

I don’t have a roadmap to share today, but I do want to assure you that this is an area we care deeply about and are investing in.

The following does not constitute something official from Salesforce yet, so don't come back to me if somehow the developer console is still the only fully integrated web-based IDE for Salesforce in 10 years.

Unofficially, you can turn to twitter:

@ntotten @ccoenraets Any plans to add to the DevConsole support for #LWC? I checked in Spring19 org and I needed to use VScode to create them. Thanks! Roy Gilad

Unfortunately, DevConsole will not get LWC. Building a modern dev experience for LWC is simply not possible in DevConsole. However, we are working on a replacement tool that supports LWC (and everything else) that will be much nicer. Details coming later this year. Nathan Totten

Another good one:

Don't forget to let us know what you want to see in the next version of "Dev Console" by opening feature requests on Github: https://github.com/forcedotcom/devconsole/issues/new?template=feature_request.md


Getting warmer:

Tooling API info will be documented soon (I think they are releasing all that on the 17th). Regarding DevConsole, we will NOT be supporting LWC in DevConsole. We are currently working on a replacement to DevConsole that will fully support LWC (and existing metadata/code).


The one thing I can say from that... Visit https://github.com/forcedotcom/web-tools/issues and register what you would want to see in a future version of the Dev Console.

  • 1
    This is what I call a good research :). Than you Daniel. I hope to see a better web-based replacement of DevConsole soon. I'll be posting some ideas on github. – Martin Borthiry Feb 23 at 10:02

LWC is meant to be used in a "source of truth" model that includes a repository. This is because the unit tests are not uploaded/stored in Salesforce, so the entire LWC needs to be offline somewhere or you'd lose some of the files. The Developer Console is still supported, and has not been deprecated in any official channel that I know of. Until/unless it is announced in release notes and/or another official channel, you can presume that the Developer Console will be viable for the foreseeable future.

  • thank you Brian! I hope so. I should remain active or have a better web-based replacement soon. – Martin Borthiry Feb 23 at 10:00

There's no official mention about Developer Console being deprecated. And I wouldn't think that it's going to be deprecated anytime sooner.

While it may not be supported for LWC specifically but it still has its place. It still proves to be a handy tool for quite a few things. And that you can always use it not only for editing Apex, VF, Lighting Aura Components, etc. but also utilize one of a very important tools for query optimization, i.e., Query Plan Tool, which is as of now available only through Developer Console.

  • In one of the developer meeting on LWC, a speaker from Salesforce told that including LWC in the developer console is in the roadmap. Not sure when it is going to be available. – sanket kumar Feb 22 at 18:53
  • Information is being contradictory from SFDC side, some are saying that it will be supported but others that will be replaced... will see – Martin Borthiry Feb 23 at 10:03

The developer console is a convenient tool that’s used daily by many Salesforce developers. You can still use it to access Apex classes, Visualforce pages and Aura bundles; however, it's not a full-blown IDE. Also, in its current form, the developer console can't provide integrated support for much of the tooling that ships with the Lightning Web Components Salesforce Extension, like ESLint.

You'll get the best developer experience using more robust tools like VS Code and the Salesforce Extensions, or Illuminated Cloud. Your users will also benefit because these tools can help you identify and avoid common issues in your code as you write, and before you even try to deploy to development environments.

With saying that there are many capabilities which are available in Developer console and there is no roadmap to retire this tool

Ref: Developer Tools for Lightning Web Components

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.