Announcements
Please use this thread to discuss feedback/suggestions/concerns on the ESLint rules for Power Apps.
How to try this feature?
Thank you for publishing theses rules!It would be great to get a base/recommended configuration to extend from similar to other eslint plugins.This would make it easier to keep up to date with the latest rules added - e.g.
"extends": [ ... "plugin:microsoft/power-apps/recommended", ],
This is great. If you want to implement this, but have multiple warnings that might take a while to fix take a look at the --max-warnings flag in EsLint when including EsLint in a DevOps pipeline/github workflow.
This allows a code base to be gradually improved in a similar way to warnings thresholds with the solution checker.
https://eslint.org/docs/latest/user-guide/command-line-interface#--max-warnings
npx eslint --max-warnings 10 file.js
or for the current directory and below
npx eslint --max-warnings 10 .
Great suggestion, Scott! We've added this to our backlog and will enhance the documentation once we've shipped the configurations.
I love this ESLINT rules as they give new devs insight into what is not supported. And they keep more experience devs apprised of issues they may not have previously noticed. This has been my first experience with ESLINT rules as a whole. These are wonderful! However, it is quite possible that I am doing something wrong. I have a js library that I have been modifying to remove all the unsupported Dynamics 365 code. I realized a while into editing it that it has stopped underlining the Dynamics 365 problems. It continues to underline any of the default/OOTB rules I have set up from ESLINT. This happens the same in both VS2022 and VSCode. I started copying and pasting the functions from the original from the modified version of the code to narrow down the issue. When I fix the last line containing Xrm.Page the problems listed ALL disappear. Including things that are still issues like the usage of $() and DOM manipulation 😬. Things I definitely know are unsupported and should be removed from the code base.Are there any thoughts as to what might be the issue? My workaround for the moment is to leave that line until the last. This is not only happening on this file but others.
Is there a github site for this package yet?
I'm not aware of one. It would be nice to see. It looks like the source code can be seen after installation of the module in node_modules\@microsoft\eslint-plugin-power-apps.
I thought it would be a minimum collab requirement at this stage especially for logging issues and requests!
I've sent you a private message David so that we can look into it together.
Moving to GitHub is in our long term roadmap, but we do not have an ETA for this yet. It will be great to work with the community on rule collaboration and issues!
cc @sidg
As discussed offline, we've released a fix for this. The current rule only flags violations if a call to Mscrm or Xrm is present. As a non-breaking change, we've released version 0.2.8 of the ESLint rules on NPM which add a requireXrm option to a few rules which have this behavior. Setting this option to false will flag all violations regardless of Mscrm or Xrm usage.
See updated docs:avoid-dom-form Power Apps checker reference - Power Apps | Microsoft Learn
avoid-dom-form-event Power Apps checker reference - Power Apps | Microsoft Learn
use-utility-dialogs Power Apps checker reference - Power Apps | Microsoft Learn
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
WarrenBelz 525 Most Valuable Professional
Haque 308
Kalathiya 234 Super User 2026 Season 1
