When I build after change package.json version:
\n...\n[webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] **/**/apps/go/package.json invalidated because hashes differ (2ff3eb40e39aa12c4653911ac2cec26b != 48ab5c04ed5af4e365e6fa6287cccf7c)\n...\nWhat is the expected behavior?
\nI hope that when I specify buildDependencies, only the files specified by that value will be considered. If I want to monitor package.json, I can add it manually, or add yarn.lock.
\nOther relevant information:
\nwebpack version: 5.99.8
\nNode.js version: 18.20.0
\nOperating System: MacOS
\nAdditional tools:
@JerryLyu93 it means somewhere you have require(\"./package.json\"), we analyze all require/import in files which you use in buildDependencies including nested files
Webpack Cache PackFileCacheStrategy always care package.json #19538
-
|
This might be more of a misunderstanding on my part. Bug reportWhat is the current behavior? If the current behavior is a bug, please provide the steps to reproduce. I have manually specified buildDependencies, which does not include package.json. However, if I only modify the version in package.json (which does not involve any dependency changes), all dependencies are still discarded. Webpack Cache Config: {
type: 'filesystem',
version: '31098c07c1e6ee6f0124f2f0ee5de6aa',
cacheDirectory: 'my-project/.webpack-cache',
store: 'pack',
buildDependencies: {
config: [
'my-project/node_modules/react-scripts/config/webpack.config.js',
'my-project/dev-configs/config-overrides/bundle.js',
'my-project/dev-configs/config-overrides/debug.js',
'my-project/dev-configs/config-overrides/index.js',
'my-project/dev-configs/config-overrides/performance.js',
'my-project/dev-configs/config-overrides/transform-imports.js',
'my-project/dev-configs/config-overrides/utils.js',
'my-project/apps/go/config-overrides.js'
],
tsconfig: [
'my-project/apps/go/tsconfig.json'
]
},
name: 'go'
}When I build after change package.json version: What is the expected behavior? I hope that when I specify buildDependencies, only the files specified by that value will be considered. If I want to monitor package.json, I can add it manually, or add yarn.lock. Other relevant information: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
@JerryLyu93 it means somewhere you have |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reply! In the file I specified, there is no reference to package.json. However, I noticed that when the compilation is completed and caching is done, the content of the build dependencies increases. Additionally, dynamic imports shouldn't be taken into account, right?
|
Beta Was this translation helpful? Give feedback.
-
They take into account Why changed version is bad for you? |
Beta Was this translation helpful? Give feedback.
-
|
Because we are working on a massive application, the compilation process is very time-consuming, and our compilation on ci is triggered by changes to the version in the package.json file. As a result, sometimes we just want to deploy a very small bug fix, but still have to perform a full compilation due to the changes in package.json. |
Beta Was this translation helpful? Give feedback.
-
|
But after some investigation and consideration, I believe that observing the entire content of package.json is a more meaningful and lower-risk choice. I have now decoupled our version control from package.json because, in reality, we are not publishing the app as a package to npm, so it’s not necessary to use the version field in package.json, even though it is a naturally good version controller. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reply, it makes things more clear! |
Beta Was this translation helpful? Give feedback.
@JerryLyu93 it means somewhere you have
require("./package.json"), we analyze allrequire/importin files which you use inbuildDependenciesincluding nested files