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
Dyn365CE2022.05.02React 18 is not compatible with Fluent UI and how to work around it in PCF projects
YouTube2022.04.08Virtual React PCF code components – create new, and convert existing ones! – YouTube
Dyn365CE2022.04.07How to convert a pcf code component to a virtual control
YouTube2022.03.12Custom Pages? So What?!!! – YouTube
