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
Dyn365CE2021.12.01Watch out for PCF (code-components) sort silently failing
YouTube2021.11.16First look at Quick ‘n’ Easy Power BI inside Power Apps – YouTube
Dyn365CE2021.11.09'ComponentFramework' is not defined – eslint with pac pcf init- Dyn365CE2021.11.08Modernized Business Units – perhaps finishing off something that was always meant to be!
