@alexander-akait
Nothing works for me, I see this error and unable to use cache.
I there is a way to debug enhanced-resolver?
I want to solve this problem.

<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: Can't resolve '@softvisio/vue/webpack-components/main' in 'd:\projects\softvisio-node\vue-ext\resources\webpack-components\main'
<w> while resolving '@softvisio/vue/webpack-components/main' in d:\projects\softvisio-node\vue-ext\resources\webpack-components\main as file
<w>  at resolve esm file @softvisio/vue/webpack-components/main
<w>  at file dependencies d:\projects\softvisio-node\vue-ext\resources\webpack-components\main\component.js
<w>  at file d:\projects\softvisio-node\vue-ext\resources\webpack-components\main\component.js
<w>  at resolve esm file @softvisio/vue-ext/webpack-components/main
<w>  at file dependencies d:\projects\zdm\playground\frontend\resources\webpack-components\main\component.js
<w>  at file d:\projects\zdm\playground\frontend\resources\webpack-components\main\component.js
<w>  at resolve commonjs d:\projects\zdm\playground\frontend\resources\webpack-components\main\component.js
<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: Can't resolve '@softvisio/vue/webpack-components/main' in 'd:\projects\softvisio-node\vue-ext\resources\webpack-components\main'
<w> while resolving '@softvisio/vue/webpack-components/main' in d:\projects\softvisio-node\vue-ext\resources\webpack-components\main as file
<w>  at resolve esm file @softvisio/vue/webpack-components/main
<w>  at file dependencies d:\projects\softvisio-node\vue-ext\resources\webpack-components\main\component.js
<w>  at file d:\projects\softvisio-node\vue-ext\resources\webpack-components\main\component.js
<w>  at resolve esm file @softvisio/vue-ext/webpack-components/main
<w>  at file dependencies d:\projects\zdm\playground\frontend\resources\webpack-components\main\component.js
<w>  at file d:\projects\zdm\playground\frontend\resources\webpack-components\main\component.js
<w>  at resolve commonjs d:\projects\zdm\playground\frontend\resources\webpack-components\main\component.js

Seems, that extended-resolver is configured to resolve dependencies for sub-packages starting from the sub-package root dir, but the correct way is to resolve them starting from the main module root dir.

This is not so rare case, this is very helpful when you for example need to work both on the end-user application and the shared web components libraries.

Interesting, that deps resolver failed only for build dependencies, but works for the same dependencies in the main build process.
Maybe fix can be simple?

ebhanced-resolver is too complex.

Did you considered to use built-in node resolcer.

import module from "node:module";

module.createRequire( from ).resolve( path );

It will work 100% correctly.

Only need to add support for custom aliases and some other features, which are used in webpack.

I can create the code.

We can do it, I doubt it only because all the time using webpack you are the first and only one who has encountered this...

technically it is possible to implement the possibility of configuring internal revolvers, but I'm not sure it will be worth the effort (very exotic case)

I honestly can't understand what the problem is with using dependencies using package.json (dependencies and devDependencies), you don't specify dependencies directly, so they don't appear in node_modules and as i said earlier such behavior can lead to unpredictable results, for example duplicated packets can be considered as completely different, which will make your bundle bigger.

I want to help you, I want to say that's such behavior is extremely undesirable and you could potentially get into serious trouble - your dependency tree is broken. The problem will be especially evident with transitive dependencies. And I don’t understand why you ignore the direct words from the author of the project that this approach is dangerous.

As well as direct words from the developer of the node:

Note, however, that using --preserve-symlinks can have other side effects. Specifically, symbolically linked native modules can fail to load if those are linked from more than one location in the dependency tree (Node.js would see those as two separate modules and would attempt to load the module multiple times, causing an exception to be thrown).

In my reproduction I didn't specified dependencies, because package-a and package-b are not published.
In my other projects all deps are specified and results are the same.

Generally - it works, project compiled, but without cache. I am unable to be happy, when something not works.
Ok, I will debug it when will find a time, currently I am overloaded with the ongoing work.
Thank you for your help.

@alexander-akait

Is it possible to use hooks for resolvers that are used to resolve build dependencies?
This problem can be fixed if we add something like SymlinksPlugin for this resolver.

Please add, I you can.
But at first, could you please point me to the place in the code, where build dependencies resolvers created?
I will test if symlink resolver will help.