p5 Versioning

[taliacotton]

I've noticed the component depends on a specific version of p5 (as of right now I see 1.9.0). I was wondering if there's a way to control which version of p5 it uses. The reason for this is that there are certain features of p5 in prior versions, so I'm wondering if it's possible to downgrade the version. Thanks!

// package-lock.json
    "node_modules/@p5-wrapper/react": {
      "version": "4.3.2",
      "resolved": "https://registry.npmjs.org/@p5-wrapper/react/-/react-4.3.2.tgz",
      "integrity": "sha512-m7MoL63grVVyu39czEi3V3tz29VM4zzd4K9MjNWZ5t7jb4itgHpw6FCiSG2JzU1SqElKgo9ny8NliavPWYYdrw==",
      "dependencies": {
        "microdiff": "^1.3.2",
        "p5": "^1.9.0"
      },
      "peerDependencies": {
        "react": ">= 18.2.0",
        "react-dom": ">= 18.2.0"
      }
    },

[yevdyko]

@taliacotton I guess you can try to install a particular version of p5 explicitly in your project dependencies

[yevdyko]

But the peer dependency probably seems like a more flexible solution, and we don't need to strictly adhere to the preferred version of p5 for users since we only provide a wrapper on top of it. To sum up, I don't mind to move it to peer dependencies

[yevdyko]

I think that when a dependency version is specified in a range, it can be overwritten if the user explicitly specifies the required version in their project. If not, the latest version will be installed. I can try this on a demo application

[yevdyko]

This is how it looks like in the demo app. There are 2 branches:

1. p5 version as 1.4.1: yevdyko/react-p5-wrapper-demo@48b2024
2. p5 the latest: yevdyko/react-p5-wrapper-demo@3680083

[jamesrweb]

Okay, let's try it this way first and fallback to peer dependencies later if necessary then