Skip to content

Support export * as my_variable_name #498

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
torch2424 opened this issue Feb 21, 2019 · 4 comments
Closed

Support export * as my_variable_name #498

torch2424 opened this issue Feb 21, 2019 · 4 comments

Comments

@torch2424
Copy link
Contributor

relates to #27

The issue above is fixed, but we still get errors for export * as...

screen shot 2019-02-20 at 9 52 00 pm

@torch2424
Copy link
Contributor Author

cc @dcodeIO Found some feedback from creating #499

@dcodeIO
Copy link
Member

dcodeIO commented Feb 21, 2019

Is export * as ... valid TypeScript actually? Whenever I enter that into vscode, it becomes all red, leaving me with the assumption that the intended use here is import * as foo from "./bar"; export { foo };. (but I wondered about that myself)

Other than that, if it isn't valid TS, it might be possible to support it nonetheless if there's interest.

@torch2424
Copy link
Contributor Author

@dcodeIO You know what, you may be right, maybe I dreamt it that it was valid syntax. 😂 Feel free to close if it is not.

@torch2424
Copy link
Contributor Author

Oh wait yup, it's only a proposal: https://github.com/tc39/proposal-export-ns-from

And can be achieved with: https://stackoverflow.com/questions/42728140/is-it-possible-to-export-as-foo-in-typescript

I'll go ahead and close this, thanks for catching that! 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants