How to use node-libcurl with NextJS using native-ext-loader?

I need Help please!

I am getting the following error when running my code on the browser:

I am using NextJS on a Netlify build image that uses Ubuntu version 16.04 (aka Xenial) as the base.

my next.config.js is set as follows:

As you can see I’m using native-ext-loader as a way to load your npm package into my build.

I’m assuming the error is basically saying it can not find the binary files that I am trying to include in the config above.

Please let me know if you need anything else in helping resolve this issue.

Thanks in advance, Antonio.

[9ntonio]

@JCMais I can confirm that your suggestion to use getServerSideProps addressed my issue. I had to use it as an async function per the following code. Please note I am using NextJS v10.0.6.

import { NextPage } from 'next';
import querystring from 'querystring';
const url = 'https://slack.com/';

interface Props {
  hostData?: string;
  slackCode?: any;
}

const Page: NextPage<Props> = ({ hostData, slackCode }) => (
  <main>

    <h1>Your data:&nbsp; 
      <u>{hostData}</u>
    </h1>

    <h1>Slack Data:<br /> 
      <u>{slackCode}</u>
    </h1>

  </main>
)

export async function getServerSideProps({ req, query }) {
  const{ Curl } = require('node-libcurl');
  const curl = new Curl();

  const hostData = req ? req.headers.host : 'NO HOST DATA';
  const slackCode = query.code;
  const data = {
    'code': slackCode,
    'client_id': process.env.CLIENT_ID,
    'client_secret': process.env.CLIENT_SECRET,
  }

  curl.setOpt(Curl.option.URL, url);
  // !! You need to build the query string,
  // !! node has this helper function for that:
  curl.setOpt(Curl.option.POSTFIELDS, querystring.stringify(data));
  curl.setOpt(Curl.option.VERBOSE, true);

  curl.on('end', (statusCode: any, body: any) => {
    console.log("\x1b[31m",`\n Body: \n${body}`);
    curl.close();
  })

  curl.on('error', curl.close.bind(curl));
  curl.perform();
  return { props: { hostData, slackCode } };
}

export default Page

For anyone trying this as a fix, please note to use the following structure of your returned data where data is whatever object you wish to return:

return { props: {data} }

If you do not use this structure you will get an error.

Thank you for your help, and I hope this helps anyone who has the same issue I did.

[JCMais]

Glad you got it working @9ntonio, and thanks for posting the full solution.