🔜 Update: Local Development Server Deprecation Notice & Announcement

[AnanyaJha]

Deprecated, we are working on making a new announcement. [05.01.2024]

Over the past few years, we've received quite a bit of feedback on the current state of the Local Development Server; it was one of the top asks from the State of LWC Development survey in 2023. It's become very clear that the feature is not serving your needs in its current state - and it has the potential to be a productivity multiplier.

We've heard your feedback and we have some updates! We're hard at work building a new solution for Local Development - - with a goal of a Spring '25 GA.

This new solution will be integrated with your VS Code and Code Builder IDEs - more information will be shared soon.

In the interim, we will be deprecating the current LWC Dev Server related commands within the Salesforce Extension Pack starting April 15th. The following commands will be removed from the SF Extension Pack:

• SFDX: Open Local Development Server
• SFDX: Start Local Development Server
• SFDX: Stop Local Development Server

As always, please share feedback and thoughts here.

[jmcnaughton-isuf]

Any suggestions or recommendations for interim substitutions? The local dev server in theory could be a real time saver like you say but there has been significant issues since December of 2022 and now we likely arent going to see anything till 2025?

[AnanyaJha]

Hi @jmcnaughton-isuf , could you tell me more about how you or your team have been working with the local dev server currently? Our impetus here is to ensure that any available solution is working correctly and we can provide you with adequate support to resolve any issues. We've made a decision to not invest further in the current solution and instead prioritize the newer one, coming soon.

I'll be sure to update this post with any Beta timelines in 2024 as soon as we have that info. In the meantime, it'd be helpful to understand the impact of deprecating the current local dev experience for your team.

[nttjansterl]

@AnanyaJha The impact is pretty simple: Instead of automatic hot reloads, we have to deploy to an org, wait and manually refresh every time we make a change.

Ask one of your frontend devs how often they perform incremental updates and they'll tell you, that they perform this type of operation hundreds if not thousand times per day.

Local Development Server allowed for this - working with frontend components, you now spend more time waiting than writing code, which increases development time at least x10.

[lukethacoder]

Looking forward to the official Local Development Server release but I really couldn't wait much longer, have sadly barely used it due to CSS Variables not being supported. Sharing because it is such a time saver when building for on-platform.

• https://lwc.garden/
• https://github.com/lukethacoder/lwc-garden
• https://stackblitz.com/edit/lwc-garden-minimal-config?file=garden.config.js

Full support for CSS Variables and anything else you could want from the modern web.

• 🚀 Local First Development (feat. Speedy HMR)
• 🧪 Mock Anything (Apex, OmniScript, 3rd Party Packages and on-platform imports)
• 🥧 <slot/> Placeholders
• 💅 SLDS Support OOTB (and lightning-base-components)
• ✏️ API Editor via Storybook-like argTypes
• 🎨 Custom Theming API
• ⚙️ Config as much or as little as your like
• 🙌 And best of all, open sourced

[ev-will]

@AnanyaJha The impact is pretty simple: Instead of automatic hot reloads, we have to deploy to an org, wait and manually refresh every time we make a change.

Ask one of your frontend devs how often they perform incremental updates and they'll tell you, that they perform this type of operation hundreds if not thousand times per day.

Local Development Server allowed for this - working with frontend components, you now spend more time waiting than writing code, which increases development time at least x10.

I also frequently use the Local Development Server for creating lightning components. Removing this functionality is a significant impediment to my efficiency.

As for how it was used... I would build my component out entirely using the local development server. Once I deemed it acceptable, I would deploy it to my scratch org or sandbox. I also taught all my devs to use it. In my opinion, it was an essential piece to the LWC development process. I am severely disappointed that this was deprecated without an official, alternative option.

[MohitPushpam]

Hi @AnanyaJha Is there any update related to new release as mentioned date [05.01.2024] has been passed.

[rsensharma]

Important Update: Changes to our deprecation plans
Remember when we mentioned plans to deprecate certain commands by mid-April? Well, after thorough testing, we’ve decided to keep them in action because they’re functioning just as they should!
However, we want to give you a heads-up on a few things to consider when using these commands. Specifically, if your Lightning Web Components include lwc:if, lwc:elseif, or lwc:else directives, you might encounter issues with the preview command. Why? Because our dev server doesn’t quite sync up with them yet.
While we won’t be issuing any fixes for this, we’ve got a brand-new solution in the pipeline slated for next year! So, stay tuned for that.
In the meantime, keep utilizing those commands and stay tuned for more updates. We’re committed to keeping you in the loop every step of the way.