Skip to content

Refactor: drop es5-ext #473

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

SukkaW
Copy link

@SukkaW SukkaW commented Aug 10, 2025

es5-ext was introduced to WebSocket-Node in 2019 by #362 to address #360. However:

The PR removes es5-ext, and instead uses the globalThis polyfill implementation from core-js.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @SukkaW, I'm Gemini Code Assist1! 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!

I've refactored the WebSocket-Node library to remove the es5-ext dependency, which was causing unnecessary bloat and not effectively solving its intended problem. My changes replace the es5-ext-based globalThis polyfill with a more lightweight and effective solution derived from core-js. This significantly reduces the library's footprint and improves its overall efficiency, especially for browser-based usage.

Highlights

  • Dependency Removal: I have removed the es5-ext package from the project's dependencies. This package was identified as a significant contributor to the node_modules size (adding 643 KiB) and was not effectively addressing the webpack bundling issues it was intended to solve.
  • Global Object Polyfill Refactor: The globalThis polyfill logic in lib/browser.js has been updated. Instead of relying on es5-ext/global, I've implemented a custom, more efficient, and robust polyfill strategy inspired by core-js. This ensures proper global object detection across various environments without the overhead of the es5-ext dependency.
  • Performance and Efficiency Improvement: These changes lead to a lighter and more efficient library. By removing a heavy and problematic dependency and replacing its functionality with a streamlined solution, the overall footprint of the WebSocket-Node library is reduced, which is particularly beneficial for browser environments.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request successfully refactors the project to remove the es5-ext dependency, addressing a known bundling issue. The dependency is replaced by a lightweight, self-contained globalThis polyfill adapted from core-js, which is a great improvement for reducing the package size and complexity. The changes are clean and focused. My feedback includes a minor suggestion to improve code consistency in the new polyfill.

@SukkaW
Copy link
Author

SukkaW commented Aug 11, 2025

cc @theturtle32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant