SharePoint / SharePoint/sp-dev-docs

Is project nucleus (sync lists) supported in SPFx? #8982

Open
#10,230 6 comments 0 reactions 1 assignee View on GitHub

@Ashlesha-MSFT is already working on this.

Since May 6, 2025.

sharepoint-developer-support type:uservoice-request
Dominant language
PowerShell
Stars
1.4k
Forks
1.1k
Avg merge
4d 12h
Merged PRs (30d)
12

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.