Today we are making available an updated version of PCF tooling and are excited to announce that this new version is offering support for React bundling as well as a number of other enhancements like:
React is no longer treated as an external library. Now tooling can bundle it directly with the custom component source code.
Relatives paths used in the manifest are now preserved when generating the control output folder as part of build. For example, if a resource file is located in a ‘…control folder\css\subfolder’, the subfolder will be created in the output folder during build with all relative paths preserved.
In preparation for future library sharing capabilities, we are removing the need for library definition in the ControlManifest.Input.xml. This will impact previously created components using the library tag (please remove all libraries from the ControlManifest.Input.xml and replace them with an import statement in the index.ts).
Added ability to include a preview image for the control by using the “preview-image” attribute in manifest’s <control> node.
Added an optional msbuild argument ‘/sourceLoc’ to enable localization during solution packaging.
Updated MSI registry path to: Software\Microsoft\PowerApps CLI\Installed
Updated help descriptions
Please make sure to update your Microsoft PowerApps CLI to the latest version and take advantage of all the latest capabilities by following the upgrade instructions.
If you have any questions please don’t hesitate to respond to this post.