You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently using phaser-plugin-inspector in a project where we've upgraded to Tweakpane 4.0.4. However, the current peer dependency in phaser-plugin-inspector is set to "tweakpane": "^3.1.0", which is causing conflicts in our dependency resolution.
Could you please consider updating the peer dependency to include Tweakpane 4.x? This would allow users to take advantage of the latest features and improvements in Tweakpane while still using phaser-plugin-inspector.
Thank you for all your help with Phaser
The text was updated successfully, but these errors were encountered:
I'm not sure how the plugin could access Tweakpane in the browser without adding an import map or globalizing Tweakpane's exports. I guess the plugin could bundle Tweakpane instead.
I think the method changes are doable somehow. But I think I would have to bundle Tweakpane to keep the plugin loadable like people are used to, and that might be a little worse for your situation.
hey @samme !
I'm currently using
phaser-plugin-inspector
in a project where we've upgraded to Tweakpane 4.0.4. However, the current peer dependency inphaser-plugin-inspector
is set to"tweakpane": "^3.1.0"
, which is causing conflicts in our dependency resolution.Could you please consider updating the peer dependency to include Tweakpane 4.x? This would allow users to take advantage of the latest features and improvements in Tweakpane while still using
phaser-plugin-inspector
.Thank you for all your help with Phaser
The text was updated successfully, but these errors were encountered: