define wrapper blocks webpack2

The current define wrapper in JSONIX blocks usage in webpack2, I wonder if it’s time to get rid of this?

        /*if (typeof define !== 'function') {^M
                // Load the define function via amdefine^M
                var define = require('amdefine')(module);^M
                // If we're not in browser^M
                if (typeof window === 'undefined')^M
                {^M
                        // Require xmldom, xmlhttprequest and fs^M
                        define(["xmldom", "xmlhttprequest", "fs"], _jsonix_factory);^M
                }^M
                else^M
                {^M
                        // We're probably in browser, maybe browserify^M
                        // Do not require xmldom, xmlhttprequest as they'r provided by the browser^M
                        // Do not require fs since file system is not available anyway^M
                        define([], _jsonix_factory);^M
                }^M
        }^M

[dubst3pp4]

Okay, I could get a workaround for webpack as follows:

Install imports-loader and exports-loader and add the following rule to webpack.config.js:

    module : {
        rules: [
            {
                test: require.resolve("jsonix"),
                use: ['imports-loader?require=>false', 'exports-loader?Jsonix']
            },
        ]
    }

You can then import Jsonix like so:

import Jsonix from 'jsonix';

The webpack-rule does the following:

• it triggers when jsonix is loaded
• for the jsonix module it sets require to false (so jsonix thinks it runs in the browser)
• it exports the global variable Jsonix, so that it can be used in ES6 import statements

@highsource the code that checks in which context Jsonix is running should also check for the ES6 import statement, which is the mostly used way to import modules in webpack. So it would happily run with webpack as well as with native ES6 imports. Thanks for that great library 😃

[GFdevelop]

    module : {
        rules: [
            {
                test: require.resolve("jsonix"),
                use: ['imports-loader?require=>false', 'exports-loader?Jsonix']
            },
        ]
    }

On new versions of imports/exports-loader (I’m using v1.1.0) the equivalent syntax is:

    module : {
      rules: [
        {
          test: require.resolve("jsonix"),
          use:[
            "imports-loader?type=commonjs&additionalCode=var%20require%20=%20null",
            "exports-loader?type=commonjs&exports=single|Jsonix"
          ]
        }
      ]
    }