perf: save 0.2kB bundle size by const-ing error message

[bartveneman]

Not sure if this is something you'd want to merge, feel free to skip, but I was profiling some perf issues at Wallace's bundle sizes and noticed this error string recurring 3 times.

before

index.cjs 50619
index.js  50478

after

index.cjs 50437 (-182B)
index.js  50296 (-182B)

It now throws a NotAllowedError with the message Manipulating a Specificity instance is not allowed. Instead, create a new Specificity()

[bramus]

Thanks for the PR. Nice handy addition.

Looking at the error message itself: I’ve got no clue what went on in my mind when I wrote “Manipulating the port of the specificity directly is not allowed. Instead, directly set a new value”.

• The port? Maybe I meant part?
• The “Instead, directly set a new value” part makes no sense at all as it contradicts the first

While at it, it might also be a good idea to change Error to a NotAllowedError.

[bartveneman]

I agree on both points, the error message didn't really make sense to me 😆

Btw, I hope the tests are ok, it's a bit repetitive, but at least there's some coverage now.

[bartveneman]

Updated:

before

index.cjs 50619
index.js  50478

after

index.cjs 50437 (-182B)
index.js  50296 (-182B)

It now throws a NotAllowedError: Manipulating a Specificity instance is not allowed. Instead, create a new Specificity()