Usage with NextJS about vm2 HOT 8 CLOSED

Have you tried without installing coffee-script and setting ignoreWarnings[].message = /Can't resolve 'coffee-script'/ in the webpack config?

from vm2.

@XmiliaH I updated the config to be:

/** @type {import('next').NextConfig} */
const nextConfig = {
  webpack: (config) => {
    return {
      ...config,
      ignoreWarnings: [/Can't resolve 'coffee-script'/],
    };
  },
};

module.exports = nextConfig;

And now I'm getting the error:

- warn ./node_modules/vm2/lib/resolver-compat.js
Critical dependency: the request of a dependency is an expression

Import trace for requested module:
./node_modules/vm2/lib/resolver-compat.js
./node_modules/vm2/lib/nodevm.js
./node_modules/vm2/lib/main.js
./node_modules/vm2/index.js
./app/api/script/route.ts

from vm2.

Then try to add the additional module.parser.javascript.commonjsMagicComments=true.

from vm2.

Updated config:

/** @type {import('next').NextConfig} */
const nextConfig = {
  webpack: (config) => {
    return {
      ...config,
      ignore warnings: [/Can't resolve 'coffee-script'/],
      module: {
        ...config.module,
        parser: {
          ...config.module.parser,
          javascript: {
            ...config.module.parser.javascript,
            commonjsMagicComments: true,
          },
        },
      },
    };
  },
};

module.exports = nextConfig;

The warning is gone but when I access the route, I get a 404 error. To be sure it is not being caused by nonrelatedvm2 code, I removed it, and I can confirm the API route works normally. So, looks like for some reason, NextJS is not being able to compile the dependencies correctly.

The route code:

import { NextResponse } from "next/server";
import { NodeVM } from "vm2";

export async function GET() {
  console.log("Enter");
  const vm = new NodeVM({
    timeout: 500,
    sandbox: {},
  });
  console.log("Starting");
  const result = vm.run(`return { a: "Bruno: }`);
  console.log("Result");
  return NextResponse.json({ data: result });
}

The logs:

- wait compiling /api/script/route (client and server)...
- event compiled client and server successfully in 1066 ms (395 modules)
- wait compiling /_error (client and server)...

Unfortunately, looks like there is no debug mode for next dev command.

from vm2.

The code that I used to test if it was related to vm2 or not.

import { NextResponse } from "next/server";
import { NodeVM } from "vm2";

export async function GET() {
  console.log("Enter");
  console.log("Starting");
  console.log("Result");
  return NextResponse.json({ data: "a" });
}

The logs:

- event compiled successfully in 242 ms (89 modules)
Enter
Starting
Result

from vm2.

While I cannot tell you why it does not work now. You could try a try-catch block and log the exception.
And some notes: NodeVM does not have a timeout option and the return in the sandbox script will not be used.

from vm2.

Even with try-catch there is no error available.

import { NextResponse } from "next/server";
import { VM } from "vm2";

export async function GET() {
  try {
    console.log("Enter");
    const vm = new VM({
      timeout: 500,
      sandbox: {},
    });

    console.log("Starting");
    const result = vm.run(`return { a: "Bruno: }`);

    console.log("Result");

    return NextResponse.json({ data: result });
  } catch (error) {
    console.error(error);
  }
}

I really appreciate your help on this but looks like NextJS is missing something. Ty.

from vm2.

Closing this for now since NextJS does not provide any helpful information on what is causing the error.

from vm2.