Cannot 'export default' abstract, ambient class or interface

[zhuravlikjb]

export default abstract class B {

}

By the way, the same with

export default declare class B {

}

Seems to be a parser bug

[DanielRosenwasser]

In what situations would one need to make an ambient class a default export?

[mhegazy]

These two are by desing. We have felt that the export default syntax is already long enough, so no modifiers are needed. for a workaround use:

declare class  C {}
export default C;

[danquirk]

We should just allow these. It's a strange inconsistency, the workaround is more verbose, and the error gives you no help getting to the workaround.

[DanielRosenwasser]

Yeah, discussed with @danquirk and @RyanCavanaugh offline; in a .d.ts file, a default exported ambient class makes sense.

I don't think it's that unreasonable to support the original syntax.

[mhegazy]

should also cover interfaces (#3914):

export default interface User {
    wpUserID: string;
}

[RyanCavanaugh]

And namespaces: export default namespace foo { ... } (#7407)

[RyanCavanaugh]

Accepting PRs for this.

[DanielRosenwasser]

Does this mean a namespace can be anonymous?

export default namespace {
    export var foo = 100;
}

What about an interface?

export default interface {
    foo: number;
}

[RyanCavanaugh]

No other changes except for allowing the export default ... ... modifier combinations that were previously illegal.

[seanchas116]

I would prefer support for export default enum and export default const enum too. (#3320)

[clavecoder]

I'm OK with leaving it as is if the reasoning is that interfaces, et al, are not vaid EcmaScript and #3917 is implemented.

[mhegazy]

Unsupported export default patterns:

• export default abstract class C { } Added by Allow export default abstract class. Related to issue 3792. #14657
• export default declare class C { }
• export default interface I { } Added by Allow export default interface. Related to issue 3792. #16040
• export default enum E { }
• export default const enum E { }
• export default namespace N { }
• export default type T = { }

[anstarovoyt]

@mhegazy what about export default type foo = {} ?

[simonbuchan]

@mhegazy for full symmetry with JS export forms, consider (strawman syntax) export default as ...:

JS	TS
export const x = 123	export type T = number
export { x }	export { T }
export class Foo {}	export interface Foo {}
export default class Foo {}	export default interface Foo {}
export default 123	export default as number

[mhegazy]

not sure what that means..

export default as number

but if it is a .d.ts, we chose not to have a special syntax for this, and the recommendation here is to use

declare cosnt _t: number;
export default _t;

[simonbuchan]

Yeah, sorry, it is a bit ambiguous. Currently, you can sort of export a type as default with:

type T = number;
export default T;

By analogy of const ~= type:

export const x = 123;
export type T = number;
export default x;
export default T;
export default 123;
export default ???; // can't put type expressions here, only type names, due to ambiguity

The motivating case would would be something like:

// Action.ts
export default as
  | { type: 'login', name: string, password: string }
  | { type: 'logout' }
  | ...

where currently you would need to bury the export at the bottom of the file.

I picked export default as <type> as strawman simply because as already suggests a type on RHS, but it doesn't really imply the right thing, you're right. Perhaps export type default <type>?

[alvis]

Really look forward to #18628! Thanks @NaridaL. 👏👏 👏

[ghost]

Found this when trying export default enum. Is this really not implemented yet? (6 years)