@Joyce So … we are having a bug with custom component that only happens in the published build and the standard editor - when we go into development mode in the editor - the bug is not present.
1) Can anyone at WeWeb explain what the key differences are in the environments - that might help us know where to look …
2) WeWeb does not yet have a proper “developer relations” and/or support - LOVE that JP has joined - but his role is “demo artist” and educator - there needs to be a point of contact for development support - even if it’s a “enterprise paid support plan”.
1 Like
it may be because of package version conflict.
from the docs:
You can add other dependencies if you need to. Be aware that all package.json will be merged in the final web-app and, if two components need the same dependencies, only the more recent one will be installed. This can lead to conflicts.
I’m happy to take a quick look at the code and see if there is something that rings a bell before going to holiday 
We think we figured it out - we will know tomorrow. Definitely not dependency related. I think we are good - but I am definitely curious about any differences in the environments (normal edits vs dev mode)