I think we need to discuss option formats.

If we want to be more granular and configurable by the user, I suggest using an array of objects with elements and ordering, like this:

{'vue/block-attributes-order': ['error',
 [
 { element: 'script', order: ['setup, 'lang', 'src'] },
 { element: 'template', order: ['functional', 'lang', 'src'] },
 { element: 'style', order: ['scoped', 'module', 'lang', 'src'] },
 { element: 'i18n', order: ['global', 'locale', 'lang', 'src'] },
 ]
]}

You can use CSS selectors for the element property. This is similar to the vue/component-tags-order option.
The order option specifies the order of the attributes. It can use attribute names, regular expressions and their arrays, and negation. This is similar to the svelte/sort-attributes option.

If you want lang and src to always be at the back:

{'vue/block-attributes-order': ['error',
 [
 { element: '*', order: [['/.*/', '!/^(?:src|lang)$/'], 'lang', 'src'] }
 ]
]}

Patterns can be used to correct some order even for unknown blocks and unknown attributes.

What do you think?

Updated as comments.

I think you can inline the constants since they are only used here. I.e.:

 {
 element: 'style',
 order: ['module', 'scoped', 'lang', 'src']
 },

This rule is not yet released. Please remove this line and re-run npm run update.

I don't understand why there is an if and the same function call again otherwise. Could it not be simplified to this?

The test file name doesn't match the code/options here.

I think that unknown attributes should only be allowed at the end. This would simplify the rule logic and make some test cases obsolete.

Please add line and column of the reported error to all the expected errors in this file. However, you can also remove the type: 'VAttribute' everywhere.

Could you change it to accept more complex options by doing the following?

This change allows users to use pattern formats such as:

• "foo" ... Matches only the foo attribute name.
• "/foo/" ... Matches attribute names that match the /foo/ regex. That is, it matches the attribute name including foo.
• "!foo" ... Exclude foo attribute from the matched attribute names. When used first in the array or alone, matches other than the foo attribute name.
• "!/foo/" ... Excludes attributes that match the /foo/ regex from the matched attribute names. When used first in the array or alone, matches an attribute name that does not match the /foo/ regex.
• ["foo", "/^bar/u"] ... Matches the foo attribute or the attribute name that matches the /^bar/u regex.
• ["/^foo/u", "!foo-bar", "/^baz/u"] ... Matches an attribute name that matches /^foo/u and other than foo-bar, or an attribute name that matches /^baz/u.

I think the rule of other plugin will also be helpful.
https://ota-meshi.github.io/eslint-plugin-svelte/rules/sort-attributes/

Could you please define the schema so that at least one item is set?

Could you define the schema so that the two properties are required?

After changing it to accept complex ordering, could you change it so that lang and src are always ordered last?

e.g.

Change other elements in the same way.

Could you add the following item to force the order of the custom elements as well?

 {
 element: '*',
 order: [
 ["!lang", "!src"],
 "lang",
 "src"
 ]
 },