Any idea why this happens after upgrade from 2.23 ...
# prisma-clientt
Tigran Tokmajyan
10/27/2021, 4:25 PMAny idea why this happens after upgrade from 2.23 to 3.3?
Copy code
WARNING in ./libs/prisma/src/lib/client/runtime/index.js 81:73-80
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARNING in ./libs/prisma/src/lib/client/runtime/index.js 85:15-22
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
Debugger listening on <ws://localhost:59074/bf3dd720-b8d2-4f0e-91c1-d9b4532054a3>
Debugger listening on <ws://localhost:59075/bf3dd720-b8d2-4f0e-91c1-d9b4532054a3>
For help, see: <https://nodejs.org/en/docs/inspector>
C:\gits\boon\backend\dist\apps\cron\webpack:\libs\prisma\src\lib\client\runtime sync:2
var e = new Error("Cannot find module '" + req + "'");
^
Error: Cannot find module 'os'
at webpackEmptyContext (C:\gits\boon\backend\dist\apps\cron\webpack:\libs\prisma\src\lib\client\runtime sync:2:1)
at ../../node_modules/.pnpm/supports-color@7.2.0/node_modules/supports-color/index.js (C:\gits\boon\backend\dist\apps\cron\webpack:\libs\prisma\src\lib\client\runtime\index.js:1740:15)
at __require2 (C:\gits\boon\backend\dist\apps\cron\webpack:\libs\prisma\src\lib\client\runtime\index.js:89:45)
at ../../node_modules/.pnpm/chalk@4.1.2/node_modules/chalk/source/index.js (C:\gits\boon\backend\dist\apps\cron\webpack:\libs\prisma\src\lib\client\runtime\index.js:2004:56)
at __require2 (C:\gits\boon\backend\dist\apps\cron\webpack:\libs\prisma\src\lib\client\runtime\index.js:89:45)
at Object../libs/prisma/src/lib/client/runtime/index.js (C:\gits\boon\backend\dist\apps\cron\webpack:\libs\prisma\src\lib\client\runtime\index.js:30779:33)
at __webpack_require__ (C:\gits\boon\backend\dist\apps\cron\webpack:\webpack\bootstrap:19:1)
at Object../libs/prisma/src/lib/client/index.js (C:\gits\boon\backend\dist\apps\cron\webpack:\libs\prisma\src\lib\client\index.js:17:5)
at __webpack_require__ (C:\gits\boon\backend\dist\apps\cron\webpack:\webpack\bootstrap:19:1)
at Object../libs/common/src/lib/services/prisma.service.ts (C:\gits\boon\backend\dist\apps\cron\webpack:\libs\common\src\lib\services\prisma.service.ts:2:1)r
Ryan
10/28/2021, 2:36 PM@Tigran Tokmajyan 👋
Are you using Webpack 5?
t
Tigran Tokmajyan
10/28/2021, 3:38 PMNo we're on webpack 4
Tigran Tokmajyan
10/28/2021, 3:38 PMso you say we have to upgrade to 5? 🙂
Tigran Tokmajyan
10/28/2021, 4:24 PM@Ryan Getting that with webpack 5.60.0
r
Ryan
10/29/2021, 6:46 AMIn Webpack 4, did you set the target to
nodet
Tigran Tokmajyan
10/29/2021, 6:53 AMYes. i'll double check. We're using nrwl/nx which takes care for webpack stuff.
👍 1
Tigran Tokmajyan
10/29/2021, 10:38 AM@Ryan just did check. we have
target: nodeTigran Tokmajyan
10/29/2021, 10:38 AMplease see webpack config:
Copy code
{
entry: { main: [ 'C:\\gits\\prj\\backend\\apps\\rest\\src\\main.ts' ] },
devtool: 'source-map',
mode: 'development',
output: {
path: 'C:\\gits\\prj\\backend\\dist\\apps\\rest',
filename: 'main.js',
hashFunction: 'xxhash64',
pathinfo: false,
libraryTarget: 'commonjs'
},
module: { unsafeCache: true, rules: [ [Object] ] },
resolve: {
extensions: [ '.ts', '.tsx', '.mjs', '.js', '.jsx' ],
alias: {},
plugins: [ [TsconfigPathsPlugin] ],
mainFields: [ 'es2015', 'module', 'main' ]
},
performance: { hints: false },
plugins: [
ForkTsCheckerWebpackPlugin { options: [Object] },
CopyPlugin { patterns: [Array], options: {} }
],
watch: true,
watchOptions: { poll: undefined },
stats: {
hash: true,
timings: false,
cached: false,
cachedAssets: false,
modules: false,
warnings: true,
errors: true,
colors: true,
chunks: true,
assets: false,
chunkOrigins: false,
chunkModules: false,
children: false,
reasons: false,
version: false,
errorDetails: false,
moduleTrace: false,
usedExports: false
},
experiments: { cacheUnaffected: true },
target: 'node',
node: false,
externals: [ [Function (anonymous)] ]
}Tigran Tokmajyan
10/31/2021, 2:45 PMHey @Ryan did you had a chance to look at this?
r
Ryan
11/01/2021, 12:01 PM@Tigran Tokmajyan Will look into this today and get back to you by tomorrow 🙂
t
Tigran Tokmajyan
11/01/2021, 12:17 PMThanks @Ryan
Tigran Tokmajyan
11/02/2021, 8:23 PM@Ryan it seems like someone else reported this as well: https://github.com/prisma/prisma/issues/10058
👍 1
7 Views