Brandon Bennett

Woah, crazy bug! Glad to know you are working on it. Just reinstalled the Live Server package because I came across this while trying to host a project over localhost....

Alright, figured out how to temporarily fix the issue for use with Live Server. The `package.json` for Live Server has Colors.js set to use the newest possible version available, `latest`,...

Is it an option that, in the meantime, you could revert your project back to `1.4.0`, the release before the new change was introduced? This seemed to fix all of...

Yeah, changing the version number to an older release would fix it, but there are many projects out there that haven't been updated in multiple years, I don't think the...

I'm not exactly sure what your dev stack is like for your use case, but I currently have a workaround to use `jsmediatags` as an ES Module exclusively, in the...

> In fact, many of the new ES6 syntaxes are not fully supported in current browsers. You may need Babel, or add type="model" to (view it with chrome). This is...

Is there a possible way to fix it? I can try to add a patch too if it's hard to find where it's at.

I have the same issue here. I also noticed this is the same case for any custom skin packs I have made myself, like ones from outside the marketplace. The...

Alright, I have some progress for this goal! Been working on my own fork of the project to add ESM, TypeScript, and native browser support out of the box. There's...

I just noticed this today too. My world was loaded at some point during the current v1.19 release cycle, and it's `level.dat` file has been showing a version number of...