[BUG] plugin/parser 0.46.0 results in TypeError: Cannot read properties of undefined (reading 'rules')

[adamlui]

Describe the bug

@html-eslint/<eslint-plugin|parser> 0.46.0 causes ESLint 9.34.0 to produce TypeError: Cannot read properties of undefined (reading 'rules')

To Reproduce

1. bump @html-eslint/<eslint-plugin|parser> and ESLint to the latest vers
2. try to lint

Expected behavior
lints

Additional context
All my repos run ESLint 9.34.0 no problem but this PR mins ago https://github.com/adamlui/chatgpt-auto-continue/pull/122/files included your plugin in the bumps, the nthis error started happening

Same thing happened to this repo because your plugin got bumped: https://github.com/KudoAI/kudoai.com/pull/194/files

[yeonjuan]

Hi @adamlui Would you like to try changing it like this?

AS-IS

   { // eslint.config.mjs
        files: ['**/*.html'], languageOptions: { parser: htmlParser }, plugins: { '@html-eslint': html },
        rules: {
            ...html.configs['flat/recommended'].rules,
            '@html-eslint/require-title': 'off', // allow missing title tags
            '@html-eslint/quotes': 'off', // allow unquoted attrs for compactness
            '@html-eslint/attrs-newline': 'off', // allow multi-attrs in single line
            '@html-eslint/require-img-alt': 'off', // allow img tags w/o alt attributes
            '@html-eslint/indent': 'off', '@html-eslint/element-newline': 'off' // allow whitespace anywhere
        }
    },

TO-BE

   { // eslint.config.mjs
        files: ['**/*.html'], languageOptions: { parser: htmlParser }, plugins: { html },
        rules: {
            ...html.configs.recommended.rules,
            'html/require-title': 'off', // allow missing title tags
            'html/quotes': 'off', // allow unquoted attrs for compactness
            'htmlattrs-newline': 'off', // allow multi-attrs in single line
            'html/require-img-alt': 'off', // allow img tags w/o alt attributes
            'html/indent': 'off', '@html-eslint/element-newline': 'off' // allow whitespace anywhere
        }
    },

[adamlui]

Ok I have to update dev deps again and it takes like half hour but in the meantime how did you get me to involuntarily assign you this Issue?

[adamlui]

Also this is a breaking change so the Major (0) shoulda been bumped to 1 because that number's for breaking changes (I have to now fix config for almost 40 repos, and I can't even do it all at once now because dependabot is rollikng it out slowly :( so very inconvenient to have to one by one as the patches hit make the changes

[adamlui]

https://stackoverflow.com/questions/71813328/is-a-small-breaking-change-enough-to-do-a-major-version-upgrade-while-using-semv

[adamlui]

I mean by using Major, then it discourages you from breaking too much (falsely inflates perceived progression) also I woulda declined the dependabot bump until all of them accumulated so I can mass edit configs, instead it also cost considerable time to reverse before your solution

[adamlui]

I applied your suggested change but all the exceptions become ignored now:

[adamlui]

NVM there was a trailing - all is well now

[yeonjuan]

Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.
https://semver.org/#spec-item-4

@adamlui I apologize for the inconvenience. Since this is a 0.x version, breaking changes may occur even with minor version bumps. That’s why I thought it was not necessary to update to a major version like 1.0.
However, I agree that this can cause inconvenience. This project has already gone through quite a number of releases, and I think it’s time to consider moving to version 1.x. it would be better to switch to version 1.0 and then increment the major version for any future breaking changes.