Skip to content
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

fix(parser): throw error with wrong typescript 'export declare' #12684

Merged

Conversation

fedeci
Copy link
Member

@fedeci fedeci commented Jan 23, 2021

Q                       A
Fixed Issues? Fixes #12658
Patch: Bug Fix? Yes
Major: Breaking Change?
Minor: New Feature?
Tests Added + Pass? Yes
Documentation PR Link
Any Dependency Changes?
License MIT

We check if after the first declare there is an exportable value.

@babel-bot
Copy link
Collaborator

babel-bot commented Jan 23, 2021

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/38377/

@codesandbox-ci
Copy link

codesandbox-ci bot commented Jan 23, 2021

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 1cb13af:

Sandbox Source
babel-repl-custom-plugin Configuration
babel-plugin-multi-config Configuration

@nicolo-ribaudo nicolo-ribaudo added area: typescript pkg: parser PR: Bug Fix 🐛 A type of pull request used for our changelog categories labels Jan 23, 2021
isDeclare &&
(this.isContextual("declare") || !this.shouldParseExportDeclaration())
) {
throw this.raise(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we not throw here to make it recoverable?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about how we could recover. What should the AST for export declare foo be?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, you're right. Let's stick with throwing!

Copy link
Member

@nicolo-ribaudo nicolo-ribaudo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving, pending a reply from @existentialism to #12684 (comment) (if we can easily recover we should do it).

@existentialism existentialism merged commit fbfd1b2 into babel:main Jan 27, 2021
@fedeci fedeci deleted the fix-parser-typescript-export-declare branch January 27, 2021 06:11
@github-actions github-actions bot added the outdated A closed issue/PR that is archived due to age. Recommended to make a new issue label Apr 29, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: typescript outdated A closed issue/PR that is archived due to age. Recommended to make a new issue pkg: parser PR: Bug Fix 🐛 A type of pull request used for our changelog categories
Projects
None yet
Development

Successfully merging this pull request may close these issues.

No syntax error is thrown for non-declaration following TypeScript export declare
5 participants