Repository navigation
Closed
Labels
area:spfxCategory: SharePoint Framework (not extensions related)Category: SharePoint Framework (not extensions related)area:spfx-in-listssharepoint-developer-supportsharepoint-developer-supportsharepoint-developer-supporttype:archive-old-issueIssues which are closed as tool old for active workIssues which are closed as tool old for active worktype:uservoice-requestEnhancements & feature requests should be posted: http://aka.ms/sp-dev-uservoiceEnhancements & feature requests should be posted: http://aka.ms/sp-dev-uservoice
Description
What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested
- 💥 Internet Explorer
- 💥 Microsoft Edge
- 💥 Google Chrome
- 💥 FireFox
- 💥 Safari
- mobile (iOS/iPadOS)
- mobile (Android)
- not applicable
- other (enter in the "Additional environment details" area below)
Additional environment details
- browser version
- SPFx version
- Node.js version
- etc
Issue description
In the dev demo of project nucleus, it was mentioned that SPFx support was on the cards. I can't find any literature if or when this will be implemented.
More specifically I'd like to know if I can do the following in an SPFx solution:
Detect if we're in offline mode (e.g., I may not want to allow users to make changes in certain circumstances if I know that it will just be a local cache change)
Detect if sync is enabled and functioning on a list. If sync is not enabled, then I'll know that some queries won't work due to the 5k threshold, and can design the UX accordingly.
If sync is not enabled, is there a way to find out why? There is no clear guide on how sync can be enabled and to troubleshoot why it is not enabled so it would help if we can obtain the reason for sync not working.
In terms of the 5k threshold limitation improvement, would that work for libraries? Would there be a separate cache for the blobs and metadata? For example, a client may not have enough storage to offline the whole library but could have enough storage for the files metadata
Metadata
Metadata
Assignees
Labels
area:spfxCategory: SharePoint Framework (not extensions related)Category: SharePoint Framework (not extensions related)area:spfx-in-listssharepoint-developer-supportsharepoint-developer-supportsharepoint-developer-supporttype:archive-old-issueIssues which are closed as tool old for active workIssues which are closed as tool old for active worktype:uservoice-requestEnhancements & feature requests should be posted: http://aka.ms/sp-dev-uservoiceEnhancements & feature requests should be posted: http://aka.ms/sp-dev-uservoice
Activity
Ashlesha-MSFT commentedon May 5, 2025
Hello smolattack,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.
Ashlesha-MSFT commentedon May 6, 2025
smolattack,
Thank you for your query.
We'll reach out to the engineering team for an update on SPFx support in Project Nucleus and get back to you as soon as we have more clarity.
Ashlesha-MSFT commentedon May 13, 2025
smolattack,
Offline mode is currently not supported with SPFx
smolattack commentedon May 19, 2025
Ashlesha-MSFT Vesa said it would be. When will it be supported?
Ashlesha-MSFT commentedon Jul 18, 2025
smolattack,
Your inquiry aligns with a feature request — specifically regarding support for Project Nucleus (sync lists/offline mode) within SPFx. You've raised important points around:
In the meantime, I’ll go ahead and formally log this as a feature request from our end as well, to ensure it’s tracked internally.
We’ll share any updates as soon as we hear back. Thanks again for highlighting this.
smolattack commentedon Jul 20, 2025
Please include the time stamped youtube link where Vesa says it will be available in SPFx
VesaJuvonen commentedon Nov 3, 2026
This issue is more than 12 months old and has not had recent activity. We are cleaning up the backlog so we can manage incoming reports more efficiently. If the issue is still relevant, please submit a new issue with updated details and current reproduction steps. We apologize for any inconvenience caused by this updated process, and thank you for being part of the SharePoint developer ecosystem.
github-actions commentedon Nov 3, 2026
Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.
If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.
We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.