Running a vanilla JavaScript Node.js project with "type": "module" in package.json gives me the following error:
node:internal/process/esm_loader:97
internalBinding('errors').triggerUncaughtException(
^
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '___\node_modules\@fastify\middie\engine' imported from
___\node_modules\fastify-next-auth\dist\index.mjs
Did you mean to import @fastify/middie/engine.js?
?[90m at new NodeError (node:internal/errors:399:5)?[39m
?[90m at finalizeResolution (node:internal/modules/esm/resolve:326:11)?[39m
?[90m at moduleResolve (node:internal/modules/esm/resolve:945:10)?[39m
?[90m at defaultResolve (node:internal/modules/esm/resolve:1153:11)?[39m
?[90m at nextResolve (node:internal/modules/esm/loader:163:28)?[39m
?[90m at ESMLoader.resolve (node:internal/modules/esm/loader:838:30)?[39m
?[90m at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)?[39m
?[90m at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)?[39m
?[90m at link (node:internal/modules/esm/module_job:76:36)?[39m {
code: ?[32m'ERR_MODULE_NOT_FOUND'?[39m
}
Node.js v18.16.0
Fixing it by adding .js to the dist file works locally (import Middie from "@fastify/middie/engine.js"; ),
but I am currently using --experimental-specifier-resolution=node as a workaround.
Running a vanilla JavaScript Node.js project with
"type": "module"
in package.json gives me the following error:Fixing it by adding .js to the dist file works locally (
import Middie from "@fastify/middie/engine.js";
), but I am currently using--experimental-specifier-resolution=node
as a workaround.