New global.d.ts "*.svg" type blocks locally defined definition (for use with SVGR)

[mikestopcontinues]

What version of Next.js are you using?

11.0.0

What version of Node.js are you using?

14.16.1

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

Vercel

Describe the Bug

I use SVGR to convert svg imports into react components. I define a custom type in next-env.d.ts to support this:

/// <reference types="next" />
/// <reference types="next/types/global" />

declare module '*.svg' {
  import type React from 'react';

  const SVG: React.VFC<React.SVGProps<SVGSVGElement>>;
  export default SVG;
}

However, with the upgrade to Next 11, I find the type definition in next/types/global blocks my custom definition:

declare module '*.svg' {
  const content: StaticImageData

  export default content
}

Expected Behavior

While I understand the utility—and I'm really excited for the direction Next is headed—my apps all only consume SVG as components. Inlining SVGs allows us to do a lot more with them than if they were squashed in image tags. While I would like the ability to do both for cases where it was warranted, it's most important that my types compile now.

I see this bug as applying to all of the module types defined by next. They're important, but they need to be overridable.

To Reproduce

It's as easy as adding the above type definition to next-env.d.ts, then trying to import an svg file into typescript. You'll see the locally defined types are not being used.

---

NOTE: This bug is about the types only. If you landed here for the webpack fix:

     cfg.module.rules[2] = {
        oneOf: [
          {
            test: /\.svg$/,
            use: ['@svgr/webpack'],
          },
          cfg.module.rules[2],
        ],
      };

[stefanprobst]

i think this is already fixed by #26281

[mikestopcontinues]

@stefanprobst Even better than I was hoping. Thanks!

[SalahAdDin]

@stefanprobst how can i test it?
I got this #26400

[stefanprobst]

@SalahAdDin the fix will be in the next release. if you want to test it now, you need to install the next@canary version.

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.