Webpack cannot resolve class-transformer/storage in a NestJS server bundle
Module not found: Error: Can't resolve 'class-transformer/storage'Short answer
@nestjs/mapped-types tries two paths for the class-transformer metadata store: class-transformer/cjs/storage first, then class-transformer/storage as a fallback. Node handles the failed one at runtime, but webpack tries to resolve both at build time. Bundle the server without node_modules, or ignore the path that does not exist.
Fix it fast
1Find out which cause you have
See which class-transformer version is installed and which package asks for the storage path.
npm ls class-transformer grep -rn "class-transformer/storage" node_modules/@nestjs/mapped-types/dist | head2Match what you see, then jump to its fix
What does the error look like?
Module not found: Error: Can't resolve 'class-transformer/storage'
Cause 1 of 2
Webpack resolves a fallback require that is meant to fail
1Check
In @nestjs/mapped-types the code tries class-transformer/cjs/storage (for 0.3.x and later) and, if that throws, class-transformer/storage (for 0.3.x and earlier). At runtime only one is needed. Webpack follows both and reports the one that is missing in your version.
npm ls class-transformer @nestjs/mapped-types2Fix
Tell webpack to skip the request that does not exist in your version.
// webpack.config.js
const webpack = require('webpack');
module.exports = {
plugins: [
new webpack.IgnorePlugin({ resourceRegExp: /^class-transformer\/storage$/ }),
],
};3Verify
Rebuild the server bundle.
npm run buildConfirmed by raw.githubusercontent.com
Cause 2 of 2
The server bundle includes node_modules that should stay outside it
1Check
A server needs no bundled copy of its npm packages. When webpack pulls them into the output, every optional require inside them has to resolve at build time.
grep -n -E 'externals|externalsPresets|target' webpack.config.js2Fix
Treat Node built-ins and the packages as externals, so they are loaded from node_modules at runtime. List the packages you want left out.
// webpack.config.js
module.exports = {
target: 'node',
externalsPresets: { node: true },
externals: /^(@nestjs\/.*|class-transformer|class-validator)$/,
};3Verify
Rebuild and start the output with node.
npm run build
node dist/server.jsConfirmed by webpack.js.org
How do I stop it coming back?
- Keep the server build separate from the browser build, with its own webpack config.
- Run the built server once in CI, so a bundling error fails the pipeline and not production.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- WorkforceA field app, an admin console and a self-hosted Node.js server for push and reconciliation.
Related fixes
Back end
TypeScript cannot find module '@nestjs/core' or its type declarations
error TS2307: Cannot find module '@nestjs/common' or its corresponding type declarations.
TS2307 means TypeScript searched node_modules and found neither the package nor its types.
3 causes, each with a fixBack end
Node.js in Docker Compose cannot reach MySQL on 127.0.0.1:3306
Error: connect ECONNREFUSED 127.0.0.1:3306
Inside a container, 127.0.0.1 is that container, not MySQL.
3 causes, each with a fixBack end
NestJS GraphQL cannot work out the output type of a field or query
Cannot determine a GraphQL output type for the "<name>". Make sure your class is decorated with an appropriate decorator.
In code-first mode Nest reads TypeScript types through decorators, and arrays, promises and unions disappear at runtime.
2 causes, each with a fixBack end
IntelliJ IDEA breakpoints are ignored in a NestJS app
No 'Debugger listening' line appears when the NestJS app starts
IntelliJ can only debug a NestJS app when the Node.js process runs with the inspector on and the IDE attaches to its port.
4 causes, each with a fixBack end
The nest command is not found in the terminal
bash: nest: command not found
The shell cannot find a nest executable on its PATH.
3 causes, each with a fixBack end
NestJS watch mode does not restart after I save a file
Changes show on the host but not in the running container
Watch mode only sees files that exist inside the process that runs it.
3 causes, each with a fix