SharePoint / SharePoint/sp-dev-docs

Question: Correct way to deploy solutions depending on library component solution

Open
#10,509 3 comments 0 reactions 1 assignee View on GitHub

@Ashlesha-MSFT is already working on this.

Since Dec 4, 2025.

area:spfx Needs: Author Feedback sharepoint-developer-support
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

Question for all browsers and all SPFx versions

Issue description

Its not an issue, its a question:
What is the right way to deploy solutions. We have several solutions with webparts and one solution with an library component to share some code.

When we update one solution and the library component solution we often have the problem that the webparts wont load anymore:

Image

The issue is that some new (added in the newest version) function in the library component solution is not found. When I look in the console/source explorer I can see, that the library component is an older version. Its maybe loaded from another solution on the page, which we didnt update.

Do we have to update all solutions which depend on the library component solution if the library is deployed in a new version? Even if we didnt change "existing" code in the library and just added newer code?
Where does the "old" library code come from when we replaced it to a new version in the tenant app catalog?

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.