Notes: logs of updating fabricjs from v5.3 to v6.0.0-beta1

[ZhengRui]

1. import { fabric } from 'fabric`` -> import * as fabric from 'fabric'`
2. There are some types that are not exposed yet, e.g. TMat2D, events. Before v6 stable comes out, you can expose it by add

"src/*": [
  "dist/src/*"
]

to the typesVersions section. Note that it should be dist/src/* instead of src/* as mentioned here pull/8725, discussions/8715, pull/8717, otherwise it has issue (relates to event types) saying event typed in src/** can not be assigned to the same event typed in dist/src/**. Use dist/src/* will ensure all fabric objects and types are from dist therefore consistent.

• import { TMat2D } from 'fabric/src/typedefs'; TMat2D is required for canvas.setViewportTransform()
• for events, v5's fabric.IEvent -> import { TPointerEventInfo as IEvent } from 'fabric/src/EventTypeDefs';

3. canvas.getObjects() now returns BaseFabricObject (discussion/8739), you have to cast to fabric.Object if it is expected in downstream logic
4. setOptions() not needed anymore, just use set() for all props including custom props
5. setCoords() not needed anymore, just delete it, seems v6 handles that automatically now (not sure though)
6. new fabric.Circle({...props}) has types issue, it asks for full CircleProps which has over 50 props to fill. You can hack it by

const circle = new fabric.Circle()  // this is fine
circle.set({...props})

7. v5 event's pointer used to be absolute coordinates, and setViewportTransform() expects absolute coordinates. In v6 event's pointer is canvas coordinates, but it returns absolutePointer which gives absolute coordinates needed for viewport transform.
8. In v6, canvas.remove() will trigger object:modified event if the removed object is also active. In v5 it does not trigger object:modified event.

'object:modified': (e: IEvent<MouseEvent>) => {
  if (!e.e) return; // likely triggered by canvas.remove()

  // actually modified
},