Adding Application Customizer to existing Web Part Project causes web parts to not be deployed #3219
Expected or Desired Behavior
This issue occurs when adding an application customizer using yo to an existing SPFx project that has a web part in it. When you add the application customizer, the Web Parts are no longer deployed.
After the application customizer is added to the project, the Web Part is no longer deployed (the application customizer is deployed).
Steps to Reproduce
My repo below shows the issue.
This is caused by the fact that web parts do not require a feature entry in package-solution.json. When you add an application customizer, it creates a feature entry and then the web parts are not deployed. In this case, when you run yo to add the application customizer, it should add the component ids of any existing web part to the feature.
Warnings should also be provided to users as to avoid having multiple features which causes issues with the wrong version of code being loaded as shown in issue #3199.
The text was updated successfully, but these errors were encountered:
I'll answer on the question... the sample which @coreyroth provided is not using tenant scoped deployment (aka skip feature activation) and therefore requires a solution to be installed on a site. Basically, a developer is looking to deploy two web parts and one application extension to a single site. That should work and we'll absolutely need to have a look at this.
WaybackMachine is your friend here:
presses CTRL+A, CTRL+C and CTRL+V