Something is different between teamwork served locally with yarn start and the teamwork we publish to kubenet such that the devtools extension isn't supported by the production version. Please figure out what this is and change it such that kubenet published teamwork does support devtools.
Beware I have a member of Max telling me about this, and there being some reason for not enabling support -- perhaps some performance factor?
Something is different between teamwork served locally with
yarn start
and the teamwork we publish to kubenet such that the devtools extension isn't supported by the production version. Please figure out what this is and change it such that kubenet published teamwork does support devtools.Beware I have a member of Max telling me about this, and there being some reason for not enabling support -- perhaps some performance factor?