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

[Web] Fix closure compiler builds using BIGINT #83720

Merged
merged 1 commit into from
Oct 21, 2023

Conversation

Faless
Copy link
Collaborator

@Faless Faless commented Oct 21, 2023

When using proxy_to_pthread we add BIGINT support (to support exchanging 64 bits integers between wasm and JS).

Bigint though, is part of ECMAScript 2020, and the closure compiler was using ECMAScript 6 instead.

This commit update the CC configuration to use ECMAScript 2020 instead.

Follow up on #79711

Bugsquad edit:

When using proxy_to_pthread we add BIGINT support (to support exchanging
64 bits integers between wasm and JS).

Bigint though, is part of ECMAScript 2020, and the closure compiler was
using ECMAScript 6 instead.

This commit update the CC configuration to use ECMAScript 2020 instead.
@akien-mga akien-mga merged commit 7d69516 into godotengine:master Oct 21, 2023
15 checks passed
@akien-mga
Copy link
Member

Thanks!

@Faless Faless deleted the web/fix_ecmascript_bigint branch October 21, 2023 16:19
@akien-mga akien-mga added the cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release label Mar 9, 2024
@akien-mga
Copy link
Member

Cherry-picked for 4.1.4.

@akien-mga akien-mga removed the cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release label Mar 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Closure compiler build error for Web platform in current dev branch
2 participants