I propose the removal of the json-loader dependency. It is unmaintained, and the Webpack version used by osgjs includes natively a json loader.
In my use-case, it would helps a lot: I import OSG modules directly from source (as opposed to loading the whole distribution) to make use of the tree-shaking ability of Webpack. But the explicit use of the json-loader in "osgNameSpace.js" conflicts with the default Webpack 3/4 behavior. It forces the installation an unmaintained package and to make a special case in webpack.config.js for osgjs.
I propose the removal of the json-loader dependency. It is unmaintained, and the Webpack version used by osgjs includes natively a json loader.
In my use-case, it would helps a lot: I import OSG modules directly from source (as opposed to loading the whole distribution) to make use of the tree-shaking ability of Webpack. But the explicit use of the json-loader in "osgNameSpace.js" conflicts with the default Webpack 3/4 behavior. It forces the installation an unmaintained package and to make a special case in webpack.config.js for osgjs.