benjamin hon
benjamin hon
any updates on this? seems to still be the case
I notice that anchor/dist/esm are not using .mjs extension, and there is no `type: module` in the package.json?
i think the problem lies in esm/index.js can we change it to? we shouldnt be using require in esm right? seems like vitest is not allowing it ``` // if...
Currently using vitest and it fails as mentioned, i think they have some checks, the only way i can make it work is to change `esm/index.js` to the following: ```...
Using mocha test doesn't seem to throw the error for inlining the module. is vitest being to strict? seems many external modules are not following best practices and waiting for...
I think the problem is when there are require imports in esm modules and vitest detects that and throws the error? However some libraries use require in esm because apparently...
Yep that was the code causing the issue, i had to manually patch that to use dynamic imports and it worked, i did ask them if its possible to change...
Sure @GoodBoyDigital I have done up a playground here: https://www.pixiplayground.com/#/edit/LAjrRIkmLeSfhO7p22nAu The only way it seems is to reserve z coordinates for use in shaders to between 0.001 to 1.0, as...
Wish there was a better way? other than redefining
yea i end up having to define so many types eg. entity type, return from rest api type etc.. how can the typed repository fetch not even return the correct...