Skip to content

Conversation

@dasoncheng
Copy link
Contributor

@dasoncheng dasoncheng commented May 24, 2025

…browser environment

Description of change

Pull-Request Checklist

  • Code is up-to-date with the master branch
  • This pull request links relevant issues as Fixes #00000
  • There are new or updated unit tests validating the change
  • Documentation has been updated to reflect this change

Summary by CodeRabbit

  • Bug Fixes
    • Improved compatibility by ensuring global objects and the Buffer object are correctly assigned across different environments, including support for globalThis.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 24, 2025

Walkthrough

The control flow of the getGlobalVariable() method in PlatformTools was updated to check for globalThis after window and before global. Additionally, the assignment of the Buffer object to the global environment was extended to include globalThis.Buffer, ensuring broader compatibility across environments.

Changes

File(s) Change Summary
src/platform/BrowserPlatformTools.template Updated getGlobalVariable() to check globalThis before global; added globalThis.Buffer assignment.

Sequence Diagram(s)

sequenceDiagram
    participant Code as Application Code
    participant PT as PlatformTools
    participant W as window
    participant GT as globalThis
    participant G as global

    Code->>PT: call getGlobalVariable()
    alt window is defined
        PT->>W: return window
    else globalThis is defined
        PT->>GT: return globalThis
    else
        PT->>G: return global
    end
Loading

Poem

A hop, a skip, a global check,
Now globalThis is on deck!
Buffer’s spread both far and wide,
Across the globals, side by side.
With every change, we leap ahead—
Hopping through the code we tread!
🐇✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
src/platform/BrowserPlatformTools.template (1)

167-169: Consolidate Buffer assignments for modern environments.

Assigning to both window.Buffer and globalThis.Buffer is redundant when they refer to the same object (in most browsers). Consider unifying this into a single block that targets globalThis (with a fallback for legacy). Also, in the Node case you’re using require("buffer/")—the standard import is require("buffer").

Optional refactor:

- if (typeof window !== "undefined") {
-     window.Buffer = Buffer;
- }
- if (typeof globalThis !== "undefined") {
-     globalThis.Buffer = Buffer;
- }
+ const _g = (typeof globalThis !== "undefined" && globalThis) ||
+            (typeof window !== "undefined" && window);
+ if (_g) {
+     _g.Buffer = Buffer;
+ }

And update the Node branch to:

- if (typeof global !== "undefined" && typeof require !== "undefined") {
-     global.Buffer = require("buffer/").Buffer;
- }
+ if (typeof global !== "undefined" && typeof require !== "undefined") {
+     global.Buffer = require("buffer").Buffer;
+ }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5003aaa and 86a8fb9.

📒 Files selected for processing (1)
  • src/platform/BrowserPlatformTools.template (2 hunks)

Comment on lines +24 to +28
if (typeof globalThis !== "undefined") {
return globalThis
}
// NativeScript uses global, not window
return global
Copy link
Contributor

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

⚠️ Potential issue

Guard the fallback to global to avoid ReferenceError.

Right now, if both window and globalThis are undefined, the code unconditionally does return global, which will throw a ReferenceError in many browser contexts (where global is not defined). You should explicitly check for typeof global !== "undefined" before returning it and provide a clear error if no global object is found.

Proposed diff:

-       if (typeof globalThis !== "undefined") {
-           return globalThis
-       }
-       // NativeScript uses global, not window
-       return global
+       if (typeof globalThis !== "undefined") {
+           return globalThis
+       }
+       if (typeof global !== "undefined") {
+           return global
+       }
+       throw new Error("PlatformTools.getGlobalVariable(): no global object available")
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
if (typeof globalThis !== "undefined") {
return globalThis
}
// NativeScript uses global, not window
return global
if (typeof globalThis !== "undefined") {
return globalThis
}
if (typeof global !== "undefined") {
return global
}
throw new Error("PlatformTools.getGlobalVariable(): no global object available")
🤖 Prompt for AI Agents
In src/platform/BrowserPlatformTools.template around lines 24 to 28, the
fallback to return global is not guarded, which can cause a ReferenceError if
global is undefined. Modify the code to check if typeof global !== "undefined"
before returning global, and if neither globalThis nor global is defined, throw
a clear error indicating no global object is available.

@dasoncheng
Copy link
Contributor Author

image
When using sql.js in the browser, inserting or retrieving large amounts of data can block the rendering process. I encountered the above issue during the migration to WebWorker. After adjusting the code, it can run normally in the Web Worker environment.

@dasoncheng
Copy link
Contributor Author

Hi @gioboa , MDN: globalThis is the doc, could you please take a look at this fix for web worker, thanks!

@pkg-pr-new
Copy link

pkg-pr-new bot commented May 26, 2025

typeorm-sql-js-example

npm i https://pkg.pr.new/typeorm/typeorm@11495

commit: 86a8fb9

@alumni
Copy link
Collaborator

alumni commented May 26, 2025

Nowadays globalThis is available on all major platforms.

Honestly, I don't see a reason to keep the getGlobalVariable function.

@coveralls
Copy link

Coverage Status

coverage: 76.308%. remained the same
when pulling 86a8fb9 on dasoncheng:master
into 5003aaa on typeorm:master.

@dasoncheng
Copy link
Contributor Author

@alumni I agree with your point. This PR only addresses the issue of running under WebWorker.

@alumni
Copy link
Collaborator

alumni commented Jul 10, 2025

Would be great to have this fixed for NodeJs Workers as well before merging the PR.

Also, some cleanup would be nice, i.e. replacing window/global with globalThis in both the main and the browser implementation.

@naorpeled naorpeled merged commit ec26eae into typeorm:master Aug 14, 2025
130 of 132 checks passed
Copy link
Collaborator

@gioboa gioboa left a comment

Choose a reason for hiding this comment

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

Thanks @dasoncheng for your help

ThbltLmr pushed a commit to ThbltLmr/typeorm that referenced this pull request Dec 2, 2025
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.

5 participants