[12.0.0] Resources type is not exported anymore
See original GitHub issue🐛 Bug Report
> tsc --noEmit false --declaration --emitDeclarationOnly --outDir dist/types
src/types.ts:8:3 - error TS2305: Module '"react-i18next"' has no exported member 'Resources'.
To Reproduce
I think it’s a breaking change… You can have a look to this PR and watch for the CI failure
https://github.com/i18next/next-i18next/pull/1966
Your Environment
- runtime version: i.e. node v14, deno, browser xy
- i18next version: i.e. 19.5.3
- os: Mac, Windows, Linux
- any other relevant information
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
"'node_modules/@prisma/client' has no exported member ...
This issue occurs when we try to use/import the enums that we define in schema.prisma file. ... npx prisma db pull && prisma...
Read more >Why am I getting "no exported member" errors when ...
I've looked at an alike issue: Ng serve throwing @angular/core/core has no exported member 'eeFactoryDef' which was the only trail I could find...
Read more >Resolve the "No Export named XYZ found" error in ...
I receive the "No Export named XYZ found" error in AWS CloudFormation when I use Fn::ImportValue in my stack.
Read more >Oracle Data Pump Export
The Oracle Data Pump Export utility is used to unload data and metadata into a set of operating system files, which are called...
Read more >Corn and Soybean Production Costs and Export ... - USDA ERS
This report explores export competitiveness for soybeans and corn in Argentina, ... soybean production is from the Heartland, compared with no more than...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
So can this be closed @belgattitude ?
yep, we moved all types to
i18next
, where it should be since the very beginning. I put a PR adding a reference to the new doc. https://github.com/i18next/react-i18next-gitbook/pull/140