If we are working in geppetto-application and we want to try a new version of a package (I tried with pixi.js from 4.2.0 to 5.0.4), it does not work. The import keeps defaulting to 4.2.0. That is because we are instructing webpack to first look for modules in geppetto-client node_modules folder.
Inverting the sequence will give us the right module version. But now we have the same issue in the opposite order (if we work in development mode, and we install a new version of an existing package in geppetto-client, then we wont be able to import it properly because it will be found first in geppetto-application node_module folder).
If we are working in geppetto-application and we want to try a new version of a package (I tried with pixi.js from 4.2.0 to 5.0.4), it does not work. The import keeps defaulting to 4.2.0. That is because we are instructing webpack to first look for modules in geppetto-client node_modules folder.
Fix:
Inverting the sequence will give us the right module version. But now we have the same issue in the opposite order (if we work in development mode, and we install a new version of an existing package in geppetto-client, then we wont be able to import it properly because it will be found first in geppetto-application node_module folder).
The problem appears when changing versions of an existing package, but it does not affect when installing new packages.
Example:
With abs path:
ImageViewer.js:11 Uncaught TypeError: __WEBPACK_IMPORTED_MODULE_2_pixi_js__.Application is not a function
With relative paths: