Alexander Kachkaev

I'd be keen to, but its just my third day of using VSCode and I'm already getting behind my todo-list because of this pause on exploration 😅 I'll be happy...

@tyrasd 🙏

@serialgit what do you mean by compatibility with React 19? I am using `[email protected]` with React 19 and I don’t see any issues. Peer dependencies in `package.json` do not set...

@LeVraiSylvain which TypeScript version you are using? Upgrading may help, as suggested by https://github.com/DefinitelyTyped/DefinitelyTyped/issues/63022#issuecomment-1299413865.

There exists [@types/eslint-plugin-tailwindcss](https://www.npmjs.com/package/@types/eslint-plugin-tailwindcss) which you can install in the meantime.

The issue you have created is valid, let’s keep it open for now. While `@types/eslint-plugin-tailwindcss` package does the job, it’d be more convenient to use types directly from `eslint-plugin-tailwindcss`. One...

Seems to be fixed in `[email protected]` 🎉 Related PR: https://github.com/import-js/eslint-plugin-import/pull/3097

Another problem with the `/app` folder is the lack of router events in `next/navigation`: https://github.com/vercel/next.js/issues/45499. This may get fixed by https://github.com/vercel/next.js/pull/46391.

Looking at Amplify docs (https://docs.aws.amazon.com/amplify/latest/userguide/ssr-deployment-specification.html), I don’t see signs of Node 22 support. For example, there is this: ```ts type ComputeRuntime = 'nodejs16.x' | 'nodejs18.x' | 'nodejs20.x'; ``` and this:...

Node.js 18 reached _end of life_ in April 2025 ([official version list](https://nodejs.org/en/about/previous-releases#looking-for-the-latest-release-of-a-version-branch)). So the only option for Amplify gen 1 is Node 20 despite that Node 22 has been available...