Skip to main content

Part URI is not valid per rules defined in the Open Packaging Conventions specification issue with SPFx package

"Part URI is not valid per rules defined in the Open Packaging Conventions specification" is very common issue and everyone who have worked with the SPFx, have faced this issue at least once.

But interesting thing is that, User will not get any information about this error on the terminal or console.

How to resolved "Part URI is not valid per rules defined in the Open Packaging Conventions specification"

Let's discuss root cause of the problem and steps to resolve this error:

  1. Check your project folder name, if your project folder name have any underscore/space/dash remove them because this is one of a cause behind this issue.

  2. Check assets you have used in your solutions, check the CSS file, .tsx file, JS file, images, Ts file, font libraries and if they have any underscore/space/dash in the file name remove them.

 Let's fixed this issue:

  1. Remove the underscore/space/dash from project folder name and from css, ts, tsx, js, font library, images. 
  2.  gulp clean
  3. gulp bundle –ship
  4. gulp package-solution –ship
  5. Deploy the .sppkg file to the app catalogue

    Please refer this blog for Component ID {0} exists in solution {1} already

    Thanks!!

    Labels:

    Comments

    Post a Comment

    Popular posts from this blog

    SPFx Interview Questions With Answers

    In this article, we are going to discuss interview questions related to the SPFx (SharePoint Framework Development ). It will help you to prepare for the interview and in getting clarity on the core concepts of SPFx development. What is SPFx? SPFx, short for SharePoint Framework,  SPFx  allows us for client-side SharePoint development, we can easily connect with SharePoint data and it also supports for open source tools. What is the major difference between SPFx web part and the SharePoint app? Both the development model supports client-side development but the major difference between these two is that the SharePoint app(add-in) runs on the iframe. What you can build with SPFx? Using SPFx framework we can customize the SharePoint pages. We can build things mentioned below using the SharePoint Framework(SPFx). Web parts, Extensions, Adaptive Card, Library Component How many types of extensions we can create using SPFx? SPFx has three extension types: Application Customizers: U...
    2 comments
    Read more

    How to register an app in SharePoint

    In this article, we are going to learn how to register an app/add-in in SharePoint online. If you have created a Sharepoint provider-hosted add-in or other SharePoint solution and to access the SharePoint site or list using the app/add-in you need to register the add-in on SharePoint and to grant permission. Register app in SharePoint 1. Login into SharePoint and Navigate to register an app page. Use the URL mentioned below:          [Sitecollection URL]/_layouts/15/appregnew.aspx 2.  Once you navigate to the Register app page, a form will open. You need to fill all the fields on the form. Client Id and Client Secret  generated when we click on the generate button available next to the fields.  Title : Name of the add-in which you want to give. App Domain : Where your domain is hosted, for the local environment you can place             "www.localhost.com". Do not include HTTP or HTTPS...
    Post a Comment
    Read more

    SharePoint Framework SPFx Node Version Compatibility

    How to check the compatibility between the SPFx version and the Node.js version The SharePoint Framework (SPFx) is a client-side development platform used to develop web parts and extensions for SharePoint. The SharePoint Framework (SPFx) is compatible with the Node.js versions. Existing SPFx solutions may have different SPFx versions as compared to the current solutions. To make the SPFx solution run, Node.js is required, and in this blog, I am sharing steps to check the compatible node module for SPFx.  Find the SPFx version from the solution:  Open the project solution and navigate to the "package.json" file. In package.json file you will find  "@microsoft/sp-core-library" key and value of this particular key is the version of the SPFx.       Ex:    "@microsoft/sp-core-library": "1.14.0" Another way to find the SPFx version is by command, open the command prompt and run the command mentioned below: npm ls -g --depth=0 @microsoft/generator-s...
    Post a Comment
    Read more