Cristiano Soleti
Cristiano Soleti
Hi, thanks for replying. I would say that if a package has incorrect peer dependencies weird stuff can happen, it's not entirely to npm as far as I know. Also,...
`{ "name": "npmpixi", "version": "1.0.0", "description": "", "main": "index.js", "scripts": { "test": "echo \"Error: no test specified\" && exit 1" }, "peerDependencies": { "@pixi/sound": "4.0.6", "pixi.js": "6.4.2", "typescript": "4.7.4" },...
Thanks that solution might work, buy I can't afford it as I'm leveraging peer deps on purpose from npm7+.
Any update on this? I have the same exact issue on windows. I used the webpack/typescript template. Using the latest Phaser Editor 2D v3.65.0
[test.zip](https://github.com/PhaserEditor2D/PhaserEditor2D-v3/files/13788236/test.zip) There you go.
I'm currently on my Mac now, I can't test on windows, and I have the same exact issue. I'm not sure if i'm doing anything wrong at this point.
I am running with Sudo. Project has node modules. I did open with Chrome. I am using the `Webpack TypeScript` template. Still same result.
I was trying to use the web one, cause the all in one is not working either. I think it asked me to setup something the very first time, and...
npm run editor has the same result btw
Few things: 1. If you have wrongly setup the editor like me, you can reset by ` rm -rf /Users//.phasereditor2d` 2. If it looks like it's doing nothing, you need...