Skip to content

[Chrome] Start page example immediately failing #188

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
tristan-f-r opened this issue Jan 10, 2023 · 1 comment · Fixed by AssemblyScript/assemblyscript#2613
Closed

[Chrome] Start page example immediately failing #188

tristan-f-r opened this issue Jan 10, 2023 · 1 comment · Fixed by AssemblyScript/assemblyscript#2613
Labels
bug Something isn't working

Comments

@tristan-f-r
Copy link

tristan-f-r commented Jan 10, 2023

Environment

Latest website version at the time of issue writing, Chrome Version 108.0.5359.125 (Official Build) (64-bit).

I don't have the ability to replicate the issue at firefox as of now, so if anyone else can, please do so.

Reproduce

  • Go to https://www.assemblyscript.org/
  • Scroll down, and click the module.wat tab
  • Immediately get the following error:
    ;; INFO asc module.ts --textFile module.wat --outFile module.wasm --bindings raw -O3 --runtime stub
    ;; ERROR TS1012: Unexpected token.
    ;;    :
    ;;  4 │ if (n > 0) {
    ;;    │ ^
    ;;    └─ in module.ts(4,3)
    ;; 
    ;; FAILURE 1 parse error(s)
    (module
     ;; FAILURE 1 parse error(s)
    )
    

To fix the error, a semicolon is needed after b = 1.

@tristan-f-r tristan-f-r changed the title Start page example immediately failing [Chrome] Start page example immediately failing Jan 10, 2023
@dcodeIO dcodeIO added the bug Something isn't working label Jan 10, 2023
@dcodeIO
Copy link
Member

dcodeIO commented Jan 10, 2023

Relevant PR causing the issue: AssemblyScript/assemblyscript#2252

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants