You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tsickle currently correctly emits the first file, but leaves out the second module file. The second file is needed so that users that import this d.ts can refer to module.name.B in type annotations.
If there are any values inside the module, tsickle should just drop them for now, because there's no way to alias a value in a module.
questions
Do we need to create an alias for each export? Or will something like exports = mangled$name; be sufficient? Will likely need an experiment.
The text was updated successfully, but these errors were encountered:
Another question: how do we handle .d.ts files that declare values, not
just types? Currently we don't generate anything and expect the user to
supply a shim.
When given a module d.ts file, e.g.
tsickle needs to emit two files:
tsickle currently correctly emits the first file, but leaves out the second module file. The second file is needed so that users that import this d.ts can refer to
module.name.B
in type annotations.If there are any values inside the module, tsickle should just drop them for now, because there's no way to alias a value in a module.
questions
Do we need to create an alias for each export? Or will something like
exports = mangled$name;
be sufficient? Will likely need an experiment.The text was updated successfully, but these errors were encountered: