Throwing errors vs console.warn

[quantizor]

For situations like min=0 max=0 where the values match, I agree there should be some sort of dev-time feedback, but throwing an error seems very extreme and breaks the entire page when there might be some async adjustment happening which just hasn't been applied yet.

Can usages of RangeError be replaced with console.warn or console.error to be friendlier to the development process?