Wrong 0.3.x definitions (ESM)?

[psioniq]

Hi,

Not quite sure if this is an issue with bitECS or the sandbox I'm using with esm.sh.

I started a project that uses 0.3.38, and everything worked great. Then, a few days ago, the sandbox linter started going crazy and telling me IWorld and Component doesn't exist. This leads me to believe that 0.3.38 is accidentally loading the definitions from 0.4.0 instead.

Seeing as you updated the project 4-5 days ago, maybe you could check if something got mixed up in the process?

Thank you for an awesome package :)

[NateTheGreatt]

very strange! i am pretty sure it is impossible to retroactively modify a previous release on NPM, so it's unlikely the latest release. this feels esm.sh related. i found a potentially related issue here: esm-dev/esm.sh#331

[psioniq]

Very strange indeed (and very annoying!).

The project runs just fine, so it's grabbing the correct package for sure, only with wrong definitions.

Was using AIStudio Build when it broke. You can try this prompt: create an example app using bitecs 0.3.38 - which makes the agent fail the first simple implementation, until it just upgrades to 0.4.0 to fix the issue. Unfortunately, upgrading the project I'm working on to 0.4.0 is not a viable option at this time.

Happens with both aistudiocdn.com and esm.sh as source in importmap. All other imports work as expected (react, zod, mitt, zustand, gl-matrix).

Will try running some tests in other sandboxes tomorrow. Thanks for chiming in!

[NateTheGreatt]

you could try the legacy api of 0.4 bitecs/legacy, where i re-implemented the 0.3 api using the 0.4 api. hasn't been extensively tested but it should work the same

import {defineComponent,defineQuery,enterQuery,exitQuery} from 'bitecs/legacy'

i added this to make incremental migration possible, so you don't have to do everything all at once and can instead progressively migrate as you go.

more info here:
https://github.com/NateTheGreatt/bitECS/blob/main/docs/MIGRATION_GUIDE_0.4.0.md#7-legacy-compatibility-module

[psioniq]

Thanks :)

Looked into that when the problem first appeared, but unfortunately it didn't work as expected (sandbox can't find /legacy in the 0.4.0 package). It could very well just be google screwing around with their sandbox again, or esm.sh is borked somehow (and I think aistudiocdn.com is just a mirror).

Only came here because it was the only package that couldn't resolve correctly.

I'll get back to you if I discover anything new (related or unrelated to bitECS).

[psioniq]

Hello again,

So, the issue is still not resolved (officially), but I found a workaround.

I simply copied the definition file from 0.3.38 into the project to override the wrong one it was loading. The agent no longer complains about it - for now.