Next.js Core Imports Throwing Error

[grizzled veldt]

This is only happening inside the next app. We're importing the node workers for a project, and we're getting errors in the console.

IMPORT CODE

// Core Modules
import { parentPort, workerData } from 'worker_threads';

CONSOLE ERROR

wait  - compiling...
error - ./src/logic/DatabaseParser.ts:2:0
Module not found: Can't resolve 'worker_threads'
  1 | // Core Modules
> 2 | import { parentPort, workerData } from 'worker_threads';

Import trace for requested module:
./src/components/templates/portal.template.tsx
./src/pages/index.tsx

https://nextjs.org/docs/messages/module-not-found

Before we get lost in the rabbit hole, the official Node.js docs now say to use node:worker_threads instead of just worker_threads.

// Core Modules
import { parentPort, workerData } from 'node:worker_threads';

Error in VS Code:

Cannot find module 'node:worker_threads' or its corresponding type declarations.ts(2307)

Recompiled error on save:

wait  - compiling...
error - node:worker_threads
Module build failed: UnhandledSchemeError: Reading from "node:worker_threads" is not handled by plugins (Unhandled scheme).
Webpack supports "data:" and "file:" URIs by default.
You may need an additional plugin to handle "node:" URIs.
Import trace for requested module:
node:worker_threads
./src/logic/DatabaseParser.ts
./src/components/templates/portal.template.tsx

The "quick fix" in VS Code when using the node: prefix, was to install @types/node. But I've already got it installed.

"devDependencies": {
    "@types/node": "^12.12.21",
}

[merry ibex]

This is probably because you can't use it in the frontend.

[grizzled veldt]

It's being called outside of a component file, and used in an official static props method.

[merry ibex]

But the only way worker_threads wouldn't be available is if you aren't building for node. :)

[grizzled veldt]

You might need to expand on that. The entire project is in Node.

[merry ibex]

The fact that you are using node to build it doesn't mean it's building for node. Next projects are first and foremost built for browsers with optional ssr componentry

The entire project is not in node. In fact, I'd wager that the vast majority of it isn't.

[grizzled veldt]

The docs say to use the static props methods.
https://nextjs.org/docs/messages/module-not-found

I've also run through countless solutions on stack overflow, they many of them talk about using a next config file. Which I've added in multiple variations.

I'm guessing that the class component is screwing this up.

I've tested each solution here and came up empty.

https://stackoverflow.com/questions/64926174/module-not-found-cant-resolve-fs-in-next-js-application

[grizzled veldt]

Any ideas?