A common problem is that a scene ends up with both a bundleDependencies and also a bundledDependencies (extra d) section on the package.json file. When this happens, the scene is unable to run, and it's very hard to debug because the error messages aren't very helpful.
This can is a result from running different Node versions on the same project, it often happens when people collaborate, or build from a shared example. It seems older versions of Node create bundleDependencies, newer ones create bundledDependencies. People can manually fix this by deleting the bundleDependencies folder, but it's hard to find out that's the right fix.
Ideally, the explorer could be able to detect when a scene's package.json contains both bundleDependencies and bundledDependencies sections, and if that's the case, it could delete bundleDependencies to keep the scene from breaking.
A common problem is that a scene ends up with both a bundleDependencies and also a bundledDependencies (extra d) section on the package.json file. When this happens, the scene is unable to run, and it's very hard to debug because the error messages aren't very helpful.
This can is a result from running different Node versions on the same project, it often happens when people collaborate, or build from a shared example. It seems older versions of Node create
bundleDependencies, newer ones createbundledDependencies. People can manually fix this by deleting the bundleDependencies folder, but it's hard to find out that's the right fix.Ideally, the explorer could be able to detect when a scene's package.json contains both bundleDependencies and bundledDependencies sections, and if that's the case, it could delete bundleDependencies to keep the scene from breaking.