Library component not working?

[JakeStanger]

Category

• Question
• Typo
• Bug
• Additional article idea

I'm not sure whether to put this down to lack of clarity in the documentation or a bug, but I've created and deployed a library component and...nothing seems to happen.

Here's what I've done:

• Create a library component
• Create a webpart
• Add the library to the webpart dependencies, and link the library to the webpart
• Build the library and deploy it tenant-wide
• Build the webpart and deploy it, and add it to a page
• Check the page requests, and notice there is no request sent to the component JS file (only to the webpart)
• Make test changes to the library and redeploy the library as a sanity check
• Re-test the app and notice the same results as before

Perhaps I am missing a step? My understanding is that deploying a library performs some magic which tells the webpart bundle to load the dependency from elsewhere, although this doesn't seem to be the case.

Sorry I haven't provided an awful lot of detail, I'm not really sure where to be looking. Any assistance on the matter is greatly appreciated.

[msft-github-bot]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[PopWarner]

@JakeStanger happy to help. A couple of questions:

1. Did the library component and web part work in development before you deployed to the app catalog? Meaning did it work from your local dev environment on your dev machine?

2. Do you happen to have a repo of the library component and web part available to look at the code?

Thanks in advance! :)

[JakeStanger]

1. Yes it works in development, but the library is installed using yarn link so it's not really a proper test.
2. Unfortunately it's all closed source so I can't really get any good examples. I can attempt to recreate the project if needed when I have more time.

It's just occurred to me that while the library is linked to the web part on my computer, the deployed version is built through CI where the library is "properly installed" from our NPM repo using yarn add.
I need to test it but is it likely/known if the build process relies specifically on the presence of a symlink i.e only works with linked packages rather than installed packages? This would make sense to me, unless the server is actually supposed to take apart and analyze the package?

Thanks for the help.

[PopWarner]

I'm not entirely sure on that as I'm not as experienced in the yarn tooling.

That being said though, I would be curious to see if just following the default tutorial results in success for you?
https://docs.microsoft.com/en-us/sharepoint/dev/spfx/library-component-tutorial

Feel free to reply back when you are able to possibly create another version and if you still don't find success and can share that version, I'm happy to help take a look. :)

[AJIXuMuK]

Sorry for the long delay.

Library components are definitely working by now.
Feel free to open a new issue if you experience any problems with library component, or any other types of SPFx solutions.

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues