json import errors after 3.0.0 update

[madisp]

After bumping to 3.0.0 I'm getting

TypeError: Module "file:///.../node_modules/@fortawesome/fontawesome-svg-core/package.json" needs an import attribute of "type: json"

when running a test with vitest on a file that imports @fortawesome/react-fontawesome.
I'm guessing it has something to do with the import here?

react-fontawesome/src/utils/constants.ts

Line 6 in 7e7375b

import SVGCorePackageJson from '@fortawesome/fontawesome-svg-core/package.json'

[matys1]

Same issue!

[matys1]

I found a workaround for the time being. If you add below to your vite.config.ts it should fix the issue:

  ssr: {
    // ensure react-fontawesome is not externalized to Node at runtime
    noExternal: ["@fortawesome/react-fontawesome"],
  },

Node 22 requires an import attribute for JSON with { type: "json" }. Somewhere inside the dependency chain there’s an ESM import of a JSON file (…/fontawesome-svg-core/package.json). When SSR runs, Node tries to load that JSON directly and throws.

Hopefully they fix it asap so you don't need to externalize.

[charles4221]

This one is strange because when using 3.0.0 to render icons in SSR-capable frameworks like Next and Vite I’m not seeing this issue. It seems to be specifically when running Vitest (Jest also works fine in a NextJS codebase I’ve tested in).

If you’re experiencing the same, maybe try implementing a global mock for FontAwesomeIcon for your tests. I will continue to investigate but this might be enough to get you moving.

If you’re seeing this when actually running a vite app in development or production, please let me know so I can prioritise further.

[matys1]

I'm seeing this error when running a Remix/Vite app in dev (npm run dev). The workaround I described above fixed it.

[stevensacks]

This error also happens in vitest.

[jeremy-step]

Happens with Astro too, easiest fix would probably be to add with { type: "json" } to the import of package.json in src/utils/constants.ts.

[ken717w]

I'm wondering if v3.0.0 is a typo of v0.3.0? It was still v0.2.x yesterday.

[charles4221]

Happens with Astro too, easiest fix would probably be to add with { type: "json" } to the import of package.json in src/utils/constants.ts.

Of course this would be an “easy” fix for this particular use case, but it would also break the library for many other users who aren’t using Vitest, and it would also significantly impact our browser support.

[charles4221]

I'm wondering if v3.0.0 is a typo of v0.3.0? It was still v0.2.x yesterday.

No typo. 3.0.0 is a complete rewrite.