Bug: `Entity` without `CollisionComponent` don't rendering on prod build

[keasy9]

Steps to Reproduce

1. Make Entity without CollisionComponent (but with TransformComponent and GraphicsComponent, so it can render)
2. Deploy project to github pages (didn't tried with orher servers, but local build in prod mode doesn't have this issue)

Actual Result

Entities not showing on screen, but showing in Excalibur dev tool. Debug drawing works partialy - shows position, coordinates and names of entities, but now shows graphic bounds.

Environment

• using vite and pnpm, vue for UI
• browsers and versions: Firefox 147.0.4 (64 bit) for Windows, Chrome 145.0.7632.109 for Adroid, didn't check other browsers
• operating system: Win 11 25H2 (26200.7840) and Android 11, didn't check other systems
• Excalibur versions: 0.32.0, didn't check other versions

Project repository is open, deployed to https://keasy9.github.io/excalibur-space/, issue can be reproduced in 57aacf7dbd7d5b55028b7e9f2df427e83795d23d commit

Also you can notice that I'm using custom Entity class with some getters and setters, but I'm tried to replace it with Excalibur Entity and issue remains.

Current Workaround

Just added ColliderComponent to all entities in project and even in Particles. Didn't specified any collider shape.
Also can be cured by using Actor instead of Entity because Actor always have ColliderComponent.

[eonarheim]

This does seem unexpected, I'll look into this today

[eonarheim]

I'm having trouble reproducing this with this minimal example

https://excaliburjs.com/playground/?code=FASwtgDg9gTgLgAgFQIIYGcEFMAeCBmMUYCA5LgMaoA2IARgK4ykDcwFUAdulNVgHTUoAcwAUpABZZqQhAHdY1ACakAlG3Zd0iYajBYEAXgScsc7Dn4BRTsJCnRAb2AJXCKpwBuGK332c4AEklAC4yCBgsTxAzAFoPb3RSABoXNyUQdAhqVABPAFkoJSww3H4AEUzsvMLi-gAxEDgAYS44VHssGFS3eRAlOAkwgDYABlGetykQYQk4MIAWceAAX3VgTW5ELACm3KMTMwtrXbhc0QBtNNNzMoAVGFRufFgwVsguHbhRVUmb44A4o8IBIQBR0O9oKYAk40q5hMDQeCws5eq4KExIgEwv8ygAlLAUdq2PhODhCGClSytCn8AlKZJ9AZDBAARnGjOms3mbPGCDWcP5k3RmK+YVIGJgWLgpDSAoAuusvnt+MIsN97o9nq9IZ8Aqp+NBMMYyp5CaIAEwchBW0brYC6fT8VBKJSiZVne2OgTaVDwH5sIA

[eonarheim]

Oh I see, during the production build it doesn't work! Wild,I'll dig into this.
npm run build && npm run serve

[eonarheim]

I'm still digging, but it looks like something has gone wrong during the bundle and these 2 components have the same name confusing excalibur at runtime when it tries to sort entities into ECS query buckets. The first is the transform component implementation, and the second is the graphics component implementation. Not sure if this is a rolldown-vite issue yet, but could be.

[keasy9]

Not sure if this is a rolldown-vite issue yet, but could be.

Just tried default vite (with rollup), and issue persists with it too

[eonarheim]

Ack, indeed. I did a little more digging and it appears the default name mangling is causing some issues in the instanceof checks in both cases. This keepNames seems to work around the issue

export default defineConfig({
  base: './',
  plugins: [vuePlugin()],
  optimizeDeps: {
    exclude: ['excalibur'],
  },
  build: {
    assetsInlineLimit: 0,
    sourcemap: true,
    rolldownOptions: {
      keepNames: true,
      output: {
        format: 'umd'
      }
    }
  },
  resolve: {
    alias: {
      '@': path.resolve(__dirname, '/src'),
    }
  },
  server: {
    host: true,
    port: 5173,
  },
});

[eonarheim]

I'm seeing some advice to hint vite with static members on the builtin excalibur components... I'll keep exploring. It's odd that this is an issue, I'd expect vite to correctly preserve instanceof behavior.

class A extends Base { static _type = 'A' as const }
class B extends Base { static _type = 'B' as const }

[keasy9]

This keepNames seems to work around the issue

Yep, this one works perfectly, thank you so much!

[eonarheim]

I'm going to put together an issue for vite with a minimal reproduction, because this does seem like unexpected bundler behavior to me.

@mattjennings @kamranayub what do you think?

[kamranayub]

I'm going to put together an issue for vite with a minimal reproduction, because this does seem like unexpected bundler behavior to me.

@mattjennings @kamranayub what do you think?

Yeah I think that would be a good upstream fix if it's truly a bug!

[Markkop]

Hey guys. I still have to make a repro for you, but wanted to share I'm also seeing issues where Excalibur works on local dev environment, but breaks on prod.
My error is CWzvY0Ly.js:10 [Fatal] : TypeError: Cannot read properties of undefined (reading 'forceOnScreen')
Will share more once I dig deeper into it (so far no AI model was able to fix it)

[eonarheim]

@Markkop are you still running into this? If you have a chance to toggle keepNames try that, otherwise please send a repro