search

MrMeCoding / TETR-VERGE

A powerful analytics engine for TETR.IO
Other
24 stars 1 forks source link

"require" is not defined #7

Open SweetSea-ButImNotSweet opened 7 months ago

SweetSea-ButImNotSweet commented 7 months ago

Affected: TETR-VERGE for Browser There is no "require" statement in Chromium-browser, it's only being used by Node.js

Browser: Chrome 121.0.6167.140 (Official Build) (64-bit) (cohort: Stable)

MrMeCoding commented 7 months ago

Which version of VERGE are you using?

MrMeCoding commented 7 months ago

Also, there was a critical error affecting version 0.0.1 of VERGE. You'll need to manually update to 0.0.2 via the GitHub files, sorry for the inconvenience

SweetSea-ButImNotSweet commented 7 months ago

Which version of VERGE are you using?

The latest one, I will try again if I find out you pushed any nrw commits

SweetSea-ButImNotSweet commented 7 months ago

Also it failed on the start of the extension...

MrMeCoding commented 7 months ago

Two errors caused this bug, both of which have been fixed.

The current version of VERGE (0.0.2) should run without errors, let me know if it works for you.

SweetSea-ButImNotSweet commented 7 months ago

Two errors caused this bug, both of which have been fixed.

The current version of VERGE (0.0.2) should run without errors, let me know if it works for you.

Extension loaded, but look like it is stuck in "TETR VERGE IS LOADING..." (network in good condition, TETR.IO loads not too slow, weird) Lemme check again in TETR.IO Desktop (reinstalling time, I don't play TETR.IO in Desktop because, I don't really want to spend extra 200MB of a browser-like app ok I think I should play in it instead of a regular browser)

Update: TETR VERGE in Desktop client works normal, something is weird with browser, lemme try again Update2: Ok I'm pretty sure the browser one is having the loading issue

MrMeCoding commented 7 months ago

Yes, I would like to apologize for not thoroughly testing the browser version of VERGE. We hope to resolve all issues with the browser version in 0.0.3. The current issue is due to insufficient storage in the browser.