__webpack_require__(...) is not a function

[PatrikElfstrom]

I'm running FaunaDB in a Netlify Function built with Webpack and I get this error:
Error during invocation: TypeError: __webpack_require__(...) is not a function

This is because of a bug in isomorphic-unfetch: developit/unfetch#122

[BrunoQuaresma]

@PatrikElfstrom what driver version are you using?

[PatrikElfstrom]

I am using v2.9.2

[danieltodonnell]

Thanks for reporting this. we will look into it on Monday.

[BrunoQuaresma]

@PatrikElfstrom I'm using netlify cli and faunadb v.2.9.2 and the following code is working good.

const { Client, query: q } = require('faunadb')
const db = new Client({ secret: '...' })

exports.handler = async event => {
  if (event.httpMethod !== 'POST') {
    return { statusCode: 405, body: 'Method Not Allowed' }
  }

  const data = JSON.parse(event.body)

  try {
    const { ... } = await db.query(
      q.Let(...)
    )

    return {
      statusCode: 200,
      body: JSON.stringify({ ... }),
    }
  } catch (error) {
    return {
      statusCode: 500,
      body: JSON.stringify({ ... })
    }
  }
}

Can you share with us more details about the tools you are using?

[PatrikElfstrom]

I think the issue might be that I’m transpiling from es6 to es5. I’ll look into it in a few hours.

On Mon, 21 Oct 2019 at 16:37, Bruno Quaresma ***@***.***> wrote: @PatrikElfstrom <https://github.com/PatrikElfstrom> I'm using netlify cli and faunadb v.2.9.2 and the following code is working good. const { Client, query: q } = require('faunadb') const db = new Client({ secret: '...' }) exports.handler = async event => { if (event.httpMethod !== 'POST') { return { statusCode: 405, body: 'Method Not Allowed' } } const credentials = JSON.parse(event.body) try { const { user, token } = await db.query( q.Let(...) ) return { statusCode: 200, body: JSON.stringify({ ... }), } } catch (error) { return { statusCode: 500, body: JSON.stringify({ ... }) } } } Can you share with us more details about the tools you are using? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#186?email_source=notifications&email_token=AADZVNHZZV34FAISBLRSNXDQPW5CFA5CNFSM4JCSNRXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB2RPZA#issuecomment-544544740>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADZVNCXL4RO4LX62OW25PDQPW5CFANCNFSM4JCSNRXA> .

-- // Patrik

[PatrikElfstrom]

@BrunoQuaresma Similar error with your code just n(...) is not a function which I guess is the same function.

This is the repo: https://github.com/PatrikElfstrom/schnitzellunch
It's a pretty bog standard create-react-app.
If your going to run that you need to change the urls in src/lambda/restaurants-recrawl.js to http://localhost:8888
And then open http://localhost:8888/.netlify/functions/restaurants-recrawl and you should get the error in the console.

I've tried with node v10.16.3 and v12.13.0 but the same error.
And the row number points me to line 3 here which is the loading of node-fetch

module.exports = global.fetch = global.fetch || (
	typeof process=='undefined' ? (__webpack_require__(/*! unfetch */ "../../node_modules/unfetch/dist/unfetch.mjs").default || __webpack_require__(/*! unfetch */ "../../node_modules/unfetch/dist/unfetch.mjs")) : (function(url, opts) {
		return __webpack_require__(/*! node-fetch */ "../../node_modules/node-fetch/lib/index.mjs")(url.replace(/^\/\//g,'https://'), opts);
	})
);

(And placing .default just after __webpack_require__(...) solves the issue)

[khrome83]

I am having this issue also. I spent all day trying to solve it.
@danieltodonnell - are you cutting a release.

[danieltodonnell]

we are cutting 2.9.3 in the next hour or two. For now use the 2.9.3-pre1 prerelease. it is identical to the actual release

[khrome83]

@danieltodonnell - I really appreciate the responsiveness. Thank you!

[danieltodonnell]

Hello everyone, I appreciate your patience with this matter. JS Drivers v2.9.3 have been released
https://www.npmjs.com/package/faunadb/v/2.9.3

This should hopefully address your issues, but if not, please open an issue and we will address it asap (usually the same or next day).

Thank you!

[khrome83]

@danieltodonnell - worked like a charm. I did my first transaction too my FaunaDB.