At some point, over the last few months, a change was introduced to the Power Platform CLI such that if you have the ESLint VS Code add-in installed, after using pac pcf init, you may see an error in VS code:
'ComponentFramework' is not defined.eslint(no-undef)
This might look something like this in the index.ts file:
The reason for this is that the pac pcf init template now includes an…
Continue Reading Develop1’s Article on their blog
‘ComponentFramework’ is not defined – eslint with pac pcf init
At some point, over the last few months, a change was introduced to the Power Platform CLI such that if you have the ESLint VS Code add-in installed, after using pac pcf init, you may see an error in VS code: ‘ComponentFramework’ is not defined.eslint(no-undef) This might look something like this in the index.ts file: The reason for this is that the pac pcf init template now includes an .
Blog Syndicated with Develop1’s Permission
More About This Author
Array
YouTube3 April 2024EPPC 2-day conference ticket winner! – YouTube
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
