Power Platform Community Forum Thread Details

Before I go mad and spend any more time investigating how to resolve the error messages the Solution checker returns for a PCF component can I confirm that the following issues (1 high and 2 medium) are currently unavoidable:-

web-avoid-eval - recorded against line 98 of bundle.js and unavoidable as the component's source code is wrapped around an eval statement to ensure it doesn't break the rest of the site

web-use-strict-equality-operators - recorded against line 64 of bundle.js

web-use-strict-mode - recorded against line 2 of bundle.js

Categories:

Power Apps Pro Dev & ISV

Hey @ben-thompson,

Great question. Unfortunately, there are going to be scenarios where issues are flagged that cannot be avoided in the current version of Solution checker. For the future, we are evaluating ways to auto-exclude 3rd party well-known libraries, such as the one in question in your post. While there are probably ways in which you work around this, they are not going to be very elegant and likely cause more work than they are possibly worth. That's the not so great news. The better news is that we are working to roll out other mechanisms that will be out in public preview very soon (as in weeks, not months) in which you will be able to pass a list of files to exclude during analysis, which will allow avoidance of the situation that you currently find yourself facing. To specifically answer your question, if this was your code, we'd suggest making the recommended changes. If it is an open source library, then you could consider contributing back to the library changes, where it makes sense, otherwise, you should simply ignore these reported issues.

Please let me/us know if you have any other questions.

Thanks,

Mike Huguet

(Lead Engineer for Microsoft PowerApps Checker)