What is the limit to create SPFx webpart in single SPFx solution?
What kind of challenges have you faced in SPFx Project?
Please share your project experience.
Loading
2 Replies
Know the answer? Post it — somebody with the same question will find it here.
Sign in to answer this question
It is the same account you read, post and publish with — and you will come straight back to this page.
What is the limit to create SPFx webpart in single SPFx solution?
Answer: Can you please let me know what exactly you are looking for. Certainly there are certain challenges and limitations with SPFX. As it is client side code so there may be some security issue.
But It’s evolving at high speed so we are getting lot of technical stuffs day by day.
What kind of challenges have you faced in SPFx Project?
Please share your project experience.
Answer: Once we moved out from Server
side development, we were having very less options to add coding part. With
SPFx , office fabric, react development make development interesting and
exiting. Personally I enjoy using SPFx.
You can also try and you will like it,
Love ThakkerPosted Sep 30, 2020, 1:48 AM
Answer - There is no limit given by the Microsoft. Even I have a solution where I have added 12 webparts in single solution. Initially I though it is good thing if we have everything in one place. But the solution is getting heavy everytime we add something to that. It is taking long time to build, we have issues of loading multiple packages which we don't recognize and not sure it is required or not now. And we can't take them off now as we are not sure which webpart will be affected by that. So If possible keep them separate, so you can maintain them easily.
Answer - As I explain earlier, it is hard to decide the architecture of solution with SPFx. That is a common pain that I face whether to go with single solution or have separate solution for each webpart.
Other than that is the npm packages that we include. We are not sure what is written in that and that can harm you. In one of my project we got a mail from Npm that mentioned that we used a package which was tracking all the payment transaction done on client browser. Npm then removed that package and that broke the functionality. So you make sure do not load your solution with any unnecessary packages.
As Vikas mentioned, the SPFx is evolving everyday. It is throwing new versions of node. But manytimes its not easy to migrate your old solution to new one. As well the new package has its own bugs that are unknown until you raise queries in the git community.
Again with opening the SPFx to new environment like Teams you need to make sure you are not giving any permission that user's should not have. Recently Microsoft provide new graph permission that helps you to restrict things for teams management. But before that this was major issue.
If you are only concern with Webpart, these are most concern. But there are few things that I face with Extensions as well like implementng them in responsive manner and applying them in Hub - associate structure.