Rename messages/en.d.json.ts to messages/en.json.d.ts

[s-lukashenka-micoworks]

Is your feature request related to a problem? Please describe.

The file named as-is (messages/en.d.json.ts) is causing the following parse error with webpack:

./messages/en.d.json.ts
Module parse failed: Cannot parse JSON: Unexpected token '/', "// This fi"... is not valid JSON while parsing '// This file is auto-generated by next-i'
File was processed with these loaders:

• ./node_modules/.pnpm/next@15.2.4_@babel+core@7.26.7_@opentelemetry[email protected][email protected][email protected][email protected]/node_modules/next/dist/build/webpack/loaders/next-flight-loader/index.js
• ./node_modules/.pnpm/next@15.2.4_@babel+core@7.26.7_@opentelemetry[email protected][email protected][email protected][email protected]/node_modules/next/dist/build/webpack/loaders/next-swc-loader.js
  You may need an additional loader to handle the result of these loaders.
  Error: Cannot parse JSON: Unexpected token '/', "// This fi"... is not valid JSON while parsing '// This file is auto-generated by next-i'
  at JsonParser.parse (/Users/m290/projects/mv-dashboard/node_modules/.pnpm/next@15.2.4_@babel+core@7.26.7_@opentelemetry[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/webpack/bundle5.js:29:1049723)
  at /Users/m290/projects/mv-dashboard/node_modules/.pnpm/next@15.2.4_@babel+core@7.26.7_@opentelemetry[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/webpack/bundle5.js:29:411930
  at processResult (/Users/m290/projects/mv-dashboard/node_modules/.pnpm/next@15.2.4_@babel+core@7.26.7_@opentelemetry[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/webpack/bundle5.js:29:407884)
  at /Users/m290/projects/mv-dashboard/node_modules/.pnpm/next@15.2.4_@babel+core@7.26.7_@opentelemetry[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/webpack/bundle5.js:29:408906
  at /Users/m290/projects/mv-dashboard/node_modules/.pnpm/next@15.2.4_@babel+core@7.26.7_@opentelemetry[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:8727
  at iterateNormalLoaders (/Users/m290/projects/mv-dashboard/node_modules/.pnpm/next@15.2.4_@babel+core@7.26.7_@opentelemetry[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:5565)
  at iterateNormalLoaders (/Users/m290/projects/mv-dashboard/node_modules/.pnpm/next@15.2.4_@babel+core@7.26.7_@opentelemetry[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:5650)
  at /Users/m290/projects/mv-dashboard/node_modules/.pnpm/next@15.2.4_@babel+core@7.26.7_@opentelemetry[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:5879
  at r.callback (/Users/m290/projects/mv-dashboard/node_modules/.pnpm/next@15.2.4_@babel+core@7.26.7_@opentelemetry[email protected][email protected][email protected][email protected]/node_modules/next/dist/compiled/loader-runner/LoaderRunner.js:1:4039)
  at Object.transformSource (/Users/m290/projects/mv-dashboard/node_modules/.pnpm/next@15.2.4_@babel+core@7.26.7_@opentelemetry[email protected][email protected][email protected][email protected]/node_modules/next/dist/build/webpack/loaders/next-flight-loader/index.js:151:10)

Import trace for requested module:
./messages/en.d.json.ts

Describe the solution you'd like

Rename the generated type file from messages/en.d.json.ts to messages/en.json.d.ts

Describe alternatives you've considered

I am not sure if this is the only solution but it looks like a potential solution.

[amannn]

Renaming it to messages/en.json.d.ts won't work, that file is not picked up by TypeScript.

Not sure what is causing your import error, you can check the examples on the website to explore a working setup.

I'll move this to a discussion since it seems to be a usage question.