There are multiple ways to debug what Boa is doing. Or maybe you just want to know how it works under the hood. Or even test some javaScript.
The first thing i usually do is add some JS here.
This file will be read if no arguments are provided. Then boa will begin to parse and execute that JS.
These are added in order of how the code is read:
The first thing boa will do is generate tokens from source code.
If the token generation is wrong the rest of the operation will be wrong, this is usually a good starting place.
Navigate to parser_expr in lib.rs and add dbg!(&tokens); just below tokens to see the array of token output. You code should look like this:
let mut lexer = Lexer::new(src);
lexer.lex().expect("lexing failed");
let tokens = lexer.tokens;
dbg!(&tokens);
...Seeing the order of tokens can be a big help to understanding what the parser is working with.
Assuming the tokens looks fine, the next step is to see the AST.
You can output the expressions in forward, add dbg!(&expr);
This will print out the entire parse tree.
Once the tree has been generated exec will begin to run through each expression. If the tokens and tree looks fine, you can start looking here.
I usually just add dbg!() in the relevent places to see what the output is at the time.
The quickest way to get debugging is to re-open the workspace in the container (using the Dockerfile provided). This is using the Remote Containers plugin. Once inside make sure you have the CodeLLDB extension installed and add breakpoints.
You can also use rust-lldb.
The Dockerfile already has this enabled, you should be able to use that environment to run your code.
rust-lldb ./target/debug/boa [arguments]