Imam Alfarizi

> @ImamAlfariziSyahputra Here you go: > > ``` > import React, { useEffect } from 'react'; > > import { Html5Qrcode } from 'html5-qrcode'; > > import Header from 'components/shared/Header';...

> @ajsystem , I checked the latest Nextjs v14.0.4. and nextjs-toploader works fine in that version. I think this issues should be closed now let see what other people opinions...

facing the same issue, any updates? ```javascript // tsconfig.json { "$schema": "https://json.schemastore.org/tsconfig", "display": "Default", "compilerOptions": { "composite": false, "declaration": true, "declarationMap": true, "esModuleInterop": true, "forceConsistentCasingInFileNames": true, "inlineSources": false, "isolatedModules": true,...

> Hello do we have a solution soon for this issue? Next.js 15 just released so I'd assume more people will run into this as well sorry for tagging you...

> I'm using Next.js 15 with `react-leaflet` v5.0.0-rc.1, and I haven't encountered any issues with it. Have you tried this release candidate version? yes, it is working fine on `rc`...

> This will be fixed by [microsoft/TypeScript#60005](https://github.com/microsoft/TypeScript/pull/60005) It’s been a year, and it’s still not fixed.🙁

but it still got types errors if using callback like on `where` clause here: ```ts const isUserExists = await dbDrizzle.query.userTable.findFirst({ where: (user, { eq }) => eq(user.email, email), }); ```...

Maybe you guys could see this alternative https://github.com/schoero/eslint-plugin-better-tailwindcss

@diegomura sorry for tagging you

> This is still an issue in V4.1.5, is there any fix or workaround for this? yes i still facing this issue. still using `@ts-expect-error` to ignoring the type errors