Undocumented restriction to lightning experience only?

[readeral]

Sorry for asking this in the example repo, I wasn't sure where to get clarification - here or in the lwc repo - but given it feels like a documentation gap, I thought I'd start here!

I've attempted to use @lwc/state in Experience Cloud in a preview org (LWR build-your-own), and the module is returning 404. I'm not sure if it's because I need to set a flag to opt into the beta, or because of lightning locker, or just because the module is not available in the LWR runtime.

My hunch is the latter, that @lwc/state is lightning-experience only at the moment?

[mburr-salesforce]

Let me check with the Experience Cloud folks & see if we need to add extra logic to make the module usable there. Our assumption is that it would work fine given that LEX and CLWR share a significant amount of module loading logic internally.

[readeral]

Thanks @mburr-salesforce

Investigating a little further into things I don't quite understand, @lwc/state tries to resolve from /scm/webruntime/component/latest/dev/en-GB/%40lwc%2Fstate, and is of course not there.

However, the compiled code for my Experience Cloud page (view) contains the following:

(function() { LWR.define('forcegen/lwcState', ['exports', 'lwc'], (function (exports, lwc) {
     ...
    exports.defineState = defineState;
    exports.fromContext = fromContext;
    exports.instrument = instrument;

    Object.defineProperty(exports, '__esModule', { value: true });
}

So its definitely "there" in the mix, just the module isn't resolving correctly or something? Again, I have no idea what I'm talking about 😅

[mburr-salesforce]

The handling of @lwc/state is a bit convoluted due to (a) the way the module works in our internal build process, and (b) constraints in the LEX namespace rules. The forcegen/lwcState module you've discovered is the name that internal Salesforce modules use, but forcegen modules are not visible to customer code. In LEX there is a special module resolver that maps @lwc/state in customer code to force/lwcStateManager. We're working on getting an equivalent mapping added to CLWR (Experience Cloud).

[readeral]

Awesome, thanks @mburr-salesforce - is that likely to be tied to a major release (i.e. misses the Spring 26 window) or potentially gets patched? (I totally understand if its not your place to say!)

[mburr-salesforce]

That's up to the Experience Cloud folks. It depends on the complexity of the change & whether they're comfortable releasing it in a patch or not. I'll follow up here when I hear back from them.

[readeral]

@mburr-salesforce thanks so much

[readeral]

That's up to the Experience Cloud folks. It depends on the complexity of the change & whether they're comfortable releasing it in a patch or not. I'll follow up here when I hear back from them.

Hi Mike, sorry to poke you. I just wonder if this has got to a point where there's more information? and if not, perhaps a better avenue for me to hassle someone down instead of you! If there is clarity over the cause, maybe it'd be worth getting some caveats into the docs until its available in Experience Cloud?

[mburr-salesforce]

I just checked on the internal work item for this on Friday afternoon & it's still sitting in "new" state. The Experience Cloud team currently has the work marked for the Summer 26 release with a note that a backport to Spring 26 will depend on availability of the team.

If there is clarity over the cause, maybe it'd be worth getting some caveats into the docs until its available in Experience Cloud?

We know the exact cause (see above). @alderete-sfdc can we add a caveat to the doc to clarify that the state manager beta is not yet supported on Experience Cloud.

[readeral]

Great, thanks for all your help @mburr-salesforce, some nice clarity thankyou. As keen as I am for this landing (would be a great addition to a very complex Experience Cloud-based application once it's supported!) it looks like we're a cycle away from being able to test it out. I'm happy for this issue to be closed.