Use file-loader to modify the image path error after packaging

[dongcer]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Home China
    Binaries:
      Node: 14.17.6
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.2.4
      eslint-config-next: 12.2.2
      react: 18.2.0
      react-dom: 18.2.0

warn  - Latest canary version not detected, detected: "12.2.4", newest: "13.4.5-canary.4".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

no

To Reproduce

//next.config.js
webpack: (config, options) => {

config.module.rules.push(
  {
    test: /\.(png|jpe?g|gif|svg)$/i,
    use: [
      {
        loader: 'file-loader',
        options: {
          name: 'static/medssssia/[name].[hash].[ext]',
          publicPath: '/scasca',
          outputPath: 'static/images',
        },
      },
    ],
  }
);

return config;

}

//index.tsx

import Image from "next/image";
import logo from "@/assets/arrowNone.png"

const Home = (props: any) => {

return (

//

<Image  height={90} width={120} src={logo} alt=""  ></Image>

) };

export default Home;

Describe the Bug

An error is reported when building

Expected Behavior

Whether I introduce a local Image in the next/Image, IMG Tag, or Sass, I want to be able to change the path of the packaged Image

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[nextjs-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[nextjs-bot]

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!