Contents
Why does SPFX component all gulp commands failed?
Error: #/ (Defines configuration options for the…) From the error, it seems that there are issues with all the Microsoft modules. We were wondering why it started breaking after updating the modules/packages. We verified the version of all our Microsoft packages package.json file which is now 1.6.0.
Important point to remember is delete the respective file from config folder of our SPFX component, if we have files at both the places then on build lots of hidden file for each component are get added which ultimately creates the problem while committing the changes. Unfortunately, I couldn’t find more documentation on this.
The isolated web parts capability is available only in SharePoint Framework v1.8 and later. Solutions using the isolated web parts capability, have a specific flag set in the project metadata in the *.sppkg file.
What is the problem with TSLint error in SPFX?
Error – JSON validation failed. WebParts\\config slint.json Today new issue and solution in this article I’ll explain the tslint error while building SPFX component (Either web part or extension) and then how we resolved it. Background: We are working on one of the O365 Intranet application. We are developing few SPFX webparts and extensions.
Why is not a single gulp command working?
This seems to be a weird issue since not a single gulp command (gulp clean, gulp build, or gulp serve) is working and we couldn’t deploy our components. It also broke the working of the local workbench.
What is version of Microsoft packages in Gulp?
We verified the version of all our Microsoft packages package.json file which is now 1.6.0. Previously, it was 1.5.1, as shown in below figure as well, This seems to be a weird issue since not a single gulp command (gulp clean, gulp build, or gulp serve) is working and we couldn’t deploy our components.