Optimizing colorKit: Running on the UI Thread for Enhanced Performance

[alabsi91]

I refactored colorKit to make it run on the UI thread. To achieve this, I combined all colorKit methods into a single function. The reason I didn't add the 'worklet' directive to each method is that the react-native-reanimated Babel plugin will transform it into something like this:

Before:

function clamp(v: number, max: number) {
  'worklet';
  return Math.min(Math.max(v, 0), max);
}

After Transformation:

const _worklet_1297586879362_init_data = { ... };

const clamp = (function () {
  const _e = [new global.Error(), 1, -27];
  const anonymous = function (v, max) {
    return Math.min(Math.max(v, 0), max);
  };
  anonymous.__closure = {};
  anonymous.__initData = _worklet_1297586879362_init_data;
  anonymous.__workletHash = 1297586879362;
  anonymous.__stackDetails = _e;
  return anonymous;
})();

Although the initial load time might be significantly affected, the trade-off is understandable given the substantial benefit of being able to run any colorKit methods on the UI thread.