Formail offers a streamlined approach to form management, enabling instant notifications and dynamic data handling without pre-structured forms. Ideal for developers, small businesses, and anyone needing efficient form submission management, Formail simplifies the process, making it accessible and user-friendly.
Description
During our latest deployments using Vercel, we encountered several warnings related to linting and best practices in our Next.js application. Addressing these warnings will improve our code quality and application performance.
Details
[x] Unresolvable Prop Values in JSX:
Issue: Linter warnings about prop values with expressions of type AwaitExpression that could not be resolved.
File(s): Various
Expected Action: Investigate why AwaitExpression types are used in JSX props and assess if they can be refactored to resolve at build time. Consider filing an issue with jsx-eslint/jsx-ast-utils if the warning persists.
[x] Usage of Tag Instead of from next/image:
File: ./src/app/dashboard/[orgId]/form/[formId]/files/page.tsx
Warning: Using could result in slower LCP (Largest Contentful Paint) and higher bandwidth usage.
Expected Action: Replace tags with components from next/image for optimized image handling. This requires ensuring that our deployment is configured to handle the potential additional usage or cost.
[x] Inefficient Dependency Handling in useEffect:
File: ./src/components/ui/hover-border-gradient.tsx
Warning: The 'rotateDirection' function within useEffect changes on every render, leading to potential performance issues.
Expected Action: Refactor the 'rotateDirection' function to be either wrapped in a useCallback() or moved inside the useEffect callback to stabilize the dependencies.
[x] error - No Sentry auth token configured. Source maps will not be uploaded.
You can find information on how to generate a Sentry auth token here: https://docs.sentry.io/api/auth/
After generating a Sentry auth token, set it via the SENTRY_AUTH_TOKEN environment variable during the build.
Description During our latest deployments using Vercel, we encountered several warnings related to linting and best practices in our Next.js application. Addressing these warnings will improve our code quality and application performance.
Details
[x] Unresolvable Prop Values in JSX: Issue: Linter warnings about prop values with expressions of type AwaitExpression that could not be resolved. File(s): Various Expected Action: Investigate why AwaitExpression types are used in JSX props and assess if they can be refactored to resolve at build time. Consider filing an issue with jsx-eslint/jsx-ast-utils if the warning persists.
[x] Usage of![]()
Tag Instead of ![]()
could result in slower LCP (Largest Contentful Paint) and higher bandwidth usage.
Expected Action: Replace ![]()
tags with
[x] Inefficient Dependency Handling in useEffect: File: ./src/components/ui/hover-border-gradient.tsx Warning: The 'rotateDirection' function within useEffect changes on every render, leading to potential performance issues. Expected Action: Refactor the 'rotateDirection' function to be either wrapped in a useCallback() or moved inside the useEffect callback to stabilize the dependencies.
[x] error - No Sentry auth token configured. Source maps will not be uploaded. You can find information on how to generate a Sentry auth token here: https://docs.sentry.io/api/auth/ After generating a Sentry auth token, set it via the SENTRY_AUTH_TOKEN environment variable during the build.