-
-
Notifications
You must be signed in to change notification settings - Fork 595
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The store works in dev mode(yarn dev), but does not compile for production(yarn buld). #352
Comments
Hi @og-dev, As you already guessed, this is due to the "strict" mode enabled in tsconfig, to solve the error without having to disable the option, you can try the following solutions: Option 1: const countriesInRegion = useMemo(
() => cart?.region.countries.map((c: { iso_2: string }) => c.iso_2),
[cart?.region]
) Option 2: type CountryProps = {
iso_2: string;
};
const countriesInRegion = useMemo(
() => cart?.region.countries.map((c: CountryProps) => c.iso_2),
[cart?.region]
); |
I had the same issue. See my comment at: #279 (comment) |
Should be fixed with the Next.js 15 update. Closing this for now. |
Running Node v23 and NPM v10.9.1 Maybe related to this post... I am trying to deploy the frontend to Azure Container using Docker. Backend builds and deploys no issues, and running the application locally is smooth and no issues... However, when building the storefront during deployment I am getting the following issue: ▲ Next.js 15.0.3
Creating an optimized production build ... |
@dapinitial I'm getting the same error. |
Im getting the same error, any news? |
OS: Ubuntu 20.04
Node: 18.18.0
Fail due Type error: Parameter 'c' implicitly has an 'any' type.
if strict is disbled in tsconfig then: Linting and checking validity of types ..Failed to compile.
Is there a way to fix those error?
I tried to fix the second error by changing @types/react, @types/react-dom but it did not work
The text was updated successfully, but these errors were encountered: