refactor: replace esprima with acorn

[hyperz111]

esprima is unmaintained, so i replace it with acorn which is an up-to-date JavaScript parser.

[gemini-code-assist]

Summary of Changes

Hello @hyperz111, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request modernizes the project's JavaScript parsing infrastructure by swapping out an outdated and unmaintained dependency for a current and actively supported one. This change improves the project's long-term maintainability and ensures compatibility with modern JavaScript syntax, enhancing the robustness of code analysis and execution features.

Highlights

• Dependency Update: The unmaintained esprima JavaScript parser has been replaced with acorn, an actively developed and up-to-date alternative.
• Parsing Logic Refactor: The code responsible for parsing JavaScript functions and execution snippets in src/lib/console.js has been updated to utilize acorn's parsing capabilities, including configuration for the latest ECMAScript version.
• AST Node Property Access: Adjustments were made to how Abstract Syntax Tree (AST) node properties are accessed, specifically transitioning from range (an array) to start and end properties, aligning with acorn's AST structure.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request successfully replaces the unmaintained esprima JavaScript parser with acorn. The changes are correctly implemented across the package configuration and the console logic in src/lib/console.js. The code is properly adapted to acorn's API, ensuring the console's parsing functionality remains intact while moving to a modern, maintained dependency. This is a great maintenance improvement.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR successfully migrates from the unmaintained esprima parser to the actively maintained acorn parser. The migration is straightforward and maintains full compatibility with the existing code.

Key Changes:

• Replaced esprima dependency with acorn (v8.15.0) in package.json
• Updated import from import * as esprima from "esprima" to import { parse } from "acorn"
• Added acornOptions configuration with ecmaVersion: "latest"
• Replaced node.range[0]/node.range[1] array access with node.start/node.end properties (src/lib/console.js:654)
• Removed the range: true option (no longer needed as acorn provides start/end by default)

Why This Works:
Both parsers follow the ESTree specification, so the AST structure is identical for all properties used in the code (type, params, id, name, expression, kind). The only difference is how position information is exposed: esprima uses an optional range array while acorn always provides start and end properties directly on nodes.

Confidence Score: 5/5

• This PR is safe to merge - it's a well-executed dependency migration with no breaking changes
• Perfect score given because: (1) both parsers follow ESTree spec ensuring AST compatibility, (2) the only API change (range array to start/end properties) was correctly updated, (3) acorn provides start/end by default making the code simpler, (4) all existing functionality is preserved, and (5) acorn is actively maintained unlike esprima
• No files require special attention - all changes are correct

Important Files Changed

Filename	Overview
package.json	Replaced unmaintained esprima with actively maintained acorn parser
src/lib/console.js	Migrated from esprima to acorn API, replacing range array with start/end properties

Sequence Diagram

sequenceDiagram
    participant User
    participant Console
    participant Parser as Acorn Parser
    participant Executor
    
    User->>Console: Input code in console
    Console->>Console: onCodeInput()
    Console->>Parser: parse(code, acornOptions)
    Parser-->>Console: AST with start/end properties
    Console->>Executor: execute(code)
    Executor->>Executor: execParsedCode(parsed.body)
    
    alt Variable Declaration (const/let)
        Executor->>Executor: Extract code substring(st.start, st.end)
        Executor->>Executor: Inject script into DOM
    end
    
    Executor->>Executor: window.eval(code)
    Executor-->>Console: Result or Error
    Console->>User: Display output
    
    Note over Console,Parser: parseFunction() also uses acorn
    User->>Console: Inspect function object
    Console->>Parser: parse(functionString, acornOptions)
    Parser-->>Console: AST with function params
    Console->>Console: Extract parameters and format
    Console->>User: Display formatted function signature

Loading

[UnschooledGamer]

many parsers in one project haha, babel parser, now Acorn

[hyperz111]

many parsers in one project haha, babel parser, now Acorn

Wait Babel? I don't see that 😅

[hyperz111]

@UnschooledGamer, maybe this is good?

[UnschooledGamer]

@UnschooledGamer, maybe this is good?

Seemingly to be

[UnschooledGamer]

Noting the https://github.com/acornjs/acorn/tree/master/acorn-loose/ here, in case we need it in the future