There are several occasions (I am not sure about the exact condition) where the developer tools complains about an export statement already existing when trying to apply a generic handler to an element event.
For example, I have a series of input elements each decorated with an edit icon which is hidden when clicked and revealed when no changes are applied. Each of the edit icons do exactly the same thing so I want to make the onClick element event the same for each element.
Sometimes if I retroactively add or update an existing element to utilize a pre-existing function to handle an event I get the error:
Error: An export statement with the given name: valueChanged already exists.
at h (built-codeEdit.min.js:28)
at Object.p [as addExport] (built-codeEdit.min.js:28)
at pageActions.js:60
At best this should be a Warning and not an Error. The error condition prevents me from attaching the handler and I end up having to remove the element and create a new one from scratch to circumvent the problem!
Feature Request: Change this from being an Error to being a Warning and hook up the existing external function (cos that is what I want to do!) 