Fix duplicate p5.js init by checking window.p5 and skipping if alread…

[VANSH3104]

…y loaded

Resolves #7687

Changes:

• Add check for window.p5 instanceof p5 before global binding
• Skip initialization and warn if p5.js was already loaded
• Avoids errors from Object.defineProperty redefinition
• Fixes issue where multiple p5.js imports cause failures

Screenshots of the change:

PR Checklist

• [x ] npm run lint passes
• Inline reference is included / updated
• Unit tests are included / updated

[limzykenneth]

The recommendation is to just check whether window.p5 is already defined or not. It doesn't matter whether that p5 variable comes from previously loaded p5.js or not as there's no easy way to check it.

[limzykenneth]

window.p5 is the constructor so it won't be an instance of p5, this condition will always be false.

[limzykenneth]

Overwriting window.p5 here will break a lot of things, it shouldn't be redefined.

[VANSH3104]

Hi @limzykenneth,Sorry for the late response—I’ve been busy with my semester exams. I made some changes to the code based on the previous discussion. Could you please take a look at it?

[limzykenneth]

Now that I think about it, I'm not sure the idea I had would work as in this case p5 would just detect itself as having already been defined as window.p5 making initialization impossible. @VANSH3104 Have you tested the code here to see if it works?

[VANSH3104]

@limzykenneth Yes, I did test the code, but unfortunately didn’t get the desired result. I think your concern about p5 being already attached to window.p5 and causing initialization issues might actually be what's happening here. I’m still experimenting to better understand the behavior