calls to tslib __setFunctionName fail on Cobalt 9 about tslib HOT 5 OPEN

It'd be an issue in both; this library is just the same helpers that TS emits but pulled out for common reuse.

@rbuckton

from tslib.

Looking closer at the error in question, it seems like it's trying to set the name property of HTMLScriptElement. Can you provide an example of the emit where this error is produced? If this is somehow a reference to the existing DOM HTMLScriptElement constructor, there's no reason we should be setting a name for it, so it would be helpful to see how things got into that state.

from tslib.

In a TS file, we have:

function foo() {
  const clazz = class {static bar = true;}
}

The output I get from tsc is:

function foo() {
    var _a;
    const clazz = (_a = class {
        },
        __setFunctionName(_a, "clazz"),
        _a.bar = true,
        _a);
}

I think this snippet should fail on Cobalt 9 (it emits the problematic __setFunctionName call), but I haven't tried it.

from tslib.

Per my comment earlier, I'm not sure the issue is __setFunctionName specifically, but how it is somehow being applied to an HTMLScriptElement per the TypeError in the issue description. Somehow __setFunctionName is being applied to the wrong thing in your project.

from tslib.

We can no longer reproduce this failure. Please feel free to close the issue.

from tslib.