-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Including eslint-plugin-html
in a config for eslint 9 prevents non-html files from being processed
#262
Comments
BenoitZugmeyer
added a commit
that referenced
this issue
Apr 9, 2024
BenoitZugmeyer
added a commit
that referenced
this issue
Apr 9, 2024
Closed
BenoitZugmeyer
added a commit
that referenced
this issue
Apr 10, 2024
Thank you for the report! A fix has been released in v8.1.0 |
Confirmed it's working in my repo. Thank you for the fix and the amazing turnaround |
It also works with the // no need to import anything. The compat layers loads it via the name
// mimic CommonJS variables -- not needed if using CommonJS
const __filename = fileURLToPath(import.meta.url);
const __dirname = path.dirname(__filename);
const compat = new FlatCompat({
baseDirectory: __dirname,
recommendedConfig: pluginJs.configs.recommended,
});
export default [
...compat.plugins("html"),
]; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
A config for eslint 9.0.0 specifies rules for js files, and also loads eslint-plugin-html.
html files are linted. JS files are not.
Setup configuration
Expected:
Actual
NOTE WELL: the html plugin does not have to be loaded in the config in order to break linting, it just has to be imported into the config file
Aditional context
index.html
lintme.js
package.json
package-lock.json
The text was updated successfully, but these errors were encountered: