GraphQL not loading

[nenti]

[ERROR][GraphqlSchemaHot]:
SyntaxError: Unexpected token import

[nodkz]

When you start webpack you should use correct babel config which understands import clause in your code. Enviroment in which launched webpack does not understand ES6.

What comand do you use for starting webpack? Do you use webpack cli or start webpack via node script (something like it done in https://github.com/kriasoft/react-starter-kit/blob/master/tools/start.js#L103)?

In my apps I'm using 2nd variant (when webpack started via node script, which launching via babel-node).

[nenti]

I am using the serverless webpack (https://github.com/serverless-heaven/serverless-webpack). And babel is working just fine after webpack has finished packing the code.

webpack.config.js
module: {
    rules: [
      {
        test: /\.js$/,
        exclude: /node_modules/,
        use: [
          {
            loader: 'babel-loader',
          },
        ],
      },
      {
        parser: {
          amd: false,
        },
      },
    ],
  },

.babelrc
{
  "comments": false,
  "sourceMaps": "both",
  "presets": [
    ["env", {
      "targets": {
        "node": "6.10"
      }
    }],
    "stage-2"
  ],
  "plugins": [
    "source-map-support"
  ]
}

[geovanisouza92]

@nenti is your babel configuration file really called babel.rc?

Can you check the docs about configuration and maybe rename it to .babelrc? I think the problem is that babel itself is not able to read the source code, and this has nothing to do with webpack or serverless-webpack.

Another test: try to manually run webpack, replacing slsw.lib.entries with each function file, just to ensure that's not related with serverless-webpack or webpack itself.

[nenti]

@geovanisouza92 thx for your input. The .babelrc was a typo. So filename is correct.

When I set entry to handler handler.js directly nothing changes.
When I run the handler.js directly with node I get unexpected token import.
When I run the handler.js with babel-node file is loading properly.

[geovanisouza92]

@nenti thanks for checking. I'm confused with that { parser: { amd: false } } in your webpack without a test rule. Is that applied to everything? Have you tried without it?

I think that it's expected the unexpected token import when using node, specially if you are running with node < 8, because prior this version, import/export was not supported.

[nenti]

My local node version is v8.9.4. I think the parser:amd part slipped in in earlier struggles with the webpack setup. I removed it and no change.

I even tried running webpack directly, and it fails to build. So I don't expect serverless-webpack to be the issue here. I suppose it is the way how this library loads the sources.