[Bug]: globalCompositeOperation does not work in node.js

[joanned]

CheckList

• [X] I agree to follow this project's Code of Conduct
• [X] I have read and followed the Contributing Guide
• [X] I have read and followed the Issue Tracker Guide
• [X] I have searched and referenced existing issues and discussions
• [X] I am filing a BUG report.
• [X] I have managed to reproduce the bug after upgrading to the latest version
• [X] I have created an accurate and minimal reproduction

Version

5.3.0

In What environments are you experiencing the problem?

Node.js

Node Version (if applicable)

16.13.0

Link To Reproduction

https://codesandbox.io/s/fabric-2-gf7x5r?file=/src/index.js (refresh the browser tab to see image result)

Steps To Reproduce

Code reproduced here in this codesandbox node.js environment that generates the image in node.js with fabric: https://codesandbox.io/s/fabric-2-gf7x5r?file=/src/index.js (refresh the browser tab to see image result)

1. I first created the starfish background image and added it to the canvas, which works fine.
2. Then I created a fabric Group, that groups the img and the maskImg together.
3. I set maskImg.globalCompositeOperation = 'destination-out'; so that any parts that maskImg touches img, it will mask those areas. I don't want to mask the background image.
4. I add that group to canvas

note: is there a better way to do masking of specific images and not the whole canvas? I tried image.BlendImage which did not work well at all. globalCompositeOperation works great but it's not working in node.js.

Expected Behavior

This jsfiddle shows the expected behavior. It works in a javascript/html environment: https://jsfiddle.net/aqvkj5zg/2/

The maskImage properly masks the baseImage and not backgroundImage

Actual Behavior

This codesandbox in the node environment that generates the image shows that maskImage masks both the backgroundImage and baseImage : https://codesandbox.io/s/fabric-2-gf7x5r?file=/src/index.js

Error Message & Stack Trace

no error logs

[ShaMan123]

Somewhere I have a PR that handles this case. I believe setting objectCaching to true will fix the issue (node has it disabled by default .the browser has it enabled)