nest-modules / mailer

📨 A mailer module for Nest framework (node.js)
https://nest-modules.github.io/mailer/
MIT License
825 stars 171 forks source link

Error: Cannot find module '@css-inline/css-inline-linux-arm64-musl when starting application #1209

Open jaqarrick opened 1 week ago

jaqarrick commented 1 week ago

Describe the bug When I am starting my nest app I see the following error:

worker-1  | Error: Cannot find module '@css-inline/css-inline-linux-arm64-musl'
worker-1  | Require stack:
worker-1  | - /app/node_modules/@css-inline/css-inline/index.js
worker-1  | - /app/node_modules/@nestjs-modules/mailer/dist/adapters/ejs.adapter.js
worker-1  | - /app/dist/apps/worker/main.js
worker-1  |     at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1140:15)
worker-1  |     at Module.Hook.Module.require (/app/node_modules/dd-trace/packages/dd-trace/src/ritm.js:54:29)
worker-1  |     at require (node:internal/modules/helpers:177:18)
worker-1  |     at Object.<anonymous> (/app/node_modules/@css-inline/css-inline/index.js:206:31)
worker-1  |     at Module._compile (node:internal/modules/cjs/loader:1364:14)
worker-1  |     at Object.Module._extensions..js (node:internal/modules/cjs/loader:1422:10)
worker-1  |     at Module.load (node:internal/modules/cjs/loader:1203:32)
worker-1  |     at Function.Module._load (node:internal/modules/cjs/loader:1019:12)
worker-1  |     at Module.require (node:internal/modules/cjs/loader:1231:19)
worker-1  |     at Module.Hook.Module.require (/app/node_modules/dd-trace/packages/dd-trace/src/ritm.js:85:33)

This occurred after upgrading to 2.0.2 of @nestjs-modules/mailer I am using v18.19.0 of node

There are a couple closed versions of this issue or a similar one (#1128 and #1146) but the solution listed there is to downgrade the package or the node version.

Older versions of the mailer package have critical security vulnerabilities by requiring vm2 for example. So a better solution is needed.

AdiMarianMutu commented 4 days ago

Having the same issue, is there any solution or workaround which does not require to downgrade?

[EDIT]

A temporary fix is to "manually" install the missing dependency during the deployment.