[Javascript] Webpack 3.0 unexpected token ===

Description

Just helping any internet searchers coming around until Webpack fixes this.

If you are

• using Webpack 3
• with parser.amd = false as per the Readme

You will run into this issue https://github.com/webpack/webpack/issues/5198.

The problematic line for me is in ApiClient.prototype.isFileParam.

    if (typeof window === 'undefined' &&
        typeof require === 'function' && // <------ here
        require('fs') &&
        param instanceof require('fs').ReadStream) {
      return true;
    }

Swagger-codegen version

Tried with 2.2.0 and 2.2.2.

Swagger declaration file content or url

Command line used for generation

Steps to reproduce

• require() Swagger generated files from Webpack 3.

Related issues

Suggest a Fix

Go back to the old hack using imports-loader?define=false which still works until the bug is fixed.

The report points to the generated JavaScript ApiClient.prototype.isFileParam code and the README setting parser.amd=false. Start by locating that generated code in the JavaScript templates, then reproduce requiring generated files with Webpack 3. Done when the generated client no longer triggers the reported unexpected-token failure under that setup.