Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PackFileCacheStrategy/FileSystemInfo warnings in console when using buildDependencies #17865

Closed
GaganpreetKaurKalsi opened this issue Dec 13, 2023 · 1 comment

Comments

@GaganpreetKaurKalsi
Copy link

Bug report

What is the current behavior?

I am getting below warnings in console on doing production build. I am using filesystem cache and importing a few files in my webpack.config.js using relative path.

[webpack.cache.PackFileCacheStrategy/webpack.FileSystemInfo] 
Resolving 'build-config/alias.config' in 
/Users/gaganpreetkaurkalsi/web-app/build-config/webpack 
for build dependencies doesn't lead to expected result 
'/Users/gaganpreetkaurkalsi/web-app/build-config/alias.config.js',
but to 'Error: Can't resolve 'build-config/alias.config' in 
'/Users/gaganpreetkaurkalsi/web-app/build-config/webpack'' instead. 
Resolving dependencies are ignored for this path.

If the current behavior is a bug, please provide the steps to reproduce.
Using cache in production mode should enable you to see these warnings.

cache: {
    name: "prod",
    type: "filesystem",
    allowCollectingMemory: true,
    buildDependencies: {
      config: [__filename],
    },
  },

What is the expected behavior?
Any work around this warning? Any solution?

Other relevant information:
webpack version: 5.89.0
Node.js version: 14
Operating System: MacOS
Additional tools:

@snitin315
Copy link
Member

@GaganpreetKaurKalsi Can you provide a reproducible GitHub repo?

@webpack webpack locked and limited conversation to collaborators Dec 29, 2023
@alexander-akait alexander-akait converted this issue into discussion #17913 Dec 29, 2023

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants