Explicit package exports in the latest version of Fluent UI might break your PCF path imports
If you are using Fluent UI in your code components (PCF) you probably are also using path-based imports to reduce your bundle size. This technique ensures that when you build your code component, the bundle doesn’t include the entire Fluent UI library, but instead just the components that you need. With the recent update to Fluent UI, you might receive an error similar to the…
Continue Reading Develop1’s Article on their blog
Explicit package exports in the latest version of Fluent UI might break your PCF path imports
If you are using Fluent UI in your code components (PCF) you probably are also using path-based imports to reduce your bundle size. This technique ensures that when you build your code component, the bundle doesn’t include the entire Fluent UI library, but instead just the components that you need.
Blog Syndicated with Develop1’s Permission
More About This Author
Array
- YouTube5 March 2024Let’s ask AI some simple questions! #copilotstudio #copilot #ai #powerplatform #responsibleai – YouTube
- YouTube5 March 2024✨Dynamic Chaining in #CopilotStudio | 🎟️ Win EPPC tickets 🎉 – YouTube
- YouTube11 January 2024Chat with external systems using plugin actions (preview) in Copilot Studio 😎 – YouTube
- YouTube19 October 2023Why I’m joining Microsoft as a Cloud Developer Advocate 🚀 – YouTube