Parsing error when default export involves Array.concat
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.1k
- Forks
- 773
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce
// okay
export default [...foo, ...bar]
// not okay
export default [].concat(foo)
^
The bottom example is how the Buble compiler transforms something like [...foo].
Expected output
Successful parse for the bottom example.
Actual output
Error: Line 5: Unexpected token .
Relevant references
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported examples in Esprima and compare the accepted array-spread export with the rejected [].concat(foo) default export. Trace the parser entry point for default-export expressions; done means the bottom example parses successfully without regressing the existing successful case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100