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.

Sign up for GitHub

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

Jump to bottom

API routes error with bigint #7980

Closed
i-tengfei opened this issue Jul 15, 2019 · 3 comments · Fixed by #10215
Closed

API routes error with bigint #7980

i-tengfei opened this issue Jul 15, 2019 · 3 comments · Fixed by #10215
Labels
good first issue Easy to fix issues, good for newcomers

Comments

@i-tengfei
Copy link

API routes error with bigint.

SyntaxError: /sandbox/pages/api/test.js: Identifier directly after number (2:12)

https://codesandbox.io/s/hello-world-g2ero
@Timer
Copy link
Member

Timer commented Jul 15, 2019 •
edited
Loading

This is a Stage 3 JavaScript proposal -- meaning it's not part of the JavaScript language yet.

However, it seems odd that Node.js supports this feature since 10.4.
I guess we can enable the syntax parsing to be pass-through for API routes only.

@Timer Timer added this to the 9.0.x milestone Jul 15, 2019
@timneutkens timneutkens reopened this Aug 10, 2019
@timneutkens timneutkens added good first issue Easy to fix issues, good for newcomers help wanted labels Aug 10, 2019
@timneutkens timneutkens mentioned this issue Aug 11, 2019
Closed
@aselhid
Copy link

aselhid commented Aug 24, 2019

This is a Stage 3 JavaScript proposal -- meaning it's not part of the JavaScript language yet.

However, it seems odd that Node.js supports this feature since 10.4.
I guess we can enable the syntax parsing to be pass-through for API routes only.

just curious, any particular reason (beside it's only on stage 3) to only enable the syntax parsing for API routes only?

@Timer Timer modified the milestones: 9.1.x, 9.2.x Jan 3, 2020
@jamesmosier jamesmosier mentioned this issue Jan 22, 2020
Merged
Timer added a commit that referenced this issue Jan 27, 2020
@jamesmosier @Timer
Added support for BigInt to API routes (#10215)
c9dc17b 
* Added support for bigint to API routes

Closes #7980

* added BigInt test to get result

Co-authored-by: Joe Haddad <timer150@gmail.com>
@Timer Timer removed this from the 10.x.x milestone Nov 16, 2020
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
good first issue Easy to fix issues, good for newcomers
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added support for BigInt to API routes
5 participants
@Timer @i-tengfei @timneutkens @balazsorban44 @aselhid