Replies: 1 comment 2 replies
-
Really appreciate you bringing this up — this feature would be incredibly helpful! Being able to define chunk filenames using a simple template like Limiting the supported placeholders to Also great to hear that you've already implemented this in a fork — that’s a strong signal of practical demand. Would love to see this upstreamed if maintainers are open to it. Thanks again for opening the discussion and offering to help — hope this moves forward! 🚀 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Goals
1.Support the similar features of output.filename and output.chunkFilename
Non-Goals
Only support template placeholder of "[name]" and "[contenthash:{len}]" like "xyn.[name].[contenthash:8].js", not support more templates
Background
next.js/packages/next/src/build/webpack-config.ts
Line 1279 in 8268575
next.js/packages/next/src/build/webpack-config.ts
Line 1292 in 8268575
the output chunk paths is configured by filename template
Proposal
We implemented these features in an forked repo of next.js , maybe not good enough for now.
v15.3.2...umijs:next.js:utoo-patch-v15.3.2#diff-408605a801220372d0b8bfe1bd753f261fde3a72e9a082b990531fcdb76b6585R426
But we hope it's been supported by Turbopack upstream. If this is acceptable, I can help to port it into upstream.
Beta Was this translation helpful? Give feedback.
All reactions