TomerAtarScopio

I was able to get tsconfig paths to work by passing a flag to node rather than importing `tsconfig-paths` at the migration level ```sh NODE_OPTIONS="-r ./scripts/bootstrapPaths.js" yarn sequelize-cli db:migrate ```...

On my case, it was a very specific scenario where the consumer of my react library was using yarn resolutions for an underlaying common dependency, the resolved library version didn't...

Can be mitigated by explicitly setting the enabledHandles after the Transformer is constructed: ```ts const transformer = app.stage.addChild( new Transformer({ group: [circle], boxScalingEnabled: true, rotateEnabled: false, enabledHandles: [ 'bottomLeft', 'bottomRight',...